PSD2 AIS for Small Business: What Account Information Services Actually Cost (2026 Guide)

If you run a small business in Europe and you've been trying to get bank transactions into your accounting software without exporting CSVs by hand every month, you've probably run into the phrase "PSD2 AIS" — usually on a pricing page that stops making sense below enterprise volumes. This is a practitioner's guide to what AIS actually is, what it should cost a small business, and how to pick a provider without a sales cycle. Fair warning up front: I maintain open-banking.io, one of the options I'll mention, so I'll be explicit about where my bias sits.

What PSD2 AIS actually is

PSD2 is the EU payments regulation that obliges banks to let licensed third parties read your account data once you consent to it. An AIS — an Account Information Service — is simply a licensed company that does that reading on your behalf, so you or your accountant can see balances and transactions from every business bank account in one place instead of logging into five different banking portals.

When a small business needs an AIS provider vs trying to call banks directly

Every PSD2 bank operates a "dedicated channel" API with public documentation, so the DIY route looks tempting: write a client per bank, consent with your own account, done, free. A few things make that a trap for anything business-critical:

• Each bank implements its own flavor of the rules — Berlin Group, UK Open Banking, or something homegrown — with its own onboarding process, consent model, and undocumented quirks.
• Banks change endpoints and break clients without much notice. Five direct integrations means maintaining five clients forever.
• And the gatekeeper: to call banks' PSD2 interfaces directly as a regulated third party, you'd need your own eIDAS certificate for that.

The rule of thumb I use: if it's you, one bank, and a weekend project to chart your own spending, the direct APIs are genuinely educational. The moment a bookkeeper or a customer depends on the data refreshing every day, you want a provider that has already absorbed the integration and compliance overhead across all your banks at once.

If you're arriving from a US stack, the switch involves more than swapping an API key — what actually changes when you switch from Plaid in Europe covers the API-shape and consent differences.

What to check when comparing AIS providers

Four things decide whether a provider fits a small business. Everything else is marketing.

1. Coverage of your banks. Headline numbers like "10,000+ banks" are padded with long-tail institutions you'll never touch. Search the actual bank list for the specific banks your business uses — including the regional one and the Revolut/Wise-style account.
2. Price per bank connection. Providers meter differently: per connection, per account, per successful refresh, or per API call. Ask what a "connection" means, and what happens when a consent expires every 90 days under PSD2 re-consent rules — some models treat re-authentication as a fresh billable connection.
3. Sandbox access. Can you build and test against realistic endpoints before signing anything? A sandbox gated behind a sales call tells you exactly what the rest of the relationship will feel like.
4. Who holds the keys. Where do consents and tokens live, who can read raw transaction payloads, and can you revoke a connection yourself? Read-only access to your business accounts is exactly as sensitive as it sounds.

A short honest provider comparison

The cheapest entry point I'm aware of starts at roughly €3/month — that's open-banking.io, and full disclosure: I maintain open-banking.io, so weigh my framing accordingly. It exists precisely because the bigger names below were a poor fit for a three-person company with four bank connections: per-connection pricing, no minimum commitment, no sales call required.

• Enable Banking — PSD2-regulated, one API across a wide set of European banks. Focused and technically solid; talk to them directly about current terms and volumes.
• GoCardless Bank Account Data — the former Nordigen. It built its reputation on a genuinely free tier; it has since been folded into GoCardless's product line and billing, and the tier limits have shifted over the years. Read the current pricing page rather than a two-year-old blog post before counting on "free."
• TrueLayer — strong coverage and genuinely pleasant developer experience, but the product direction has moved upmarket toward enterprise data products. Expect a sales conversation and minimum commitments.
• Tink — Visa-owned, pan-European coverage, an enterprise sales motion. Great if you're building a fintech; overkill if you have three bank accounts and one accountant.

I've deliberately not quoted numbers for the others, because AIS pricing moves constantly and stale figures are worse than none. If you want the full price-first breakdown, the cheapest open banking APIs for small businesses and indie builders in 2026 goes deeper on tiers and thresholds.

A worked mini-example

A two-person design studio has a business account at a regional bank plus a Revolut account. The bookkeeper needs monthly transaction data. Until now that meant the founder exporting CSVs — or worse, sharing banking credentials (please don't).

With an AIS in the middle:

1. The founder goes through a consent redirect at each bank, and the bank's own app confirms identity (SCA). Credentials are never shared with the AIS or the accountant.
2. Each consent lasts up to 90 days, then needs one re-confirmation. Meanwhile, balances and transactions refresh daily without anyone logging in anywhere.
3. The bookkeeper gets read-only access to categorized transactions through a dashboard or a clean export — and nothing more than that.

Note the shape of that access: AIS consent is read-only by construction. Moving money is a separate regulated service (a PIS), not part of account information. That's the strongest argument for the AIS route over "just give my accountant the login" — it's not merely tidier, the blast radius if anything goes wrong is categorically smaller.

Total cost for that scenario at open-banking.io pricing: two connections, roughly €6/month — less than one month of most bank-feed add-ons the accounting suites themselves will try to sell you.

If you're evaluating providers this week, the checklist matters more than any single price: your banks on the coverage list, a predictable per-connection cost, an open sandbox, and a clear answer about who holds the keys. Everything else is negotiable.