While connecting your bank account to dub is usually straightforward, you might encounter issues with the Plaid integration. This article addresses the most common bank linking problems and how to resolve them.

Issues with Smaller Banks and Credit Unions

Some smaller financial institutions and credit unions may experience connection issues with Plaid despite being listed as supported banks.

Symptoms:

• Connection errors when attempting to link
• Repeated authentication failures
• "Bank not supported" messages for smaller institutions

Solutions:

1. Contact Your Bank's Customer Service
   • Inform them you're having issues connecting through Plaid
   • Ask if they're aware of any ongoing integration issues
   • Request assistance in resolving any potential blocks from their end
2. Try an Alternative Bank Account
   • If available, consider linking another bank account temporarily
   • Major banks like Chase, Bank of America, Wells Fargo, and other national banks typically have more reliable Plaid connections
   • Online banks like Chime often work seamlessly with dub

Account Name Mismatch Issues

For security and regulatory reasons, the bank account you link must be a personal account in your name.

Symptoms:

• Error message indicating an "Identity Mismatch"
• Successful bank connection but inability to complete the linking process
• Message about account ownership verification

Solutions:

• Link a personal bank account that contains your name as it appears on your dub account
• Ensure your name is spelled identically on both your dub account and bank account
• If necessary, contact your bank to confirm how your name appears on your account

Duplicate Application Issues

If you've previously submitted another dub application or had an application canceled and then reapplied, you may encounter linking issues due to duplicate records.

Symptoms:

• Unexpected errors during the bank linking process
• Application seems to stall after selecting your bank
• Loading spinning wheel appears in an endless loop 

Solution:

This issue requires manual resolution from our support team. Please contact dub support at support@dubapp.com to resolve this issue. 

OAuth and Tokenized Account Numbers

Some banks use OAuth (Open Authorization) for enhanced security, which creates a unique account number specifically for third-party connections.

Symptoms:

• The account number shown in dub differs from your actual bank account number
• You see unfamiliar account details after linking

Explanation:

This is a security feature, not an error. As a security measure, some banks create tokenized account numbers specifically for third-party integrations through Plaid. This means:

• The account number you see in dub is different from your actual account number
• This tokenized number is created specifically for the connection between your bank and dub
• Your actual account number remains protected
• All transfers will still work correctly using this tokenized number

Solution:

No action is needed. This is a security feature working as designed to protect your actual account details.

Need Help?

If you have any questions or need assistance during the account opening process, please contact us at support@dubapp.com.