Skip to content
Create account
or
Sign in
The Stripe Docs logo
/
Ask AI
Create account
Sign in
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Developer tools
Get started
Payments
Finance automation
Get started
Payments
Finance automation
Platforms and marketplaces
Money management
Overview
About Stripe payments
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseManaged Payments
Use Payment Links
Build a checkout page
Build an advanced integration
Build an in-app integration
Payment methods
Add payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Elements
Payment scenarios
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
Other Stripe products
Financial Connections
    Overview
    Get started
    Use cases
    Fundamentals
    Testing
    Supported institutions
    Collect accounts for data
    ACH Direct Debit payments
    Connect payouts
    Other data-powered products
    Access account data
    Balances
    Ownership
    Transactions
    Manage accounts
    Disconnections
    Webhooks
Crypto
Climate
HomePaymentsFinancial Connections

Test Financial Connections

Learn how to test your integration with simulated Financial Connections accounts.

Copy page

Get started using a sandbox

Testing other Stripe APIs

Refer to the testing documentation to learn more about testing your Stripe integration.

To test Financial Connections, follow the relevant use case guide using a sandbox and its associated test API keys. Accounts and customers that you make in a sandbox are invisible to your live mode integration.

Note

The Financial Connections authentication flow is subject to change, so we don’t recommend automated client-side testing. Usage of Stripe’s API with sandbox test keys is also strictly rate limited, which you must account for in your tests.

How to use test accounts and institutions
Server-side

When you provide Stripe.js with a Financial Connections Session token created using sandbox test keys, the authentication flow exclusively shows a selection of test institutions managed by Stripe. The client can link accounts from any of these institutions without providing credentials.

Features like balances, account ownership, and transactions work the same way as they do in live mode, except they return testing data instead of real account data.

Sandbox webhooks are separate from live webhooks. Learn about testing your webhook integrations.

Testing different user authentication scenarios
Client-side

Stripe provides a set of test institutions exercising different success and failure scenarios, each represented as a bank in the list of featured institutions.

Simulating successful authentication

  • Test Institution: Simulates the user successfully logging into their institution and contains a basic set of test accounts.
  • Test OAuth Institution: Contains the same test accounts as Test Institution, but instead of authenticating directly with the modal, it opens an OAuth popup for authentication.
  • Ownership Accounts: Contains test accounts representing different ownership states.
  • Sandbox Bank (OAuth): Provides a test institution OAuth popup that allows you to select accounts to link. Sandbox Bank is the most representative of account linking for the majority of live mode institutions.
  • Sandbox Bank (Non-OAuth): Provides a Stripe-hosted login form to simulate institutions that don’t support OAuth. Use the following test credentials to proceed:
    • The initial prompt asks for username and password. Entering any input value simulates a successful login.
    • In the password field or any subsequent field, enter options (selection from a list), mfa (one-time passcode entry), confirm_mfa (one-time passcode confirmation), or security_question (secret answer entry) to exercise further login prompts.
    • Entering error in any field ends the login session; incorrect gives you a chance to try again.
  • Invalid Payment Accounts: Contains test accounts that are unusable for ACH payments.

Simulating failed authentication

  • Down Bank (Scheduled): The institution’s login API is unavailable for a known time period that the institution communicated to Stripe.
  • Down Bank (Unscheduled): The institution’s login API is unavailable without any information about the downtime communicated to Stripe.
  • Down Bank (Error): Stripe is experiencing an unknown error communicating with the institution.

Note

We recommend manually testing OAuth and non-OAuth institutions to make sure that both UI flows work within the context your application. See additional documentation about the differences between OAuth and non-OAuth connections.

Was this page helpful?
YesNo
Need help? Contact Support.
Join our early access program.
Check out our changelog.
Questions? Contact Sales.
LLM? Read llms.txt.
Powered by Markdoc