[DEPRECATED] Pay a Pix QR Code (via EMV, sync)
[DEPRECATED] Pay a Pix QR Code (via EMV, sync)
DEPRECATED: prefer POST /v1/accounts/{accountId}/pix/out/qr-code/async,
which returns 202 immediately and delivers the final result via webhook.
This synchronous endpoint remains functional for backward compatibility and
returns Deprecation: true, Sunset and Link headers. Planned sunset:
2026-11-21.
Pays a PIX QR Code using the EMV string (copy and paste).
For static QR Codes without a predefined value, the amount field is required.
For dynamic QR Codes with a predefined value, the amount field is optional
(if provided, it will be validated against the QR Code value).
Balance verification: The system automatically checks if there is sufficient available balance before executing the transfer.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Headers
Client-generated idempotency token.
CPF of the human performing the operation. Required on cashout routes when the credential enforces a transaction PIN. On a company P2P profile contact, this CPF is the holder who signs; it is not taken from the body.
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.
Optional user-agent of the end user’s browser or app, for integrator credentials calling on their behalf. Feeds risk analysis only: an invalid or oversized value is dropped and the payment still proceeds. Ignored for delegated credentials.
Optional device fingerprint or identifier from the integrator’s own system. Risk analysis only; never required and never a reason to reject the payment. Ignored for delegated credentials.
Optional session id of the end user in the integrator’s system. Risk analysis only; never required and never a reason to reject the payment. Ignored for delegated credentials.
Optional latitude,longitude in decimal degrees. Out of range or malformed values are dropped. Risk analysis only. Ignored for delegated credentials.
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
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.