Plaid Pricing 2026: Cost Per Connection and Request
Nov 5, 202615 min read
Plaid has four plans, which teams often review alongside the workflows they automate with tools like Activepieces:
- Trial
- Pay-as-you-go
- Growth
- Custom
Plaid pricing is the set of fees Plaid charges for access to bank-account data and related products, billed per product as a one-time fee, a per-request fee or a monthly subscription per connected account, depending on your plan.
Plaid Pricing Plans, Rates and Free Allowances Compared
The plan sets your terms; the unit sets your bill. Each product within these plans bills by its own unit: once, per request, or per month.
1% of US bank-account holders have connected through Plaid, according to its own materials. That's a vendor-stated figure, but it means most of your users will be linking for the first time.
Read the commitment column first, because it decides whether you can leave when volume changes. The table shows what each plan commits you to.
| Plan | Price or contact sales | Billing unit | Item limit | Commitment |
|---|---|---|---|---|
| Trial | Free | None | Capped | None |
| Pay-as-you-go | Per-product rates | One-time, per request or per month, by product | Priced per product | None |
| Growth | Per-product rates | Same units, on contract terms | Priced per product | Contract |
| Custom | Contact sales | Negotiated | Negotiated | Negotiated |
Plan structure as listed on plaid.com/pricing, checked 2026-11-05.
If you get a quote above Pay as You Go, there is no public price to compare it against, because Growth and Custom both require a sales conversation.
Billing units: one-time, per request, per month
Look at per-request products first, because the spread is widest there. PriceLevel reports Balance at $0.05 per request and Monitor rescans at $0.10.
According to PriceLevel, Signal is $0.20, ID data source and Monitor base are $0.50 each, and the ID fraud engine is $0.55, so fraud detection is the costliest per-unit service.
That's roughly a 10x gap. At 10,000 calls a month per Costbench, Balance costs about $500 and the fraud engine about $5,500, so which product you call matters more than any plan discount.
If you run Signal before every payment, 20,000 payments cost about $4,000 at $0.20 each. That is per-request billing scaling with how often you call.
The same applies when you chain calls inside workflows you build with Activepieces: Plaid meters every triggered call.
You pay nothing on the Trial plan, but it caps Items, meaning linked bank connections. It suits proving an integration, not carrying production traffic. Once you pass the cap, you move to Pay-as-you-go rates, and every per-request figure above starts applying to real users.
If you are running this arithmetic for your own team, see what the same workload costs on Activepieces.
Monthly Plaid bill for small teams
At pay-as-you-go rates, this workload costs roughly a thousand dollars in its first month, and the line that keeps recurring is the per-account Transactions fee, not the one-time link fee. Whether a quote replaces these rates depends on how far the account count climbs.
Over the month, the team links 500 new users, each through Auth, and keeps Transactions running on 2,000 connected accounts, which means they're paying for both new customer onboarding and ongoing account servicing. It also checks balances on demand.
I'm not assuming a balance-check volume, because the right number depends on your product, so that line stays as a rate you multiply yourself: $0.05 per request.
Plaid cost breakdown for 500 links
For 500 links at $1.00 to $1.25 each, Auth comes to $500 to $625. Plaid bills it once per link, so you pay it only in months when you onboard people.
Every month those accounts stay connected, Plaid bills Transactions again, at $0.25 per account. For 2,000 accounts that's $500. Balance checks add $0.05 each, so an app that refreshes a balance on every page load pays for traffic, not for customers.
Auth and Transactions are of similar size, but only Transactions is sure to recur next month, and the balance-check segment is the one your own code can inflate.
Summed, Auth plus Transactions come to $1,000 to $1,125 before any balance checks, and the actual total will grow when balance operations are added. That's the figure to hold against your budget, with the balance-check line added once you count your own calls.
Plaid pricing at 2x and 10x usage
Doubling both onboarding and connected accounts gives 1,000 links ($1,000 to $1,250) and 4,000 accounts ($1,000). The bill roughly doubles, so nothing about the rates punishes growth yet.
At 10x, it's 5,000 links ($5,000 to $6,250) and 20,000 accounts ($5,000), and the recurring line alone is now a fixed four-figure commitment each month.
That's the point at which a Growth plan or custom quote becomes worth requesting. I have no published threshold, so ask Plaid sales for a quote and compare it against this arithmetic, using your own link and account counts.
Fees and Limits That Change the Plaid Bill
Before you sign, your quote should name each of five charges, because together they move a Plaid bill more than any per-call rate. Each is set out in Plaid's own documentation:
- A monthly subscription charged on each connected account, from Plaid's billing docs
- Repeat calls on the same account, from Plaid's billing docs
- Support at $500–$2,000 per month, from Plaid's support documentation
- A $1,000 per month business minimum, from Plaid's pricing documentation
- A 12-month commitment on the Growth plan, from Plaid's pricing documentation
When a customer linked an account a year ago and never opens it, it still bills every month, because a subscription that bills per account per month meters time, not use.
Unless you unlink dormant accounts, your cost tracks your all-time account count, not your active users.
Refresh balances nightly on every account and you make about thirty billable requests per account per month, since request-billed products charge each time you call them. Moving to refresh-on-demand, or only for recently active users, cuts that volume directly.
**Unless you unlink dormant accounts, your cost tracks your all-time account count, not your active users.
Plaid minimums, contracts and support tiers
, so a small workload pays for usage it doesn't have.
The 12-month Growth commitment means you carry that cost even if your volume drops. Support at $500–$2,000 a month can add up to $24,000 a year on top.
To see what buyers actually sign, look at Vendr, which tracks software purchases. Its Plaid marketplace data runs from the lowest deal at $6,917 a year to the highest at $72,315, so the top contract is about ten times the bottom.
Two buyers can both be "on Plaid" and pay an order of magnitude apart, so a list rate tells you very little about your own contract. Your unit counts decide where you land.
Both cost time, though neither carries a published fee: Plaid limits how fast you can call its API, and production access requires approval.
Budget for a launch that waits on review, and for batch jobs that must be spread out instead of run all at once.
Worth checking against a plan that does not meter every step: one credit covers a whole run on Activepieces.
Plaid Against Its Closest Alternatives on Price
Only two of the five let you build the budget from a public page: Plaid and Teller publish pricing you can model by billing unit, while MX, Finicity and Yodlee mostly sell by quote.
Once launch review and batch spacing are already in your plan, pricing visibility matters: a quote-only vendor makes your cost depend on a sales cycle you can't forecast.
Comparison table by vendor
To see what each vendor discloses and in which unit, read the billing unit column first: a "quote only" cell means the unit is set in a contract, so you can't compare it with Plaid's until you have the paper.
| Vendor | Published price or quote only | Billing unit | Free allowance | Region | Support level |
|---|---|---|---|---|---|
| Plaid | Published for some products, custom for others | Once, per request or per month, by product | Free testing access | US, Canada, UK and parts of Europe | Varies by contract |
| MX | Quote only | Set in contract | None published | Mainly US | Contract-defined |
| Finicity (Mastercard) | Quote only | Set in contract | None published | Mainly US | Contract-defined |
| Teller | Published | Per connection | Free for development | US | Not published |
| Yodlee | Quote only | Set in contract | None published | Global | Contract-defined |
I haven't verified source URLs or check dates for these cells, so confirm each on the vendor's own pricing page before it goes into a budget. Treat the table as a map of where to look.
Where published pricing exists and where it doesn't
With a published page you can multiply your expected calls by a unit and see the bill before talking to anyone. Plaid and Teller allow that, though Plaid still pushes some products into custom contracts.
For MX, Finicity and Yodlee, the first real number arrives with a proposal, and that proposal will bundle minimums and term length you can't see in advance.
Choosing a Plaid alternative by workload
A small team with a US-only product and a predictable connection count can price Teller or Plaid on paper. A product that needs Canada, the UK or Europe should start with Plaid or Yodlee, since the other three are US-centred.
If a bank-scale rollout already expects a negotiated contract, it can fairly ask all five for quotes. Put the quotes beside Plaid's per-unit model, then compare the totals at your own volume.
Watching Plaid Usage with Activepieces Workflows
Once you have the quotes and your own volume, the next job is to catch the day real usage drifts away from the model. Activepieces can log the webhooks Plaid sends you, count billed events per product, and alert you when a count jumps.
Its core is MIT-licensed and its open source monorepo holds 747 integrations, so the Slack or email step that delivers the alert is a published integration rather than something you write.
It doesn't lower Plaid's rates or change how Plaid bills you.
What a Plaid usage-alert workflow does
Activepieces catches webhooks and routes them by event type, and its audit-event example shows the shape you would reuse: a trigger node feeds a "Catch Webhook" step, which hands the payload to a router that sends each event type down its own branch.
In that example the branches are "Flow created", "Flow published" and "Otherwise". You test the setup against a live webhook URL and preview the incoming payload field by field.
Swap Plaid in for the audit source and the structure holds. Plaid can send webhooks to a URL you register.
Point that URL at the catch-webhook step, and the router splits events by type or by product. That split matters because the article's argument is that cost follows the billing unit.
A one-time item, a per-request call and a monthly subscription each need their own counter, and one total hides which of them is growing.
Build it like this:
- Catch each Plaid webhook and store the raw payload with its timestamp.
- Route by product, so each product keeps its own tally.
- Compare each tally against the expected volume from your cost model.
- Send a message through a channel the builder supports, such as Slack, Gmail, Teams or an HTTP call, when a count crosses your threshold.
The "Otherwise" branch earns its place too: an event type you didn't plan for is a product you may be billed for without having modeled it.
The watcher is cheap to run: Activepieces' published pricing page lists 1 credit per flow run, any number of steps, so the four-step flow above costs one credit per webhook, while Zapier's pricing page bills per task and Make's bills per module, which makes each step count separately.
The Free plan includes 1,000 credits a month and unlimited flows, and unlimited flows applies on every plan.
What it cannot do
It can't see your invoice. Webhooks tell you that something happened, not what Plaid charged, so your counts are an estimate built from your own rate assumptions.
Some billed calls, such as ones your code makes directly, may never produce a webhook, so those counts will run low unless your application also reports them.
It also can't move you off a custom contract or change a rate. Treat the workflow as an early-warning check against your model, and reconcile it against the actual bill each month.
I wouldn't rely on any specific Plaid connector existing in Activepieces without checking its current integrations list; the webhook route above needs none.
Pricing Checks to Run This Week
Run five checks in order, and you'll know what Plaid actually costs you, which the rate card alone can't tell you. The sequence matters because each step produces the input for the next.
Pull last month's Plaid invoice
Pull last month's invoice, broken out by product. Export one line per product your integration calls: account linking, balance checks, transaction syncs, identity lookups, whatever appears.
A single total hides which product drives the bill, so you can't tell whether trimming one call pattern would matter or whether you're paying for something you barely use.
Map Plaid invoice lines to billing units
Map each line to its billing unit. Mark every product as billed once per connected account, per request, or per month per connected account. This decides how the cost behaves as you grow.
A one-time charge scales with new signups, and a per-request charge scales with how often your code polls. A monthly charge scales with the total accounts you keep connected, whether or not anyone uses them.
Rebuild your Plaid bill from usage
Rebuild the worked bill from your own volumes. Take the unit counts from the invoice and multiply them by the rates on your contract, not the public ones.
If your rebuilt total doesn't match what you were charged, the gap is a discount, a minimum, or a fee you haven't found yet, and it is worth chasing before anything else.
Three questions for Plaid sales
Ask sales three questions. First, is there a minimum monthly or annual spend, and what happens when you fall below it? Second, does any commitment lock in volumes or a term, and what is the penalty for undershooting?
Third, which of the products you call are priced only under a custom agreement, and what would you pay if you moved off it?
Get the answers in writing, since verbal quotes can't be audited later.
Set a Plaid pricing re-check date
Set a re-check date. Put a recurring calendar entry on the day after your next invoice arrives, and repeat the first three checks. Usage drifts and contracts renew, so a bill you understood in January may not be the one you pay in June.
Frequently asked questions
Is Plaid free for small projects or testing? Testing is free in Sandbox, which returns simulated data, so you can build the whole integration without a live bill.
Live banks are different: what you can try for free depends on the allowances on your current plan, so check your dashboard before assuming any real connection is unmetered.
Does Plaid charge for failed or abandoned bank links?
Opening the link flow isn't itself a billed product, and an abandoned session produces no connected account to bill against. Charges attach to products on a connected account, each on its own unit: once, per request or per month.
Confirm with Plaid at which event each product you use starts billing, because a link that succeeds but is never called again can still start a monthly charge.
Can I negotiate Plaid's pricing? Yes, and your leverage is the product list rather than the headline rate. Volume, the mix of one-time, per-request and monthly products, and a commitment term are what a custom contract prices.
Go in with a model that counts each product by its billing unit, so you can show which line dominates your bill and ask for movement there.
Does Plaid price differ for non-US connections? Expect it to. Coverage outside the US is sold by product and region, and not every rate is published on the public pricing page.
Treat any US-based estimate as a starting point only, and ask sales for a written quote that names the products, the countries and the billing unit for each.
How often does Plaid change its pricing?
There's no published schedule, so don't build a budget on the assumption that today's page will hold. Record the date you read each rate and re-check before renewing or adding a product.
On a custom contract, the rates you signed hold for the term, which is a practical reason to read the renewal clause as closely as the price table.
Related reading
References
Running the numbers
See what the same workload costs here.
Free forever plan, and every paid plan self-hosts at no extra cost.
See pricing Talk to sales
