evonx
Guide

How to integrate Plaid

Follow these steps in Evonx to connect Plaid for bank account linking and financial data access. Use this when expense, lending, or fintech flows need verified accounts.

Step-by-step

Create a Plaid application

Register products (Auth, Transactions, etc.) and note sandbox vs production credentials.

Implement Link on the client

Launch Plaid Link with a server-created link token; never embed secret keys in the browser.

Exchange public tokens server-side

Swap public tokens for access tokens and store them encrypted with tenant ownership.

Fetch accounts and balances

Pull account metadata required for your product and map to local bank account records.

Handle webhooks and item errors

Listen for ITEM errors and login repairs; prompt users to re-authenticate when needed.

Preview in sandbox

Complete Link flows with sandbox institutions in Evonx preview before production access.

Outcome

Plaid-connected banking flows with Link, token exchange, and webhook repair paths you can ship.

FAQ

Which Plaid products do I need?

Auth for account/routing verification, Transactions for expense feeds, Identity when you must confirm ownership.

How should access tokens be stored?

Encrypt at rest, scope by tenant, and restrict decryption to server jobs that need them.

Can I move from sandbox to production easily?

Yes if env vars and Link configs are environment-specific and you completed Plaid’s production checklist.

Build production software with Evonx

Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.