Skip to content
OpenBanqing

OpenBanqing — Conventional open-banking infrastructure

Open-banking infrastructure · early access

One API contract for the open-banking stack.

OpenBanqing unifies payments, accounts, consents, KYC, and capital-markets rails behind one PSD2 / PSD3 / FAPI 2.0 / FDX contract — so engineering teams can ship product instead of integrating vendors.

Read the developer docs →
PSD2PSD3FAPI 2.0FDX 6.0Open Banking UKBasel IIIIFRS 9SOC 2+ 6 more

Compliance frameworks listed describe the design scope. See the compliance page for current attestation status of each frame.

POST /obf/v1/payments/initiateexample
{
  "rail":      "SEPA_INSTANT",
  "amount":    { "value": "150.00", "currency": "EUR" },
  "debtor":    { "iban": "DE89 ••• 0130 00" },
  "creditor":  { "iban": "FR14 ••• 13M02 606" },
  "reference": "Invoice 2026-04-1182",
  "consent":   "csnt_01HK2NX9ZP",
  "compliance": {
    "sca":       "PASSED",
    "fapi_v2":   true,
    "screening": { "ofac": "clear", "uk": "clear" }
  }
}
Rail
SEPA Instant
Auth
FAPI 2.0
Audit
structured

Illustrative request. Live sandbox available on request.

8
Rail categories
Payments, capital markets, KYC, treasury, trade, ops
1
API contract
OpenAPI 3.1 · semver-stable · /obf/v1
FAPI 2.0
Authorization
DPoP · PAR · MTLS · OAuth 2.1 baseline
ISO 20022
Native messaging
End-to-end across payments and settlement
How it works

Connect once. Compose anything. Comply by default.

OpenBanqing sits between your product and a fragmented landscape of cores, rails, and regulators. One contract; one observability surface; one audit trail.

01
Connect

Connector interfaces for the major core-banking platforms (Temenos, Finastra, Mambu, Thought Machine) and PSP rails (Visa, Mastercard, Stripe, Adyen). The connector layer is open-source so you can audit, extend, or self-host.

02
Compose

Compose retail, commercial, wholesale, and capital-markets products from a normalised rail catalogue. ABAC policies enforce tenant, role, and jurisdiction at every call so you can ship multi-region without forking your code.

03
Comply

Every request is signed, audited, and policy-evaluated. Evidence is structured and exportable for SOC 2, ISO 27001, PSD2, FAPI 2.0, FDX, and ISO 20022 audits. Auditors get read-only views; you keep operational control.

One request, one pipeline

What happens between POST and 201 Created

01 / 6

Edge ingress

≈ 6 ms of 59 ms illustrative budget

TLS 1.3 termination at the edge. DPoP proof verification. Per-tenant rate limit and burst control. The edge layer is stateless — one Cloudflare Worker per region.

Illustrative latency budget — design target
Numbers are a representative budget for an in-region SEPA Instant call. Real latency depends on the rail, the core, and the screening provider.
Architecture

One platform. Many connectors. Zero lock-in.

The edge layer is stateless. The rail catalogue is the only integration boundary. The cores are pluggable — connectors live under Apache 2.0 so you can audit, extend, or fork them.

Read why we built it this way →
Architecture

Edge to core, with one auth and audit pipeline

Hover any block to see what it does. The edge layer is stateless; the rail catalogue is the integration boundary; the cores are pluggable.

OpenBanqing platform architectureYour applicationWeb · mobile · backendEdgeTLS · DPoP · rate limitAuthorisationCerbos ABAC · FAPI 2.0Rail cataloguePayments · accounts · KYCAudit pipelineStructured JSONLScreening providersOFAC · EU · UN · UKBanking coresTemenos · Finastra · MambuPayment schemesSEPA · FedNow · FPS · gpiCard networksVisa · MastercardPSP integrationsStripe · Adyen · in-house
OpenBanqing platform

Rail catalogue

The rail layer normalises payments, accounts, consents, KYC, capital markets, and treasury into one OpenAPI contract. Picking a rail is a runtime field, not a build-time fork.

Platform

Every conventional banking rail, one platform.

