Test data and magic values
In a sandbox, payments go through a simulated connector: no money moves, and the outcome depends only on the amount you send. You can test every path, failures and payments that stay pending included, without waiting for a real provider.
Magic values
The connector reads the last two digits of amount_cents (the amount in cents). For example, 1,250.00 MZN sent as 125000 ends in 00 and confirms at once; 125009 stays pending.
| Last two cents | Example (amount_cents) | Outcome | Requires sandbox advance | Description |
|---|---|---|---|---|
00 | 125000 | confirmed | No | Payment confirms immediately and triggers confirmation webhooks. |
02 | 125002 | failed | No | Payment fails immediately with a simulated decline. |
05 | 125005 | expired | No | Payment session expires without settlement. |
09 | 125009 | pending | Yes | Payment stays pending until advanced via sandbox advance. |
any other | 125013 | confirmed | No | Any other cent suffix defaults to immediate confirmation. |
Each outcome produces the same events as a real payment: a confirmed payment sends payment.received and, when it settles the invoice, invoice.paid.
Advance pending payments
A payment ending in 09 stays pending until you advance it. With no options the CLI confirms every pending payment in the sandbox; --payment and --outcome pick one payment and its outcome.
gotactl sandbox advance
gotactl sandbox advance --payment pay_7QmXc2Lk9ZtR4wYb --outcome expiredTrigger events
To test your webhook receiver without setting up the scene by hand, the CLI creates the sandbox data that produces these events:
| Event | Command |
|---|---|
customer.created | gotactl events trigger customer.created |
account.created | gotactl events trigger account.created |
invoice.issued | gotactl events trigger invoice.issued |
invoice.paid | gotactl events trigger invoice.paid |
payment.received | gotactl events trigger payment.received |
reading.accepted | gotactl events trigger reading.accepted |
webhook.test | gotactl events trigger webhook.test |