Scan And QR API
QR payloads are typed, signed, expiring, and one-time when required. Scan payloads never move money without explicit user confirmation, eligibility checks, and transaction recording.
Endpoints
| Endpoint | Method | Auth | Headers | Notes |
|---|---|---|---|---|
Create scan payload/scan/api/v1/payloads/Create a payment, receipt-verification, giftcard, deposit, withdrawal, or crypto-address QR payload. |
POST | User JWT Authenticated caller |
Authorization: Bearer <user-jwt>Content-Type: application/json |
Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |
Resolve scan payload/scan/api/v1/resolve/Inspect a QR payload before executing it. |
POST | User JWT Authenticated caller |
Authorization: Bearer <user-jwt>Content-Type: application/json |
Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |
Execute scan payload/scan/api/v1/execute/Perform the typed scan flow through the financial engine. |
POST | User JWT Authenticated caller |
Authorization: Bearer <user-jwt>Content-Type: application/json |
Webhooks: wallet.debited, wallet.credited, giftcard.redeemed Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |