Production access

Once all required endpoints pass validation, a Request Production Access button becomes available in the Dashboard.

After you submit a production request, Plaid will:

• Perform a final configuration review
• Recheck your OAuth and data flows
• Confirm your institution branding
• Coordinate production timing with your team

Your integration will not be visible to end users until your team confirms the launch timing.

For platform integrations, you do not need to request production access for each institution separately. Submit each new institution as a new integration in the Dashboard, and Plaid will review and approve it before enabling production traffic.

Stealth testing allows you to run production traffic under a temporary institution name that does not appear in Plaid Link search results. This allows you to:

• Test your integration through real third-party applications
• Send limited traffic through production infrastructure
• Run friends-and-family or internal testing
• Identify edge cases not present in pre-production

Once testing is successful, update the institution name and branding to make the integration discoverable in Plaid Link.

After production access is enabled, your institution appears in Plaid Link search results for applications that use the products you support (e.g., Auth, Transactions, Identity) and the account types you offer (e.g., checking, savings, credit).

Complete before going live:

• Deploy your OAuth server to your production environment
• Verify your discovery endpoint is accessible
• Publish your JWKS endpoint and verify it is accessible
• Issue production credentials to Plaid
• Configure mTLS certificates (if applicable)
• Confirm your organization name, logo, and URL

• Pass validation for all required endpoints
• Verify error handling for common failure cases
• Test token expiration and refresh flows

• Enable latency monitoring for your endpoints
• Configure error rate alerts
• Set up uptime monitoring
• Verify log aggregation is working
• Establish an on-call rotation

• Create runbooks for common issues
• Document escalation paths
• Share support contact information with Plaid
• Define maintenance window procedures