Skip to main content
Retrieve QR metadata and, when available, the latest transaction associated with it.

​
Endpoint

POST /v3/qr_code/details

​
Authentication and target

Use an account credential for its bound account, or a user credential with both X-ISPB and X-Account-Number. If an account credential sends those headers, both must be present and must match its bound account. Platform credentials are not accepted. All requests require the standard HMAC-SHA256 headers. The curl example below uses an ACCOUNT credential bound to the operated account, so it omits X-ISPB and X-Account-Number. If X-Client-ID identifies a USER credential, add both target headers and include their exact trimmed values in the canonical header set before calculating X-Signature.

​
Request body

​
Success data

qr_code_id, merchant_order_id, numeric qr_code_type, qr_code_memo, qr_code_payload_base64, numeric created_at, optional last_txn, and is_paid. last_txn contains numeric status/source enums, string amount/currency/IDs, parties, and numeric timestamps when populated.

​
Behavior and validation

A nil QR result or absent QR details currently becomes a successful empty data object rather than a documented not-found error. is_paid is true only when last_txn exists and its status is COMPLETED. Party documents may be masked. Known QR type values are 11 static, 12 dynamic instant, 13 dynamic expiry, and 14 composite.

​
Errors

Every call can fail for missing or invalid signature headers, an expired timestamp, nonce replay, an invalid body hash or signature, insufficient permission, or a downstream service error. Endpoint-specific errors include:
  • 4000 for a missing QR ID.
  • 501 for RPC transport failure.
  • Mapped domain errors including 4003003 for transaction-not-found behavior, and 4003008 for missing account context.

​
Example request

​
Example response