Plaid OAuth 2.0 — Production connector profile – StackOne setup guide

Set up the OAuth 2.0 — Production connector profile for Plaid in StackOne. One-time admin setup required before your users can link Plaid accounts via Hub.

Production secrets are only revealed after Plaid approves your account for Production access. If you have not yet been approved, you cannot use this auth method — use OAuth 2.0 — Sandbox instead.

1. Create a Plaid account

If you do not already have one, sign up first. Sandbox access is granted automatically.

1. Sign up

   Go to the Plaid Dashboard signup page, create an account, and verify your email.

2. Apply for Production access

Plaid does not grant Production access automatically. You must apply and pass Plaid’s risk and security review before your Production secret is enabled and your client_id can call real banks.

1. Start the Production application

   Sign in to the Plaid Dashboard and click Get Production access in the left sidebar.

2. Complete the questionnaires

   Fill out the company info, use case, security, and compliance questionnaires that Plaid presents. Be specific about which products and country codes you intend to use.

3. Wait for approval

   Approval typically takes several business days but can take longer if Plaid asks follow-up questions. Until you are approved, the Production secret on the Keys page will remain hidden.

3. Copy your Client ID and Production Secret

Once you are approved for Production, the Production row on the Keys page becomes interactive.

1. Open the Keys page

   In the Plaid Dashboard left sidebar, expand Developers and click Keys.

2. Copy the Client ID

   Copy the value labeled client_id at the top of the page (a 24-character hex string, no prefix) for the Client ID field. The same client_id works in Sandbox and Production.

3. Reveal and copy the Production Secret

   In the Production row, click the eye icon next to secret to reveal the value. Copy it for the Secret field and store it securely.

   • Use the Production secret here. The Sandbox secret will not authenticate against real banks.
   • Treat the Production secret as highly sensitive — it grants access to your real Production account.

4. Register a Plaid Link redirect URI (depends on your platform)

This URI is a page in your own application — the page that hosts your Plaid Link integration. It is not a StackOne URL. Unlike connectors where StackOne completes the OAuth handshake, StackOne never receives a browser redirect from Plaid, so the StackOne callback URL you may have used elsewhere does not apply here.

Banks that use OAuth (Chase, Capital One, Wells Fargo, and others) send the user back to this page after they authenticate at the bank, and Plaid only permits redirects to URIs registered in advance.

1. Check whether your platform needs one

   Whether a redirect URI is required depends entirely on where you run Plaid Link.

   • Desktop web — not needed. Link opens the bank in a pop-up window, and Plaid’s OAuth guide states that OAuth flows function properly on web without a redirect URI.
   • Mobile web in a webview — required. Webview browsers opened from Mail, Facebook, Google Maps and similar apps usually block pop-ups, so without a redirect URI those users cannot complete OAuth.
   • iOS — required. You must also host the page as a blank web page and configure an Apple App Association File so the URI works as a universal link. Custom URI schemes are not supported.
   • Android — a redirect URI is not used. Pass android_package_name to /link/token/create instead and add your package name to Allowed Android package names in the Plaid Dashboard. Plaid derives the redirect URI from the package name.
2. Add the URI to the allowlist

   In the Plaid Dashboard, navigate to Developers > API, find Allowed redirect URIs, then click Configure > Add New URI and save.

   • Example: https://your-app.com/plaid/oauth-return
   • Production URIs must use HTTPS. localhost over HTTP is accepted in Sandbox only.
   • The URI cannot contain query parameters, and it cannot contain a # because Plaid does not support hash routing.
   • Subdomain wildcards such as https://*.your-app.com/plaid/oauth-return are allowed on the allowlist, but never in the redirect_uri you pass to /link/token/create — that value must match a registered URI exactly.
3. Handle the redirect in your app

   The page at that URI must reinitialize Plaid Link with the same link_token and pass receivedRedirectUri: window.location.href. Plaid appends an oauth_state_id query parameter that Link needs in order to resume the session.

   • Full reference: Plaid Link OAuth guide

Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Plaid:

1. Navigate to Connector Profiles

   Login to StackOne and navigate to Connector Profiles

2. Create New Connector Profile

   • Click + Connector Profile
   • Search for and select Plaid
   • Select Type as OAuth 2.0 — Production

   • Fill out the fields using details retrieved from your provider:

     • Client ID
     • Secret
   • (Optional) Select Actions to be enabled for this Connector Profile
   • Click Create profile

Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Plaid.