Replace fragmented vendor integrations with a single API that normalises core-banking, payments, KYC/AML, and regulatory reporting under one authorisation and audit pipeline.

🔒

PSD2 / PSD3 / FAPI 2.0

Strong Customer Authentication, dynamic linking, DPoP, PAR, message signing — implemented to the published specifications and regression-tested against the open conformance suites.

🌐

FDX 6.0 + Open Banking UK

One product surface across UK FCA, EU EBA, and US FDX standards. Region routing happens at the edge so you don't fork your application by jurisdiction.

📊

Basel III + IFRS 9

RWA, LCR, and NSFR computation patterns built in. Forward-looking ECL provisioning across IFRS 9 stages 1, 2, and 3 with structured lineage suitable for audit review.

⚡

Real-time payments, every rail

SEPA Instant, Faster Payments, FedNow, RTP, PIX, UPI — and SWIFT gpi tracking on cross-border — all behind one /payments endpoint with consistent error envelopes.

🏦

Multi-rail core banking

Hot-swappable banking-core connectors. The connector boundary is contract-typed so you can migrate from a legacy mainframe to a modern core without rewriting your product code.

🛡

Operational resilience

Multi-region, multi-AZ, edge-distributed by design. Structured failure pipeline, fingerprinted incidents, and DORA-aligned ICT register of information are part of the platform — not an afterthought.

What you actually get

An infrastructure platform — not a marketing surface.

OpenBanqing is in early access. The product is what we ship: a published OpenAPI 3.1 contract, open-source connectors, and a compliance pipeline that you can audit before you commit.

Browse the developer portal →
Single product surface

Replace four to six vendor SDKs with one OpenAPI 3.1 contract that covers payments, accounts, consents, KYC/AML, capital markets, and treasury.

Compliance, not bolt-on

Every endpoint passes through the same authorization, consent, and audit pipeline — you cannot accidentally ship a non-compliant call.

Connectors you can read

Open-source core-banking and PSP connectors under Apache 2.0. Audit them, fork them, or build your own against the published interface.

Bring-your-own-cloud

Enterprise tier deploys inside your own AWS, GCP, or Azure tenant. Zero data egress. Helm charts, Terraform modules, and a runbook ship with the product.

Rails

Browse the rails. Pick the one you need.

Filter by category or search by spec. Every rail is normalised behind one contract and one authorisation pipeline.

Rail catalogue

Browse the rails behind the contract

Every rail is normalised behind the same authorisation and audit pipeline. Filter by category, or search by name or specification.

  • SEPA Credit Transfer
    Payments
    ISO 20022 pacs.008
  • SEPA Instant Credit Transfer
    Payments
    EBA TIPS · ISO 20022
  • FedNow
    Payments
    ISO 20022 · US instant
  • TCH RTP
    Payments
    ISO 20022 · US real-time
  • Faster Payments (UK)
    Payments
    ISO 20022 migration
  • SWIFT gpi
    Payments
    MT to MX migration · gpi tracker
  • PIX (Brazil)
    Payments
    BCB · ISO 20022
  • UPI (India)
    Payments
    NPCI
  • Account Information Service
    Accounts
    PSD2 AIS · OB UK · FDX
  • Balances
    Accounts
    Real-time and posted
  • Transactions
    Accounts
    ISO 20022 camt.052/053
  • Standing orders & direct debits
    Accounts
    Berlin Group · OB UK
  • Consent management
    Consents
    AISP · PISP · CBPII
  • Consent revocation
    Consents
    Webhook + API
  • Consent dashboard
    Consents
    White-label UI
  • KYC orchestration
    KYC / AML
    FATF · per-jurisdiction
  • Sanctions screening
    KYC / AML
    OFAC · EU · UN · UK · AUSTRAC
  • PEP screening
    KYC / AML
    Pluggable provider
  • Transaction monitoring
    KYC / AML
    Rules + ML provider hooks
  • FX execution
    Capital markets
    Mid-market quoting · ISO 20022
  • Securities order routing
    Capital markets
    FIX 4.4 / 5.0
  • Settlement
    Capital markets
    ISO 20022 sese.023/024
  • Liquidity management
    Treasury
    Basel III LCR / NSFR
  • RWA computation
    Treasury
    Basel III standardised
  • IFRS 9 ECL
    Treasury
    Stages 1 / 2 / 3
  • Letters of credit
    Trade finance
    URDG / UCP 600
  • Guarantees
    Trade finance
    ISO 20022 · MT 760
  • Supply-chain finance
    Trade finance
    Reverse factoring
  • Audit pipeline
    Operations
    Structured JSONL · append-only
  • Webhooks
    Operations
    Replay + retry · idempotency
  • Regulatory reports
    Operations
    PSD2 · DORA · per-jurisdiction
