Skip to content
OpenBanqing
← OpenBanqingWhy OpenBanqing

Cut the integration tax on open banking — without cutting compliance corners.

One API contract. A normalised rail catalogue. A single authorisation and audit pipeline. Open-source connectors you can actually audit. Bring-your-own-cloud on the enterprise tier.

Open vs commercial

What ships open-source

Open under Apache 2.0

  • PSD2/PSD3-aligned connector schemas open under Apache 2.0
  • FAPI 2.0 auth pipeline reference implementation
  • OpenAPI 3.1 spec for every public endpoint
  • TypeScript, Python, Go, and Java / Kotlin SDK skeletons
  • Berlin Group NextGenPSD2 conformance fixtures
  • Open Banking UK v3.1 schema parity files

What we charge for

Commercial platform

  • Multi-tenant SaaS hosting (api.openbanqing.com)
  • Managed FAPI 2.0 authorisation server + consent store
  • Core-banking connector runtime (Temenos, Finastra, Mambu, FIS)
  • Real-time payment routing: SEPA Instant, FedNow, RTP, SWIFT gpi
  • BYOC / on-prem deployment + Helm charts + Terraform modules
  • Named CSM + 24×7 SLA + SOC 2 evidence packs
1 contract
OpenAPI 3.1, semver-stable, covering accounts, payments, consents, KYC, and capital markets.
FAPI 2.0
DPoP, PAR, MTLS, and JAR built into the auth pipeline — not a per-rail extension.
Apache 2.0
Connectors and SDKs are open-source — audit, fork, or build your own against the published interface.
BYOC
Enterprise tier deploys inside your AWS, GCP, or Azure. Helm charts and Terraform modules ship with the product.

Before vs. after

What integration looks like on legacy stacks today — and what it looks like on OpenBanqing.

Fragmented core connectors

Before

Every core integration is bespoke, six to twelve months, brittle on every release.

With OpenBanqing

One API contract that abstracts Temenos, Finastra, Mambu, FIS, Fiserv, and Thought Machine behind a contract-typed connector boundary.

Compliance bolted on late

Before

PSD2 / FAPI / FDX retrofitted in the final quarter, auditor surprises, late-stage re-architecture.

With OpenBanqing

A single authorisation and audit pipeline gates every request. SCA, DPoP, PAR, and consent are part of the path — not a per-endpoint reimplementation.

The payments-rail zoo

Before

SEPA, SWIFT, FedNow, RTP, FPS — five SDKs, five schemas, five operational rotas.

With OpenBanqing

One ISO 20022 abstraction. Pick the rail at call time, not at build time. Errors and webhooks share one envelope.

Auditor evidence gaps

Before

Manual evidence collection before every SOC 2 or ISO audit — weeks of engineering time spent on screenshots and spreadsheets.

With OpenBanqing

Evidence is structured JSON written by the platform itself. Export on demand for SOC 2, ISO 27001, PSD2, and DORA reviews.

One pipeline for every rail

Every request flows through one authorisation and audit pipeline. SCA, DPoP, PAR, MTLS, consent lookup, ISO 20022 validation, sanctions screening, and audit logging are part of the same predictable path. No per-rail forks. No per-region special cases.

  • ✓ ABAC authorisation per resource and per action
  • ✓ FAPI 2.0 with DPoP, PAR, and MTLS
  • ✓ ISO 20022 native across payments and settlement
  • ✓ Structured evidence exportable for audit
Book a 30-min architecture call →
Related: About · Features · Pricing · Compliance · Contact