Skip to main content
The sandbox is an isolated testing environment, identical to production in terms of the API contract, but that does not move real money. Instead of real acquirers, it uses a simulated provider (FakeProvider) that decides the outcome of each payment in a deterministic way — you choose whether a payment will be approved, declined, or left pending.

Test cards

Which card numbers pass, which fail — and a valid card generator.

PIX and boleto

Control settlement: pay instantly, after X minutes, or manually.

Simulate events

Force manual payment and chargeback from the dashboard.

Test script

A step-by-step walkthrough covering approval, decline, PIX, refund, and chargeback.

​
How to access

  1. Log in to the production Dashboard and click “Testing environment”.
  2. Grab your sandbox credentials from the credentials section.
  3. Point your integration to the sandbox URLs:
ServiceBase URL
API (PSP)https://api.sandbox.z2pay.com
Checkout APIhttps://checkout-api.sandbox.z2pay.com
Hosted pageshttps://pay.sandbox.z2pay.com
See details in Environments.

​
Principle: everything is deterministic

Unlike a real gateway (where the outcome depends on the card issuer), in the sandbox you control the result:
MethodHow the outcome is determined
CardBy the last 4 digits of the card number. E.g.: ...1002 = declined, ...1111 = approved.
PIX / boletoBy the settlement configuration per method (instant/auto/manual) and, optionally, by amount (magic cents).
ChargebackBy amount (paid card ending in 31) or manually from the dashboard.
In the sandbox, the CVV is ignored for cards — what matters is the last-4. In production, the CVV is validated normally by the acquirer.
Since the amount’s cents can trigger PIX/boleto/chargeback scenarios, when testing cards use “round” amounts (ending in 00) to avoid accidentally triggering an unintended scenario.