Schedule Pix QR Code payment (async)
Schedule Pix QR Code payment (async)
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.
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.