---
title: "API Banking"
url: "https://mahouse.world/glossary/api-banking"
type: "glossary term"
topic: "Open banking & APIs"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-06"
---

# API Banking

API banking is the exposure of banking services — account information, payment initiation, virtual accounts, cards, FX, lending — as programmable interfaces that authorised third parties and corporate customers call directly from their own systems, instead of through a branch, a file transfer or a portal; it includes the mandated open-banking APIs under PSD2, the commercial APIs banks sell to corporate treasuries and platforms, and banking-as-a-service APIs. It turned the bank into a service that software calls.

**Also known as:** Banking APIs, Bank APIs, Programmable banking, Corporate banking APIs

## Key facts

- **Used at:** fintechs reading and initiating on customers' accounts (open banking); corporate treasuries automating payments, collections and reconciliation across banks; marketplaces and platforms running payouts, virtual accounts and wallets; BaaS programmes; embedded finance; and the bank's own channels, which increasingly run on the same APIs
- **Binding:** PSD2 and the UK Payment Services Regulations mandate open-banking access for account information and payment initiation with customer consent, on APIs meeting the EBA's technical standards; beyond the mandate, commercial APIs are contracts; DORA governs the ICT risk; and the bank remains responsible for AML, sanctions and fraud on every API-initiated transaction
- **Typical services:** account balances and transactions; credit transfers (SEPA, instant, Faster Payments, wires); direct debits and collections; virtual account creation and allocation; card issuing and controls; FX quotes and execution; statements and confirmations; webhooks for incoming funds; and, for BaaS, customer onboarding and ledgering
- **Typical quality:** uneven — the mandated open-banking APIs vary by bank in reliability and completeness (a persistent complaint that PSD3 addresses with performance standards), while the commercial APIs of the leading transaction banks and the API-native banks (Starling, ClearBank, Modulr, Banking Circle, Griffin) are built to fintech standards
- **Parties:** banks, the third-party providers and fintechs calling them, corporate treasurers, the regulators (and the UK's Open Banking implementation entity and its successor), the aggregators (Plaid, Tink, TrueLayer, Yapily) that normalise many banks' APIs into one, and the standards bodies (Berlin Group, UK Open Banking)

## How API banking works in practice

A marketplace paying 30,000 sellers used to upload a payment file to a bank portal each evening and reconcile the next morning from a statement. On banking APIs: each seller has a virtual account under the marketplace's master account, buyer payments arrive with the virtual account number identifying the seller, a webhook notifies the marketplace's ledger the moment funds land, and payouts are initiated by API as instant transfers in the seller's currency, with FX executed on the same API where needed. Reconciliation is automatic because every inbound and outbound transaction carries the reference the marketplace's system assigned. The treasury team sees balances across four banks in one dashboard built on their APIs and sweeps between them daily. The bank is a set of endpoints, and the marketplace's product is built on top of them.

The open-banking side works differently and less smoothly. A lender wanting to verify an applicant's income asks the applicant to consent; the applicant authenticates with their bank; the lender's provider retrieves 12 months of transactions through the bank's PSD2 API — or through an aggregator that handles the 3,000 European banks' varied implementations — and categorises them. The mandate made the access a right; the bank's incentives made the APIs uneven; and the aggregators exist to absorb the variation. PSD3 and the Payment Services Regulation add performance standards and a permitted premium-API market. For a fintech, API banking is the plumbing that its product's promises depend on, and the choice of bank is a choice of API; for a buyer, a target built on one bank's APIs is a target with a dependency, and one built on an aggregator has another.

For a treasurer, API banking is the end of the file-and-portal era; for a fintech, it is the raw material of the product; for the bank, it is the channel through which its next generation of customers will never see its brand.

## Example

A payroll fintech serving 8,000 employers moves from batch files to a bank's commercial APIs and virtual accounts. Before: employers fund a pooled account by transfer; the fintech matches funds to employers by reference, with 6% needing manual work; salaries go out in a file at 3 p.m. for next-day arrival; 40 support tickets a week concern late or unmatched funds. After: each employer funds its own virtual account, matching is automatic, salaries are initiated by API as instant payments the moment funds are confirmed, and employees are paid within minutes of the employer's funding. Manual matching falls to 0.2%, tickets to 4 a week, and the fintech launches same-day pay as a product. When the bank's API has a four-hour outage in month five, the fintech's fallback — a second bank's API with the same virtual-account structure, kept warm — carries the day's payroll.

## Common mistakes

- One bank's APIs with no fallback; outages become the fintech's outages.
- Reading open-banking APIs as uniform; each bank's differs, and an aggregator's normalisation is the product.
- Virtual accounts without a reference discipline, which recreates manual reconciliation.
- Treating API-initiated payments as outside the bank's AML view; the bank checks every one.
- Buying a fintech without mapping which bank APIs its product cannot run without.

## Related terms

- [API](https://mahouse.world/glossary/api.md)
- [PSD2](https://mahouse.world/glossary/psd2.md)
- [BaaS](https://mahouse.world/glossary/baas.md)
- [Account-to-Account Payment](https://mahouse.world/glossary/account-to-account-payment.md)
- [Virtual Account](https://mahouse.world/glossary/virtual-account.md)
- [Treasury Management](https://mahouse.world/glossary/treasury-management.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov