# Troubleshooting missing connected accounts after OAuth onboarding

If you're unable to find a newly onboarded connected account after completing OAuth, it’s likely due to a configuration issue. This guide will help you check your settings and correct any issues to ensure smooth account connections.
---
### Common cause
A missing connected account usually happens when:
* The **OAuth redirect URI** is incorrectly configured or missing.
* The **redirect endpoint** automatically moves users to a success page without completing the account connection flow.
* Your platform is still using **Express OAuth**, [which has been deprecated](https://docs.stripe.com/connect/oauth-express-accounts).
### What to check
1. **OAuth Settings**
* Go to your Stripe Dashboard → **Settings** → **Connect** → **Onboarding Options** → **OAuth Settings**.
* Verify that the **redirect URI** points to an endpoint that can properly handle the [OAuth authorization response](https://docs.stripe.com/connect/oauth-reference#post-token).
1. **Redirect URI Behavior**
* Ensure the redirect URI captures and processes the OAuth response (authorization code and state).
* Avoid immediately forwarding users to a success page (for example: `/billing-success/`) without processing the OAuth response.
1. **OAuth Completion**
* Confirm that your integration finalizes the account connection after receiving the authorization response.
* Double check your server logs or Stripe logs to ensure that the account_id was generated and linked.
1. **Express OAuth Deprecation**
* If you're still using **Express OAuth**, our recommendation is to leverage the [Account/AccountLink API](https://docs.stripe.com/connect/express-accounts#create-account)
### How to fix it
* Update your redirect URI to a live endpoint capable of handling the OAuth response properly.
* Reinitiate the OAuth onboarding for the impacted connected account(s).
* Test the flow to ensure accounts are correctly connecting and appearing in your dashboard.
### Additional tips
* Use Stripe’s **OAuth logs** to trace the authorization request and response.
* Review your server-side handling of the OAuth `code` and `state` parameters to make sure the account is being created or updated.
* Consider adding basic logging around your OAuth endpoints to catch and diagnose future issues early.
### Related resources
* [Stripe Connect OAuth Documentation](https://stripe.com/docs/connect/oauth-reference)
* [Connect OAuth — Linking Accounts with Stripe](https://stripe.com/docs/connect/oauth-reference)
* [Standard OAuth Onboarding — How It Works](https://stripe.com/docs/connect/standard-accounts#using-oauth)
* [Handling the OAuth Redirect and Code Exchange](https://stripe.com/docs/connect/oauth-reference#get-authorize)
* [Testing OAuth Flows in Stripe](https://stripe.com/docs/connect/testing#oauth)
* [Setting Redirect URIs for Connect OAuth](https://stripe.com/docs/connect/oauth-reference#redirect-uris)