Testing

This page includes test card numbers, banking numbers, and other information to make sure your integration works as planned. Use it to trigger different flows in your integration and ensure they are handled accordingly.

Basic Test Card Numbers

ACH Debit Testing

The following table includes examples of well-known ABA routing numbers for ach_debit payment methods. The account_number can be any 4 or 17-digit number.

EFT Direct Debit Testing

The following table includes examples of well-known institution_id or Bank Codes for eft_debit payment methods. The account_number can be any 4 or 12-digit number and the transit_number can be any 5-digit number.

Simulating Charge Declines

The following exact amounts will result in the associated error code on a payment intent. This is only accessible for card. Example: 777701 = $7777.01.

Simulating Address Verification Responses

By default, all card transactions with valid billing_details addresses will pass the address verification checks. To simulate a different response, add a single letter code from the table below as a prefix to the billing_details.street property. Example: billing_details.street='11 123 Main Street' will produce failed checks where the address matches, but postal code does not. These checks are available on the payment_method.card.checks property.

Example:

billing_details.street is prefixed with 11 and therefore the card.checks.address_postal_code_=fail

 1{
 2  "id": "pm_7jzakGs4bVgTo82EDLZcS",
 3  "type": "card",
 4  "card": {
 5    "brand": "visa",
 6    "last4": "1111",
 7    "checks": {
 8      "cvc_check": "pass",
 9      "address_line1_check": "pass",
10      "address_postal_code_check": "fail"
11    },
12    "exp_year": 2026,
13    "exp_month": 8
14  },
15  "billing_details": {
16    "name": "John Doe",
17    "address": { 
18      "zip": "80302",
19      "street": "11 123 Main Street", // Note the '11' prefix
20      "country": "US"
21    }
22  },
23  ...
24}

Simulating CVC Responses

Webhooks

To test your integration, perform actions using the API (in test mode) to send legitimate events to your endpoint. For instance, creating a charge triggers the charge.succeeded event that contains the charge data. You can then use the API to verify the resulting event data.