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 more.
Create test accounts
You can create multiple test accounts and use any account type you might need (for example, representing multiple countries).
Advertencia
Don’t connect the platform account to itself—that fails to reflect the real world use of Connect, and makes debugging difficult.
You can create test accounts of all types through the API or Dashboard.
Use 000-000 as the SMS code when prompted for test accounts.
Test the OAuth flow Express accountsStandard accounts
You can test your OAuth integration for Express or Standard account creation with the development client_id.
Your development client_id is ca_FkyHCg7X8mlvCUdMDao4mMxagUfhIwXb; you’ll be able to find this in your Connect settings.
Your development client_id allows you to:
- Set your
redirect_urito a non-HTTPS URL - Set your
redirect_urito localhost - Force-skip the account form instead of having to fill out an entire account application (Standard)
- Auto-fill
000-000-0000as the test phone number and000-000as the SMS code when prompted (Express) - 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 the platform account.
Identity verification
After creating a test connected account, you can use tokens to test different verification statuses to ensure 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.
| DOB | Type |
|---|---|
1901-01-01 | Successful verification. Any other DOB results in unsuccessful verification. |
1902-01-1902 | Successful, immediate verification. The verification result is returned directly in the response, not as part of a webhook event. |
1900-01-01 | This DOB triggers an Office of Foreign Assets Control (OFAC) alert. |
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.
Nota
Currently, address verification is only required when requesting the card_payments capability for US connected accounts.
| Token | Type |
|---|---|
address_full_match | Successful verification. |
address_no_match | Unsuccessful verification. |
address_line1_no_match | Unsuccessful verification from partial address match. |
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.
| Number | Type |
|---|---|
000000000 | Successful verification. 0000 also works for SSN last 4 verification. |
111111111 | Unsuccessful verification (identity mismatch). |
222222222 | Successful, immediate verification. The verification result is returned directly in the response, not as part of a webhook event. |
Test identity documents
For testing Custom accounts, use test images or file tokens instead of uploading your own test IDs. For details, refer to Uploading a file. These images don’t work for testing Express accounts.
Test document images
You can use a verified image that causes the user to be automatically marked verified. You can use an unverified image that causes the user to be automatically marked unverified.
Test file tokens
Use these file tokens to trigger certain identity verification conditions.
| Token | Type |
|---|---|
file_identity_document_success | Uses the verified image and marks that document requirement as satisfied. |
file_identity_document_failure | Uses the unverified image and marks that document requirement as not satisfied. |
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.
Nota
Currently, business address validation is only required when requesting the card_payments capability for US connected accounts. Address tokens have no effect if you’re requesting legacy_payments because business address validation isn’t required.
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.
| Token | Type |
|---|---|
address_full_match | Both charges and payouts are enabled on the account. |
address_no_match | Only charges are enabled on the account. Since validation failed on the line1 attribute, it becomes listed again in the requirements hash. |
address_line1_no_match | Neither charges nor payouts are enabled on the account. Since validation failed, the address attributes become listed again in the requirements hash. |
Test business tax IDs
Use these business tax ID numbers for company.tax_id to trigger certain verification conditions.
| Number | Type |
|---|---|
000000000 | Successful verification. |
000000001 | Successful verification as a non-profit. |
100000002 | Successful verification as a Canadian Registered Charity. |
111111111 | Unsuccessful verification (identity mismatch). |
111111112 | Unsuccessful verification (tax ID not issued). |
222222222 | Successful, immediate verification. The verification result is returned directly in the response, not as part of a webhook event. |
Test directorship verification (Canada Only)
Trigger director verification for an Account object by using this token for the individual.first_name. attribute and setting the individual.relationship.director attribute to true.
| Token | Type |
|---|---|
mismatch_director | Unsuccessful verification of this director. |
Test company name verification
Trigger company name verification for an Account object by using this token for the company.name attribute.
| Token | Type |
|---|---|
mismatch_business_name | Unsuccessful verification due to mismatched business name. |
disallowed_name | Unsuccessful verification due to generic business name. |
match_name_relationships | Unsuccessful verification due to generic business name. |
match_name_only | Unsuccessful verification due to business name discrepancy. |
Test statement descriptor verification
Trigger statement descriptor verification for an Account object by using this token for the settings.payments.statement_descriptor attribute.
| Token | Type |
|---|---|
mismatch | Trigger an invalid_statement_descriptor_business_mismatch verification error. |
disallowed | Trigger an invalid_statement_descriptor_denylisted verification error. |
Trigger statement descriptor prefix verification for an Account object by using this token for the settings.payments.statement_descriptor_prefix attribute.
| Token | Type |
|---|---|
mismatch | Trigger an invalid_statement_descriptor_prefix_mismatch verification error. |
disallowed | Trigger an invalid_statement_descriptor_prefix_denylisted verification error. |
Test business URL verification
Trigger URL verification for an Account object by using this token for the business_profile.url attribute.
| Token | Type |
|---|---|
https://disallowed.stripe.com | Trigger an invalid_url_denylisted verification error. |
https://problem.stripe.com | Trigger an invalid_url_website_other verification error. |
https://missing.stripe.com | Trigger an invalid_url_website_business_information_mismatch verification error. |
https://mismatch.stripe.com | Trigger an invalid_url_website_business_information_mismatch verification error. |
https://accessible.stripe.com | Trigger a successful validation of the URL. |
https://inaccessible.stripe.com | Trigger an invalid_url_website_inaccessible verification error. |
Test Doing Business As (DBA) verification
Trigger DBA verification for an Account object by using this token for the business_profile.name attribute.
| Token | Type |
|---|---|
disallowed_dba | Trigger an invalid_business_profile_name_denylisted verification error. |
invalid_dba | Trigger an invalid_business_profile_name verification error. |
Test product description verification
Trigger product description verification for an Account object by using this token for the business_profile.product_description attribute.
| Token | Type |
|---|---|
require_url | Trigger an invalid_url_web_presence_detected verification error. |
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.
| Number | Token | Type |
|---|---|---|
| 4000000000004202 | tok_visa_triggerNextRequirements | Changes the next set of eventually due requirements to currently due. |
| 4000000000004210 | tok_visa_triggerChargeBlock | Triggers a charge block. |
| 4000000000004236 | tok_visa_triggerPayoutBlock | Triggers a payout block. |
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
In some countries, Express and Custom accounts 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.
To test the US bank account ownership verification process, use the following test bank account number while in test mode. In test mode, you can upload test images or file tokens to complete the verification process. Currently, a test account with available ownership verification is available only in the US.
| Routing | Account | Type |
|---|---|---|
110000000 | 000999999991 | Triggers the bank account ownership verification process after a short delay |
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.
| Information provided | Person verification status | requirements[currently_due] |
|---|---|---|
| Verified date of birth and verified address | Verified | None |
| Verified date of birth and unverified address | Unverified | verification.additional_document |
| Unverified date of birth and verified address | Unverified | verification.document |
| Unverified date of birth and unverified address | Unverified | verification.additional_document, verification.document |
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.
| Token | Type |
|---|---|
btok_us_verified | Successful |
btok_us_verified_noAccount | Unsuccessful with a no_account code |
btok_us_verified_accountClosed | Unsuccessful with an account_closed code |
btok_us_verified_insufficientFunds | Unsuccessful with an insufficient_funds code |
btok_us_verified_debitNotAuthorized | Unsuccessful with a debit_not_authorized code |
btok_us_verified_invalidCurrency | Unsuccessful with an invalid_currency code |
Payouts Express accountsCustom accounts
For Express and Custom accounts, use the following test bank and debit card numbers to trigger certain events during payouts testing. You can only use these values in test mode with test secret keys.
To create test mode payouts for a Standard account, use any valid bank account details (for example, your own). Test mode payouts simulate a live payout but aren’t processed with the bank. Test mode Standard accounts 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.