Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
OverviewAccept a paymentUpgrade your integration
Online payments
OverviewFind your use case
Use Payment Links
Use a prebuilt checkout page
Build a custom integration with Elements
Build an in-app integration
Use Managed Payments
Recurring payments
In-person payments
Terminal
Payment methods
Add payment methods
Manage payment methods
Faster checkout with Link
Payment operations
Analytics
Balances and settlement time
Compliance and security
Currencies
Declines
Disputes
Radar fraud protection
Payouts
ReceiptsRefunds and cancellations
Advanced integrations
Custom payment flows
Flexible acquiring
Off-Session Payments
Multiprocessor orchestration
Beyond payments
Incorporate your company
Crypto
Agentic commerce
Machine payments
Financial Connections
    Overview
    Get started
    Use cases
    Fundamentals
    Testing
    Supported institutions
    Deployment checklist
    Collect accounts for data
    ACH Direct Debit payments
    Connect payouts
    Other data-powered products
    Access account data
    Balances
    Ownership
    Transactions
    Ownership match
    Manage accounts
    Relink
    Tokenized account numbers
    Disconnections
    Webhooks
Climate
Verify identities
United States
English (United States)
  1. Home/
  2. Payments/
  3. Financial Connections

Deployment checklist

Use this checklist before deploying your Financial Connections integration.

When integrating with Financial Connections on the web, refer to this checklist to ensure your users can use the authentication flow without issue.

  • Configure the page that launches the authentication flow so that the Cross-Origin-Opener-Policy response header is same-origin-allow-popups, restrict-properties, or unsafe-none. Using a restrictive value such as same-origin might interfere with OAuth bank login flows. If your page doesn’t set a Cross-Origin-Opener-Policy header, it defaults to unsafe-none.

  • Configure the page that launches the authentication flow with a referrer policy that sends a Referer header to other origins. Either don’t send a Referrer-Policy response header or use a value such as origin, origin-when-cross-origin, strict-origin, or strict-origin-when-cross-origin. Using no-referrer suppresses the Referer header and might interfere with OAuth bank login flows.

    If your page contains a <meta name="referer" /> tag, set its content value to one of origin, origin-when-cross-origin, strict-origin, or strict-origin-when-cross-origin.

  • If the page that launches the authentication flow is displayed inside an iframe, include allow-popups-to-escape-sandbox in the sandbox property. Some OAuth flows don’t work inside a sandboxed iframe, so using a more restrictive allow-popups value breaks them. See the MDN iframe documentation for a full description of these values.

  • Before enabling live traffic, test your integration using a sandbox. Use each of the Test (OAuth), Test (Non-OAuth), Bank (OAuth), and Bank (Non-OAuth) institutions to link accounts.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Chat with Stripe developers on Discord.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc