Docs

How QR Payments Work

A step‑by‑step guide to the QR payment flow: generation, scan, auth, settlement, and notifications.

1) Generate a QR

Operator requests a payment session: amount, currency, reference, and expiry. A short‑lived, signed payload is encoded in a QR.

2) Scan & Authenticate

The player scans with a supported wallet/bank app. The app displays details and prompts for Face/Touch ID or passcode.

3) Execute & Settle

On approval, funds move and a receipt/ID is issued. Timing varies by rail, but UX targets near‑instant confirmation.

4) Webhook Notify

Our webhook notifies the operator backend. Balances are credited and the player can start or continue play.

Error Handling

  • Expired QR: regenerate with a fresh expiry.
  • Insufficient funds: present retry guidance.
  • User cancels: session closed, no funds moved.

Best Practices

  • Always show amount, payee, and expiry visibly.
  • Use short‑lived tokens and strict scopes.
  • Persist event logs for reconciliation and disputes.