In-person quests with Solana Pay

Check members in at a booth, a door or a stage with a printed QR code. Members scan it with a mobile wallet, sign, and complete the quest for that station.

Print a QR code at each station of an event, such as a booth, a door or a stage. A member scans it with their mobile wallet and signs one transaction, and the quest completes for that station. The transaction moves no funds: the member pays only Solana's network fee.

The code points at your app, which serves each station as a Solana Pay transaction request. Domino adds the quest's memo and checks the quest once the transaction lands. Domino doesn't host station URLs for you.

This is experimental: a minor release can change it.

What members see

  1. The member opens their wallet's QR scanner and scans the station's code.
  2. The wallet shows your app's name and icon, and a message: "Checks you in at North gate for "Check in at our booth"", with a note to sign in to your app first if the wallet isn't linked yet.
  3. The member signs. The transaction sends 0 SOL from their wallet to itself and carries the quest's memo.
  4. Within about a minute, the quest shows as complete for that station in your app.

Solana Pay gives your app no callback after the member signs. Each transaction names a one-time reference account, and your app looks it up on Solana for about 90 seconds after it answers, then hands the transaction to Domino.

Set it up

Declare the stations

List the stations on the quest, each with a key and a label, and optional opening and closing times. Check-in stations shows the quest and each rule. Deploy it.

Serve the stations from your app

Your app needs a server key with Read and Ingest, as for blinks, and a Solana RPC endpoint for the quest's cluster.

The handler refuses before the member signs when:

RefusalStatus
The URL names no station400
The quest has no station with that key404
The station isn't open now, or you revoked it409
The quest has no stations, is paused or has ended422

The station URL must be public HTTPS. A hosted app on *.domino.page needs transparent routing, since legacy routing refuses POST.

Print the codes

In Console, open the quest. Its Check-in stations section lists each station. Enter your app's station URL in App action URL, then use Download QR on a station for an SVG to print or a PNG. Console remembers the URL in your browser for that quest and environment. A station a code proves gets its QR code from Domino instead, linked to your app's scan page: see stations a code proves.

Or write one code per station with the CLI, pointing at the URL your app serves:

domino quests stations qr booth-check-in --url https://your-app.example/api/stations/booth

It writes <station key>.svg per station into booth-check-in-stations/, with the station's label printed under the code. Each code encodes solana: and your URL with ?station=<key>. Pass --out to write elsewhere and --force to overwrite. With --json, it lists the files and what each encodes. Console and the CLI draw the same code for the same station and URL. When the quest also has stations a code proves, add --page-url with your scan page, and the same command writes their files too.

Test it

  1. Open the station URL with ?station=<key> in a browser. It answers the label and icon as JSON.
  2. Scan a code with a wallet a member linked, on the quest's cluster, and sign. Check the quest shows as complete for that station in your app.
  3. Scan the same code again: the quest stays complete once for that station.
  4. Scan with a wallet no member linked to see what an unlinked member sees.

At the event

Time windows. A station takes a transaction whose block time falls in its window, between opensAt and closesAt. A member who signs just before closing still checks in. Your app also refuses to build a transaction for a station that is closed when the member scans, so nobody pays a fee for nothing.

Once per member per station. With perStation(), a member who scans the same station twice completes it once. A quest with several stations completes once for each.

Unlinked wallets. Domino completes the quest only for a wallet a member linked. The wallet's message asks the member to sign in to your app first. If they signed before linking, the check-in doesn't count: they sign in to your app with that wallet, which links it, then scan the code again.

A check-in that didn't count. On a quest with stations, only a transaction that names a station completes it, so the quest's Check button in your app can't. If your app missed the transaction, for example because it wasn't found within 90 seconds, the member scans again. A station already completed stays completed once.

A leaked code. If a station's code is photographed and shared, open the quest in Console and choose Revoke on the station, with a reason. From then on Domino refuses every transaction for that station in that environment, even one a member signed before you revoked it, and your app refuses to build one. Completions the station already gave stay. Revoking is not a change to the quest, so it takes effect in live at once, without a promotion, and a promotion never undoes it. Restore makes the station take check-ins again. Revoking and restoring need the publish permission, as pausing a quest does, and the audit log records both with their reasons.

Replacing a code. To retire a printed code for good, add a station with a new key and give the old one a closesAt, or revoke it. Then print the new code.

Which wallets work

The member's wallet must support Solana Pay transaction requests, where the wallet asks your app for the transaction. Some wallets support only transfer requests, which send a fixed payment.

WalletTransaction requests
PhantomListed as a Solana Pay wallet in Solana's documentation. Not tested by Domino on a device.
SolflareListed as a Solana Pay wallet in Solana's documentation. Not tested by Domino on a device.
BackpackListed as a Solana Pay wallet in Solana's documentation. Not tested by Domino on a device.

We found no page in these wallets' own documentation that says whether they take transaction requests, or a transaction that moves no funds. Scan a code with each wallet your members use before the event.

Guard against farming

Anyone who knows the station URL can ask for its transaction without being at the event, and a code can be photographed and shared. Domino checks the station's window and completes each station once per member, so the window is your main guard: open each station only while the event runs. Revoke a station whose code leaks, then rotate it.

Each request also costs your RPC endpoint up to about 45 lookups, and anyone can send one. Use an endpoint whose rate limit or plan covers a scripted burst, or put your own rate limit in front of the route.

Where next

On this page