PSD2-Compliant API Infrastructure

One API.
2,000+ Bank Connections.

BankLyra wraps 2,000+ European bank connections into one PSD2-compliant API — so your engineering team ships account aggregation, balance checks, and payment initiation in days, not the nine-month bank integration each bank demands.

Get API Keys Read the Docs
BankLyra API — /connect 
# 1. Create a connection session
POST https://api.banklyra.com/v1/connect
Authorization: Bearer blyr_live_sk_...
Content-Type: application/json

{
  "user_ref": "usr_7f3a9b",
  "scopes": ["accounts:read", "transactions:read"],
  "redirect_uri": "https://app.yourco.io/callback"
}

# Response 201 Created
{
  "session_id": "ses_3c8e2f1a",
  "redirect_url": "https://connect.banklyra.com/...",
  "expires_at": "2026-03-15T11:00:00Z"
}

The Problem

Integrating one bank takes 9 months. You need 2,000.

  • Each European bank has a different PSD2 API spec, authentication flow, and error format — requiring months of per-bank engineering.
  • Maintaining consent flows, token refresh, and SCA redirects for hundreds of institutions is a full-time platform team job.
  • Bank API uptime varies from 94% to 99.9% — without normalisation, your product's reliability is only as good as the weakest bank.
  • Regulatory requirements — FCA AISP registration, PECR consent records, UK GDPR data residency — compound every integration.
How It Works

From integration to live data in three API calls

BankLyra abstracts every bank's quirks behind a single unified API. Your team writes one integration; we handle the rest.

Architectural diagram showing fintech app connecting to BankLyra unified API layer which fans out to multiple European bank connections
01

Connect

POST to /connect — we redirect your user through the bank's PSD2 consent flow and handle SCA. Session tokens returned to your callback URL.

02

Query

Call /accounts, /transactions, or /balances. Responses are normalised to a consistent schema regardless of which bank your user chose.

03

Automate

Subscribe to webhooks for real-time balance updates, transaction events, and consent expiry notifications — so your product stays live without polling.

Coverage

Every major European banking market, connected

From the UK's Open Banking standard to Germany's NextGenPSD2, France's DSP2 implementations, and beyond — BankLyra covers the markets your users are in.

View full coverage
2,000+
Bank connections
28
Countries covered
99.2%
Aggregate uptime
<200ms
Median API latency
GB
DE
FR
NL
ES
IT
SE
PL
PT
BE
AT
DK
FI
IE
NO
+13

Everything your open banking integration needs

From raw data access to production-grade reliability features — BankLyra covers the full integration surface.

Account Aggregation

Retrieve accounts, balances, and transaction history in a normalised schema. Supports current, savings, and credit accounts across all covered institutions.

AIS →

Balance Checks

Real-time balance queries for affordability checks, credit decisioning, and identity verification. Polling-free with webhook-push when balances change.

AIS →

Payment Initiation

Initiate account-to-account payments via PSD2 PISP access. Immediate confirmation, no card rails, lower processing costs. UK Faster Payments and SEPA supported.

PIS →

Consent Management

Consent lifecycle API tracks grant scope, expiry dates, and revocation events. Audit logs meet UK GDPR and PECR requirements out of the box.

Compliance

Webhooks

Subscribe to transaction events, balance changes, and consent state transitions. Signed payloads with retry logic, delivery guarantees, and dead-letter queuing.

Docs →

SDKs & Libraries

Node.js, Python, Go, and Java SDKs. OpenAPI spec for any language. Postman collection, sandbox environment, and mock bank for development.

Quickstart →
Developer Experience

Built for engineering teams that ship fast

  • Sandbox environment with mock banks — test every edge case before touching production credentials
  • OpenAPI 3.1 spec with interactive explorer — generate client code in any language in seconds
  • Normalised error codes across all banks — one error-handling layer covers every institution
  • Idempotent POST endpoints — retry-safe payment initiation and consent creation
  • Dashboard logs every API call with full request/response trace — debug production issues in minutes
Start with Quickstart API Reference
GET /accounts 
# Fetch connected accounts
GET /v1/accounts?session=ses_3c8e2f1a

HTTP/1.1 200 OK
{
  "accounts": [
    {
      "id": "acc_uk_hsbc_9f2b",
      "iban": "GB29MIDL40051512345678",
      "account_name": "Current Account",
      "currency": "GBP",
      "balance": {
        "available": 4218.53,
        "current": 4318.53
      }
    }
  ]
}
Compliance

Designed with regulatory requirements in mind

Open banking is a regulated activity. BankLyra is built with PSD2, UK Open Banking, GDPR, and PECR requirements as first-class considerations — so your product benefits from that foundation.

PSD2 EU Payment Services Directive 2
UK Open Banking OBIE standard conformant
UK GDPR Data Protection Act 2018
SCA / PECR Strong Customer Authentication
UK Data Residency Data processed in UK/EEA regions
From Engineering Teams

Built with feedback from fintech builders

We went from bank integration hell to a working prototype in under a week. The normalised error codes alone saved us a month of defensive coding across different bank responses.

James K.
CTO, lending platform

The webhook reliability is what sold it for us. Real-time balance notifications without polling — that's what our affordability check flow needed. Delivered sub-200ms on average.

Anya M.
Platform engineer, neobank

The sandbox with mock banks is exceptional. We simulated bank downtime, consent expiry, partial data — every edge case before touching a real bank API. QA went from weeks to days.

Ravi L.
Head of Engineering, fintech startup

Ready to ship open banking in days?

Get API keys now and connect your first bank account in under an hour. No sales call needed.

Get API Keys Free Talk to the team