Decode a Pix QR Code (EMV)
Decodes a PIX QR Code EMV string and returns the beneficiary details without executing payment.
Use this endpoint to display QR Code information to the user before confirming payment. The decoded data includes beneficiary name, document, bank info, amount, and PIX key.
After reviewing the decoded data, use
POST /v1/accounts/{accountId}/pix/out/qr-code/async to execute the payment
(the synchronous /pix/out/qr-code is deprecated).
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Optional client-generated idempotency token (recommended for safe retries).
Unix seconds. Required on the signed host; tolerance is 300s either way (403 request_timestamp_skew).
Lowercase hex SHA-256 of the body. An empty body hashes the empty string, so the header is always present. Mismatch returns 400 body_hash_mismatch.
Detached JWS (<protected>..<signature>, ES256 or PS256) over METHOD\nPATH?QUERY\nTIMESTAMP\nIDEMPOTENCY_KEY_OR_EMPTY\nX_CONTENT_SHA256.
Request
The EMV string from the QR Code (copy and paste content).
Response
PIX key of the beneficiary (email, phone, CPF/CNPJ, or EVP).
Payment amount in BRL. May be 0 for static QR Codes without a predefined value.
For dynamic-due-date, this is the final value to pay (originalAmount - discount - deduction + interest + penalty).
Original face value of the QR before discount/interest/penalty are applied. For static and dynamic-immediate this equals amount.
Reusable decode identifier. Same value as decodeId. Can be sent as decodeId in POST /v1/accounts/{accountId}/pix/out/qr-code/async (or the deprecated sync /pix/out/qr-code) to skip a second decode round-trip.
Alias of identifier, preserved for backward compatibility.
Numeric type id returned by the partner (kept for parity with raw payloads).
Whether the payer can modify the payment amount (dynamic-immediate only). Always present; false for variants where the partner does not return it.
Free-text payment message embedded in the QR (when present).
Trade / fantasy name of the beneficiary (typically populated for dynamic-due-date invoices).
Canonicalised account type of the beneficiary. Other values may appear in upper snake-case if the partner introduces new types.
Discount amount to subtract from originalAmount (only dynamic-due-date).
Deduction amount to subtract from originalAmount (only dynamic-due-date).
Interest amount to add to originalAmount (only dynamic-due-date).
Late-payment penalty amount to add to originalAmount (only dynamic-due-date).
Due date of the charge in ISO 8601 / RFC 3339 (YYYY-MM-DD or full datetime, only dynamic-due-date).
Last accepted payment date (grace period after dueDate). Only dynamic-due-date.