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-Policyresponse header issame-origin-allow-popups,restrict-properties, orunsafe-none. Using a restrictive value such assame-originmight interfere with OAuth bank login flows. If your page doesn’t set aCross-Origin-Opener-Policyheader, it defaults tounsafe-none.Configure the page that launches the authentication flow with a referrer policy that sends a
Refererheader to other origins. Either don’t send aReferrer-Policyresponse header or use a value such asorigin,origin-when-cross-origin,strict-origin, orstrict-origin-when-cross-origin. Usingno-referrersuppresses theRefererheader and might interfere with OAuth bank login flows.If your page contains a
<meta name="referer" />tag, set itscontentvalue to one oforigin,origin-when-cross-origin,strict-origin, orstrict-origin-when-cross-origin.If the page that launches the authentication flow is displayed inside an
iframe, includeallow-popups-to-escape-sandboxin thesandboxproperty. Some OAuth flows don’t work inside a sandboxediframe, so using a more restrictiveallow-popupsvalue breaks them. See the MDNiframedocumentation 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.