Testing topics:

• Payouts
• Creating accounts
• OAuth
• Testing Top-ups
• Test keys
• Identity verification

Testing payouts

For Express and Custom accounts, use the following test bank and debit card numbers to trigger certain events during testing of payouts. These values can only be used when creating or updating Custom accounts via the API in test mode or with Express in test mode.

To create test mode payouts for a Standard Stripe account, use any valid bank account details (e.g., your own). Test mode payouts simulate a live payout but are not processed with the bank.

Test mode always has payouts enabled, as long as valid external bank information and other relevant conditions are met, and never requires real identity verification or other interactive steps that are part of the Custom account workflow.

Bank numbers

Debit card numbers

Use these test debit card numbers to test payouts to a debit card. These can only be used with test secret keys.

Creating accounts

You can create any type of test account you need: Standard, Express, or Custom. You can also create multiple test accounts, e.g., representing multiple countries.

To test the OAuth flow for connecting another account, create a new Stripe account using another email address and then take that new account through the OAuth flow. This works for both Standard and Express accounts.

To test Express accounts without providing a real phone number, use 000 000 0000 as the phone number and 000-000 as the SMS code when prompted.

You can create Custom test accounts using the code on the Custom Accounts page. The account does not need to be activated because it can’t be used for live charges.

Using OAuth

To easily test an OAuth integration, the development client_id allows you to:

• Set your redirect_uri to a non-HTTPS URL
• Set your redirect_uri to localhost
• Force-skip the account form instead of having to fill out an entire account application (Standard accounts only)
• Get test access tokens for connected users

You’ll be able to find your development client_id in your platform settings.

Testing Top-ups

To test Top-ups in the Dashboard, enable test mode and select the desired test bank account in the drop-down menu within the top-up dialog. You can simulate a successful top-up or a top-up that fails due to insufficient funds.

To test Top-ups in the API, use the following test bank tokens as the top-up source while in test mode. Each token simulates a specific kind of event.

Generating test keys for live applications

When using an access_token derived via the OAuth flow, you can only generate test access tokens using a development client_id, but may generate either live or test access tokens using a production client_id.

To generate a test access token for a production client_id, use a refresh_token:

curl https://connect.stripe.com/oauth/token \
  -d client_secret=sk_test_4eC39HqLyjWDarjtT1zdp7dc \
  -d refresh_token=REFRESH_TOKEN \
  -d grant_type=refresh_token

Note that it’s still preferable to authenticate using the Stripe-Account header, not an access token.

Identity and address verification

When creating test accounts that use Identity Verification, providing any image results in the user being verified (whether the image is of an ID or not). Alternatively, for testing Custom accounts only, Stripe created two sample images you can use instead of uploading your own test IDs. These images do not work for testing Express accounts.

• A verified image that causes the user to be automatically marked verified
• An unverified image that causes the user to be automatically marked unverified

For details, refer to Uploading a file.

If your platform has connected accounts in different countries or plans to, depending on the country, you might need to verify a person’s address as well as their identity. Stripe provides a sample date of birth (DOB) and sample addresses so that you can test for this requirement. For testing purposes, you can use the aforementioned verified and unverified images for the verification.document and verification.additional_document fields. Below is a listing of events you can simulate.

• A verified date of birth and verified address that causes the user to be marked as verified.
• A verified date of birth and unverified address that causes the user to be marked as unverified and verification.additional_document becomes required. You can view the requirement with the currently_due array.
• An unverified date of birth and verified address that causes the user to be marked as unverified and verification.document becomes required. You can view the requirement with the currently_due array.
• An unverified date of birth and unverified address that causes the user to be marked as unverified and both verification.document and verification.additional_document become required. You can view these requirements with the currently_due array.

Trigger cards

Use these card numbers on a charge to trigger various conditions when testing tiered verification.

Test dates of birth

Use these dates of birth (DOB) to trigger certain verification conditions.

Test addresses

Use these addresses for line1 to trigger certain verification conditions.

Test personal ID numbers

Use these personal ID numbers for individual[id_number] to trigger certain verification conditions. You can also use these values for the id_number attribute on the Person object.

Test business tax IDs

Use these business tax ID numbers for company[tax_id] to trigger certain verification conditions.