Testing Stripe Connect

Use testing to make sure your Connect integration handles different flows correctly. Use test mode to simulate live mode while taking advantage of Stripe-provided special tokens to use in your tests. Take a look at our payments testing guide for more information on testing charges, disputes, and so on.

Create test accounts

You can create multiple test accounts and use any account type or controller properties you might need (for example, representing multiple countries).

You can create test accounts using the Accounts API or in the Stripe Dashboard.

Use 000-000 as the SMS code when prompted for test accounts.

Test the OAuth flow

You can test your OAuth integration with connected accounts that use a Stripe-hosted dashboard using your test mode client_id.

Your test mode client_id is ca_FkyHCg7X8mlvCUdMDao4mMxagUfhIwXb. You can find this in your Connect OAuth settings.

Your test mode 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 (Stripe Dashboard accounts only)
• Get test access tokens for connected accounts

To test the OAuth flow, create a new account after clicking the OAuth link. You can also test connecting an existing Stripe account only if the email is different from your platform account.

Identity verification

After creating a test connected account, you can use tokens to test different verification statuses to make sure you’re handling different requirements and account states. You can use the following tokens to test verification with test accounts.

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. You must pass in legitimate values for the city, state, and postal_code arguments.

Test personal ID numbers

Use these personal ID numbers for individual.id_number or the id_number attribute on the Person object to trigger certain verification conditions.

Test identity documents

For testing, use file tokens instead of uploading your own test IDs. For details, refer to Uploading a file.

Test file tokens

Use these file tokens to trigger certain identity verification conditions.

Business information verification

Business address validation

In some countries, the business address associated with your connected account must be validated before charges, payouts, or both can be enabled on the connected account.

Test business addresses

Use these addresses for line1 to trigger certain validation conditions. You must pass in legitimate values for the city, state, and postal_code arguments.

Make sure you start with an address token that has the least permissive validation condition you want to test for. This is because you can’t use an address token that has a more restrictive validation condition than the previous token used. For example, if you provided address_full_match to have both charges and payouts enabled, you can’t disable payouts or charges afterward by changing the token to an invalid one. You can work around this by creating a new account with the relevant token.

Test business tax IDs

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

Test directorship verification

Stripe performs directorship verification by comparing the list of directors on the Account object against a list retrieved from local registries. If the country requires it, you can trigger verification for an Account object by using these tokens for the person.first_name attribute and setting the person.relationship.director attribute to true.

The verification errors can trigger if multiple directors on the Account object use these magic tokens.

Test company name verification

Trigger company name verification for an Account object by using this token for the company.name attribute.

Test statement descriptor verification

Trigger statement descriptor verification for an Account object by using this token for the settings.payments.statement_descriptor attribute.

Trigger statement descriptor prefix verification for an Account object by using this token for the settings.payments.statement_descriptor_prefix attribute.

Test business URL verification

Trigger URL verification for an Account object by using this token for the business_profile.url attribute.

Test Doing Business As (DBA) verification

Trigger DBA verification for an Account object by using this token for the business_profile.name attribute.

Test product description verification

Trigger product description verification for an Account object by using this token for the business_profile.product_description attribute.

Test capability disabled reasons

Trigger assignment of a specific requirements.disabled_reason to all of an Account object’s inactive Capability objects by using this token for the account’s business_profile.url attribute.

Trigger or advance verification

Trigger cards

Use these card numbers to trigger various conditions when you’re testing both requirements and tiered verification. For the trigger actions to work, you must use these cards with a Connect charge by setting on_behalf_of, or creating the charge directly on the connected account.

Trigger next requirements

Live mode can require additional verification information when a connected account processes a certain amount of volume. This card sets any additional verification information to be required immediately. If no additional information is required, nothing appears.

Trigger a charge or payout block

If required information isn’t provided by the deadline, Stripe disables the connected account’s charges or payouts. These cards disable the connected account and move any currently due requirements to overdue. These cards have no effect until an account provides the initial information that’s required to enable charges and payouts.

Trigger bank account ownership verification

Connected accounts in the United States and India are subject to Bank account ownership verification. You can complete this verification by uploading supporting documents with the Connect Dashboard or with the API through the documents[bank_account_ownership_verification] hash.

In test mode, you can simulate the US bank account ownership verification process. Use the following test bank account numbers to trigger the verification process. One number presumes successful verification and the other prompts you to upload test images or file tokens to complete the verification process. These test accounts are only available for US accounts.

Simulate requirements

If your platform has connected accounts in different countries or plans to, you might need to verify a person’s address as well as their identity (depending on the country). Stripe provides a sample date of birth (DOB) and sample addresses to test for this requirement.

Add funds to Stripe balance

To test adding funds to your Stripe balance from a bank account in the Dashboard, enable test mode and select the desired test bank account in the drop-down menu within the Add to balance dialog. You can simulate success or failure due to insufficient funds.

To test adding funds in the API, use the following test bank tokens as the source while in test mode. Each token simulates a specific kind of event.

Payouts

Use the following test bank and debit card numbers to trigger certain events during payout testing. You can only use these values in test mode with test secret keys.

Test mode payouts simulate a live payout but aren’t processed with the bank. Test mode accounts with Stripe Dashboard access always have payouts enabled, as long as valid external bank information and other relevant conditions are met, and never requires real identity verification.

Bank numbers

Use these test bank account numbers to test payouts. You can only use them with test secret keys.

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.