Showing 31 of 31 rails. The full registry ships with the SDK and is callable behind one OpenAPI contract.
Compliance map

Fourteen frameworks. Honest status on every one.

We tell you exactly where each frame stands today — designed for, in implementation, audit scheduled, or certified — and we update it as the auditors sign off.

Compliance map

Where we are on every framework

We don't claim certifications we don't hold. Hover or tap any frame to see its current status.

Designed for5
In implementation6
Audit scheduled / in progress3
Certified0

PSD2 / PSD3

Designed forEU · EBA

Berlin Group NextGenPSD2 v1.3.12 schema parity

See the compliance page for full evidence text on every frame.

Frequently asked questions

Everything regulated institutions need to know — answered.

The questions our solutions engineers field daily, with the detail your procurement, security, and compliance teams will ask in week two of evaluation.

Early access. We have a published OpenAPI 3.1 contract, a runnable sandbox, open-source connectors, and a small cohort of design partners working with us through pilot and conformance. We don't claim production references we don't have.
Most early-access teams are in a sandbox tenant within one business day of an approved request. Production cutover depends on your own licence (AISP / PISP / e-money / banking), your core integration, and the regulator's review of the change — typical pilot-to-production windows run six to twelve weeks.
OpenBanqing is a B2B platform — we operate under your AISP / PISP / e-money / banking licence, not in place of it. We provide the technical infrastructure, structured evidence material for your auditors and regulators, and FCA / EBA-aligned change-management documentation. We don't hold your licence.
FAPI 2.0 Baseline + Advanced — DPoP tokens, MTLS client auth, PAR (RFC 9126), JAR (RFC 9101). SCA workflows are implemented for redirect, decoupled, and embedded modes. Your customers never see our brand — every screen is white-labelled to yours.
Customer-elected data residency: EU, UK, US, and APAC regions. Cross-region transfers go through Standard Contractual Clauses with supplementary measures where required. Our DPO maintains the sub-processor list with 30-day change notice. Bring-your-own-cloud removes the question entirely on the enterprise tier.
Account aggregators stop at AIS. OpenBanqing covers AIS + PIS + payment-scheme rails (SEPA Instant, FedNow, SWIFT gpi, Faster Payments) + capital-markets + treasury + consent dashboards behind a single OpenAPI contract. The connector layer is open-source, so the integration boundary is auditable, not a vendor black box.
Tier-based subscription with usage-based per-API-call metering. The enterprise tier includes bring-your-own-cloud deployment, dedicated authorisation decision points, 24×7 support with named contacts, and access to the current compliance evidence pack under mutual NDA. Final pricing is quoted per tenant.
The platform is designed for multi-region active-active, with a published 99.95% uptime SLA on the enterprise tier. Current operational metrics are reported on the status page; SLA credits are governed by the contract, not by support tickets. Status history is public.

Pick the conversation that matches your week.

Each route opens a 30-second form. Replies come from info@openbanqing.com within one business day.

Book a demo

Live walk-through of the API, dashboard, and SDKs with one of our solutions engineers — not a sales BDR.

Security review

Architecture deep-dive, ISMS scope, sub-processor list, DPIA templates, and current attestation status under mutual NDA.

Pricing & procurement

Custom quote based on volume, regions, and tier. Includes ramp-up discounts and multi-year terms.

Partner with us

Banks, processors, ISVs, and system integrators — apply to the OpenBanqing partner network.

We reply from info@openbanqing.com within one business day. We never share your details with third parties.

Related: About · Why OpenBanqing · Features · Pricing · Compliance · Developers · Partners · Contact