Testing with Connect

Testing topics:

• Payouts
• Creating accounts
• OAuth
• 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.

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

Test mode always has payouts enabled, and never require 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 deferred account creation flow, create a standard account using another email address you control or a dummy email address such as me+123@example.com.

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 demonstrated in the quickstart.

As the connected account will not be used for live charges, the account does not need to be activated.

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
• Get test access tokens for connected users

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

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_BQokikJOvBiI2HlWgH4olfQ2 \
   -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 verification

When creating test accounts that use Identity Verification, providing any image results in the user being verified. Alternatively, Stripe created two special images you can use instead of your own:

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

Complete file upload instructions are available on the Identity Verification page.

Trigger cards

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

Test date of birth

Use this magic DOB to trigger a certain verification condition.

Test personal ID numbers

Use these magic personal ID numbers—for legal_entity[personal_id_number]—to trigger certain verification conditions.

Test business tax IDs

Use these magic business tax ID numbers—for legal_entity[business_tax_id]—to trigger certain verification conditions.