[DEPRECATED] Pay a Pix QR Code (via EMV, sync)
[DEPRECATED] Pay a Pix QR Code (via EMV, sync)
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Client-generated idempotency token.
Transaction PIN of the operator in X-Acting-Document. Required on cashout routes when the credential enforces a PIN (428 pin_required).
Real IP of the end user, for integrator credentials calling on their behalf. This is the IP evaluated against cashoutSourceIps — without it the check would see your server’s IP. Ignored for delegated credentials, where the connection IP is already the right one.
Request
Source account identifier (UUID).
PIX QR Code EMV string (“copy and paste” field). Starts with “00020126” and contains encoded recipient data.
Payment amount in BRL. Max 2 decimal places (e.g., 150.75 for R$150,75).
- Required for static QR Codes without defined value
- Optional for dynamic QR Codes (will be validated against QR value)
Payment description (for internal use).
Client-side reference for reconciliation. Echoed back on the payment, in the statement and in pix.out.* webhooks. Also the key used by the Location header of the async variant.
Response
PIX payment via QR Code accepted/executed.
Internal payment intent identifier (tracking/reconciliation).
Canonical status:
COMPLETED- settled (HTTP 200)FAILED- rejected (HTTP 422; seeerrorCode/errorReason)TIMEOUT- indeterminate; request reached the partner (HTTP 202; check the statement before retrying)PENDING/PENDING_APPROVAL/PROCESSING- not terminal yet (HTTP 202)
Business identifier (client-provided or auto-generated UUID).
BACEN end-to-end PIX identifier (present once settled).
Error code (present when FAILED).
Error reason (present when FAILED).
Completion timestamp (UTC).
Present on indeterminate (TIMEOUT) results.