Skip to main content
POST

Authorizations

Authorization
string
header
required

Keycloak JWT. Roles: admin (platform admin — can register merchants, act on behalf of any merchant), merchant (dashboard user — scoped to their own merchant_id via user attribute mapper), POS terminals use client credentials flow with merchant_id injected via protocol mapper.

Body

application/json

Request body for counter-initiated (reverse QR) payment. counter_id is required and validated server-side to confirm it belongs to the authenticated merchant.

scan_token
string<uuid>
required

Token read from the user's QR code (currently equals the user's wallet ID).

Example:

"8566959d-f366-45d9-9e6e-241ba189988f"

counter_id
string<uuid>
required

POS terminal identity — must belong to the authenticated merchant.

Example:

"c1d2e3f4-a5b6-7890-abcd-ef1234567890"

amount
number<double>
required
Required range: x >= 0.01
Example:

35.5

currency
string
default:USD
Example:

"USD"

description
string
Example:

"Lunch combo"

expires_in
integer
default:300

Seconds until approval expires (default: 300 — 5 minutes)

Required range: x >= 30
Example:

300

reference
string | null

Merchant's own order or invoice ID.

Example:

"ORD-9001"

callback_url
string<uri> | null

Per-intent webhook override URL.

Example:

"https://pos.example.com/webhooks/ORD-9001"

metadata
object | null

Arbitrary JSON metadata forwarded verbatim in the webhook payload.

Example:

Response

Payment intent created — awaiting user approval on mobile app

success
boolean
Example:

true

payment_intent
object