Testing

Pay-ins

You can test card payments using the sample test cards below to simulate different outcomes (e.g. successful or failed payments) in a sandbox environment.

Test cards act as fake credit cards, and allow you to simulate the following scenarios:

• Successful payments by card brand
• Card errors due to declines, fraud, or invalid data
• Authentication with 3D Secure

To use the test cards, manually enter the card info as follows:

• The card number listed in the table and the response code you want to test
• Any valid three-digit card verification value (CVV) for Visa and Mastercard cards, or four-digit CVV for American Express cards
• Any future card expiry date, in the format MM/YY or MM/YYYY
• Any valid 5-digit US zip code (e.g. 10001)

Default (non-3DS) cards and responses

3D Secure cards and responses

Use these test cards to simulate different 3D Secure (3DS) authentication flows and results.

You can use:

• Any valid three-digit CVV for Visa and Mastercard, or four-digit CVV for American Express
• Any future expiry date, in the format MM/YY or MM/YYYY

If your 3DS authentication test is challenged, and you're redirected to the 3DS simulator page, enter the password Checkout1!.

3DS2 Challenge Flow

Crypto

Sandbox uses the Polygon Amoy testnet (chain ID 80002) and Base Sepolia testnet (chain ID 84532) for crypto pay-ins. USDC is the supported test token - USDT is not available on Amoy.

Get test USDC from the Circle faucet and select the testnet you're using. The Polygon Amoy faucet dispenses the gas token (POL) only - not USDC.

There are two crypto pay-in flows, and they're tested differently.

Connected wallet (gas token required)

The customer connects an EVM wallet (e.g. MetaMask) and approves the transfer from within the wallet. Because the wallet broadcasts the on-chain transaction, it must hold a small amount of the network's gas token (POL on Polygon Amoy).

1. Set up a testnet wallet. Configure MetaMask (or any EVM wallet) for the testnet you're using.
2. Fund the wallet. Get test USDC from the Circle faucet, and get gas token (POL) from the Polygon Amoy faucet.
3. Create a payment page with crypto enabled in your sandbox environment.
4. Connect the wallet on the payment page and approve the transfer.
5. Breeze detects the on-chain transfer automatically and fires the PAYMENT_SUCCEEDED webhook once confirmed.

Manual deposit (no gas token required)

The payment page displays a Breeze-generated deposit address. You send test USDC straight to that address - there's no wallet to set up and no gas token to hold, because the faucet sends the funds on your behalf.

1. Create a payment page with crypto enabled in your sandbox environment.
2. Copy the deposit address displayed on the payment page. Breeze generates this address automatically - you do not configure one.
3. Send test USDC to that address using the Circle faucet - enter the deposit address as the recipient.
4. Breeze detects the on-chain transfer automatically and fires the PAYMENT_SUCCEEDED webhook once confirmed.

---

Payouts

Push-To-Card

Use the following test card for push-to-card payouts in the sandbox environment:

Bank accounts

If the payout page supports more than one rail or currency, a Choose destination step appears
first: the payer picks a country and then a payout currency, and that pair selects the rail whose
bank account form they then fill in. Which countries and currencies are offered comes from the
merchant's agreement, so a rail you want to test may not be listed. Pages that support a single
currency have no destination step - the rail follows from the page's own funding currency, so a
USDC-funded page reaches ACH and a EURC-funded one reaches SEPA.

Append ?locked_payout_methods=BANK_ACCOUNT to the payout page URL to isolate the bank flow.

Values below pass validation in the sandbox. Bank name fields are a searchable list on the page, so
pick any entry rather than typing one.

ACH - USD, United States

SEPA - EUR

GBP FPS - GBP, United Kingdom

HKD FPS - HKD, Hong Kong

KRW KFTC - KRW, South Korea

Zengin - JPY, Japan

TWD FISC - TWD, Taiwan

KYC

When testing payout flows that involve KYC in the sandbox environment, keep the following in mind. Tier 1 is required for card/bank payouts; Tier 2 is required for crypto payouts - see KYC Overview for the full breakdown.

Tier 1 KYC (Card / Bank payouts)

• Name fields - The name entered in the KYC form should match the firstName, middleName, and lastName in the corresponding Customer record.
• Date of birth - Use a date of birth for a user aged 18 or older. Year 2000 or earlier is a safe choice for sandbox testing. Note that this threshold is specific to the sandbox configuration.
• taxId - Use any 9-digit number for US-based testing. The sandbox checks format validity but does not verify the value against a real identity.

Tier 2 KYC (Crypto payouts)

All Tier 1 notes above apply. Additionally:

• When the camera prompt appears for the Government ID document scan, you may use any image - the sandbox does not perform real document authenticity checks.