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

📘

Breeze offers both fiat (card) and crypto (non-card) payment options, along with Apple Pay and Google Pay wallets. However, the guide below is for testing card payments.

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

📘

If the test card returns a failed payment response, the end user is presented with the following error message: "Payment failed. Please check your card details and balance, or try another card. If the issue persists, contact your bank or support."

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

Payouts

Push-To-Card

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.

⚠️

The hosted KYC form in sandbox may pre-populate with dummy values. Always overwrite these with values that are consistent with your Customer record before submitting.

📘

To keep testing clean, consider creating a fresh Customer record for each distinct test scenario rather than reusing the same one across multiple flows.