Come code hub

The Come code hub publishes the status of any public literal code, the rules around destination-applied offers, the safe-apply three-step path and the verification surface each offer is read against.

How destination-applied offers work

On Come, an "offer" is a destination-applied reward. It is not a coupon. There is no input field on the deposit screen where a visitor can paste a code; the offer is attached to the user's account through the verified install path and surfaces inside the bonus card the moment the wallet is opened.

Verified surface points:

• Install path - the verified route is /install/; offers do not bind to any other install path.
• KYC state - the KYC must be complete before the offer activates. A pending KYC holds the offer without surfacing it in the bonus card.
• Bonus card - the destination surface is the bonus card on the wallet screen, not the deposit screen.
• Snapshot timestamp - every offer carries a snapshot timestamp on the same row as the prize pool / match-data block; that timestamp is the source of truth at request time.

How to verify an applied offer

The verification path is small and stays the same on every offer. Open the bonus card and confirm the four fields below match the snapshot; if any field disagrees, the offer is not on the verified surface and the support desk will treat the ticket accordingly.

1. Offer name. Matches the offer name on the snapshot row in the promos hub.
2. Snapshot timestamp. The timestamp on the bonus card matches the value listed in the promos hub at request time.
3. KYC state. KYC is complete. If KYC is pending, the offer is held and the bonus card shows a hold reason.
4. Install route. The installed package matches the verified route at /install/. If the install came from a third-party mirror, the offer is not on the verified surface.

Why there is no public literal code

Come offers are destination-applied because the offer terms are bound to the install path, the KYC state and the wallet timestamp. A public literal code is a code that anyone can paste into a code field on a deposit screen, regardless of which install path the visitor used, whether KYC is complete, or what timestamp the wallet shows. Verified: that pattern is incompatible with the verified install path at /install/ because the offer would have to bind to anyone, including third-party mirrors. Unverified: any public literal code claimed to be valid on Come is either a third-party mirror code (not on the verified surface) or an old code that has since been retired from the snapshot.

Three reasons there is no public literal code:

1. Install path binding. The verified install path is a first-party route; a public code would let offers bind to mirrors that bypass the first-party route and the verified install hint on the lobby.
2. KYC binding. A pending KYC holds the offer without surfacing it in the bonus card. A public code cannot enforce that hold, so a code-style offer would surface before KYC is complete and the verification step would no longer be a gate.
3. Timestamp binding. Each offer carries a snapshot timestamp on the bonus card. A public code would not know the timestamp, so the offer row on the wallet could not be reconciled with the row on the promos hub.

The "code" wording that does appear on the surface

The word "code" appears on the verified surface in three places that are not literal codes. Verified: each of these is named on the relevant surface and is read against the snapshot timestamp. Unverified: any literal "code" string on a third-party mirror is not part of the verified surface and is closed on tickets against the public documentation.

The three places the word "code" appears:

• Code hub. This page lists the status of any public literal code, which is currently "no public literal code confirmed". The status is a single line at the top of the page; the rest of the page is about destination-applied offers and the safe-apply three-step path.
• Promo credits row. The promos hub lists offers with a snapshot timestamp and a destination surface. The "code" on a promos row is the snapshot timestamp, not a coupon.
• Bonus card. The bonus card on the wallet shows the offer name, the snapshot timestamp and the destination surface. There is no coupon field on the bonus card.

What to do if a third-party site lists a "Come code"

Third-party sites that list a "Come code" are not on the verified surface. Verified: a code claimed to be valid on a third-party site does not bind to the verified install path at /install/ and does not surface in the bonus card. Unverified: a code claimed to be valid on a third-party site may bind to a third-party mirror, in which case the deposit lands in the manual review queue and the offer does not pay out through the verified surface.

How to handle a third-party code claim:

1. Confirm the install route. The verified route is /install/. A third-party code cannot apply to a verified install; the two surfaces are separate.
2. Confirm the KYC state. KYC must be complete on the verified surface for any offer to surface in the bonus card. A third-party code claim does not change the KYC state on the verified surface.
3. Open a ticket on the verified surface. If a third-party code is offered, open a ticket at /contact/ with the code, the third-party URL, the timestamp on the offer and the timestamp on the bonus card. The support desk can resolve the offer against the snapshot.