Skip to main content
In addition to automatic scenarios (based on the card’s last-4 digits or PIX/boleto amount), the sandbox dashboard lets you manually force the outcome of a payment or a chargeback. This is the most practical way to test specific states on demand.
These actions are performed in the sandbox dashboard (not via the public API with x-api-key). Use them to unlock the state you want to observe in your API/webhook integration.

​
Configure PIX and boleto settlement

Under Sandbox → Settings, define the settlement mode per payment method:
  • PIX and boleto, each with mode instant, auto (with a delay of 0 to 60 minutes), or manual.
See what each mode does in PIX and boleto testing.

​
Simulate a payment

On the detail page of a transaction/payment waiting (PIX/boleto in waiting_payment), use “Simulate Payment” to force an outcome:
ActionEffect
PayMarks the payment as paid (triggers transaction.paid, releases split/wallet).
RefuseMarks as refused.
FailMarks as failed.
Open dispute (in_protest)On a paid card payment, opens a chargeback and triggers the real dispute flow.
Each action goes through the same production pipeline (events, webhooks, balance updates) — only the trigger is manual.

​
Simulate a chargeback

To test the dispute flow end to end:
  1. Make an approved payment with a card.
  2. Open the dispute: use “Open dispute” on the payment (or use an amount ending in 31). This creates the chargeback and debits the wallet.
  3. Submit the defense documents (standard chargeback flow).
  4. Force the outcome in the dashboard: won (won) or lost (lost).
See the full flow in Chargebacks.
For automation (E2E tests), prefer deterministic scenarios: card last-4 digits for approval/refusal and amounts ending in 07/17/27/31 for PIX/boleto/chargeback — so you don’t rely on dashboard clicks.