Plaid Integration Expert
Guide Plaid Link, Auth, Transactions, Identity, Accounts, balances, and webhook integrations with consent and token-safety checks.
Fast Workflow
- Identify the product flow: account linking, ACH auth, transaction sync, identity verification, balances, or webhook handling.
- Inspect the existing Link token endpoint, public token exchange, item/access-token storage, product list, and webhook receiver before editing.
- Keep Plaid secrets and access tokens server-side, store tokens encrypted where appropriate, and avoid logging account or identity data.
- Use sandbox/development/production environments deliberately; do not mix tokens or assumptions across them.
- For current API details, read local docs if present or official Plaid docs before changing banking-data behavior.
Detailed Reference
Read references/full-guide.md when you need Link setup, token exchange, Auth, Transactions sync, Identity, Accounts, balances, webhooks, environments, and security checklists. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.
Documentation
Use official Plaid docs when local docs are absent.
Safety Checks
- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.
- Keep secrets server-side and use environment variables for credentials.
- Prefer the simplest supported integration path that satisfies the product requirement.
1---2name: plaid3description: Expert guidance for Plaid banking API integration — Link flow, Auth (routing/account numbers for ACH), Transactions (sync/categorize), Identity (KYC/account holder), Accounts (balance/types), and webhook handling. Invoke when user mentions Plaid, bank connections, ACH verification, account ownership, transaction history, KYC, or Plaid webhooks. Example queries — "connect a bank account with Plaid", "retrieve ACH routing numbers", "sync transactions since last webhook", "verify user identity via Plaid".4---56# Plaid Integration Expert78Guide Plaid Link, Auth, Transactions, Identity, Accounts, balances, and webhook integrations with consent and token-safety checks.910## Fast Workflow11121. Identify the product flow: account linking, ACH auth, transaction sync, identity verification, balances, or webhook handling.132. Inspect the existing Link token endpoint, public token exchange, item/access-token storage, product list, and webhook receiver before editing.143. Keep Plaid secrets and access tokens server-side, store tokens encrypted where appropriate, and avoid logging account or identity data.154. Use sandbox/development/production environments deliberately; do not mix tokens or assumptions across them.165. For current API details, read local docs if present or official Plaid docs before changing banking-data behavior.1718## Detailed Reference1920Read `references/full-guide.md` when you need Link setup, token exchange, Auth, Transactions sync, Identity, Accounts, balances, webhooks, environments, and security checklists. Keep this entrypoint loaded first, then load only the reference sections relevant to the task.2122## Documentation2324Use official Plaid docs when local docs are absent.2526## Safety Checks2728- Do not invent product limits, API behavior, prices, compliance requirements, or security guarantees.29- Keep secrets server-side and use environment variables for credentials.30- Prefer the simplest supported integration path that satisfies the product requirement.
tuyv