https://api.sandbox.pagou.ai). The
values below let you validate approvals, refusals, 3DS, and asynchronous Pix/Boleto settlement end
to end without moving real money.
These values only work in sandbox. Production outcomes depend on the real payment attempt. Keep
sandbox and production credentials, webhooks, and base URLs separate (see Environments).
Pix, Boleto and Voucher
A Pix/Boleto/Voucher charge is created aswaiting_payment (with a QR code or barcode). The sandbox
settles it to paid 15 seconds after the QR code / barcode is generated when the charge is
eligible. Eligibility is decided by the payer document, or — when no document is sent — by the amount:
Any other amount (without an approved document) stays
pending and never settles — use this to test
your pending/expiration handling.
1
Create the charge
Send a Pix, Boleto, or Voucher charge with one of the eligible combinations above.
2
Show the QR code / barcode
The response returns a scannable Pix EMV (copia e cola) or a Boleto barcode in
waiting_payment.3
Wait ~15 seconds
The sandbox confirms eligible charges and fires the
payment.confirmed webhook; the transaction
moves to paid.Credit card
Any payer information is accepted. The final status is decided by the card number — use any future expiry and any CVV unless noted below.3DS Challenge
The 3DS Challenge card returnsthree_ds_required with a next_action. Complete the challenge
in the Payment Element (or the sandbox challenge endpoint); on success the transaction settles to
paid, on failure to refused. See
Three-D Secure for the browser flow.
3DS Frictionless
The 3DS Frictionless card authenticates without a challenge and is approved directly — use it to verify the no-challenge happy path.Verifying the result
Always trust the webhook, not the synchronous response, as the source of truth:- Pix/Boleto/Voucher →
payment.confirmed~15s after creation (eligible charges). - Card approved →
captured; declined →refused.