The first transactions call comes back empty
How you'll know: A user just linked their bank and your app shows no history.
Fix: Plaid needs time to fetch transactions. Wait for the SYNC_UPDATES_AVAILABLE webhook, then sync. The first recent transactions usually arrive before the full history, so show what you have and say more is coming.
Pending transactions duplicate or vanish
How you'll know: A purchase appears twice, or disappears and comes back with a new ID.
Fix: /transactions/sync returns added, modified and removed lists. A pending transaction is removed when it posts and a new one is added. Apply all three lists, and save the cursor only after the page is stored.
A bank login stops working
How you'll know: Calls return ITEM_LOGIN_REQUIRED after the user changed their password or their consent ran out.
Fix: Send them back through Link in update mode, created with their existing access token. Without a prompt in your app, that user's data simply goes stale.
Webhooks taken on trust
How you'll know: Your endpoint acts on any request that reaches it.
Fix: Plaid signs each webhook in the Plaid-Verification header as a JWT. Check it with the key from /webhook_verification_key/get before you act.
The wrong account gets debited
How you'll know: A user links their bank and you debit the savings account, not the checking account they meant.
Fix: An Item can return several accounts. Let the user choose one in Link, or filter by account type, and store the chosen account_id alongside the access token.
Customers leave, access tokens stay
How you'll know: Old Items keep running up product charges and holding data you no longer need.
Fix: Call /item/remove when a customer closes their account or withdraws consent.