Skip to content
VKraft Software ServicesBook a free consultation
finX Open Finance Platform

Open finance, live in weeks.

Secure, consent-driven APIs for partners and customers, running inside your own data centre or private cloud, in front of your core rather than inside it. Security, consent and data control are built in.

What is in the box

FAPI 2.0 authorisation serverOAuth 2.0, OIDC, mTLS, PAR, DPoP and JWS/JWE, pre-built and tested
Consent engineCapture, renew and revoke, with an immutable audit trail
Integration StudioLow-code core-banking adapters, authored by your own architects
Partner sandboxOpenAPI 3.0 specs, mock data and a full FAPI 2.0 test suite
Zero-storage relayPermissioned data passes through rather than being copied

From a multi-year build to a first release in weeks

WeeksNot years, to a first release
FAPI 2.0Security pre-built and tested
Zero-storageData stays in your environment
One platformReused for every next use case

Why finX

The regulated plumbing, already built

Open finance is easy to announce and hard to run securely at scale. None of this differentiates your bank, and all of it sits between you and your first partner.

Authorisation

Build an OAuth server, add mTLS, PAR, DPoP and PS256 signing, then prove the profile holds.
finXFAPI 2.0 pre-built and tested, with CSR, key rotation and JWKS hosting automated.

Consent

Schema, approval screens, grant, renew and revoke, plus an audit trail a regulator accepts.
finXTurnkey consent engine with published approval screens and an immutable audit trail.

Core mapping

An adapter per endpoint, maintained through every core release.
finXCamel route templates and SDKs, mapped once, low-code, by your own architects.

Partner testing

A sandbox, mock data and a test suite before you will expose production.
finXPartner sandbox with OpenAPI specs, mock data and a full FAPI 2.0 test suite.

Staying current

Rework every time the standard or a partner's needs change.
finXA mapping change and a test re-run, because schema is configuration.

Architecture

In front of the core, not inside it

Partners, customers and regulators connect at the edge, secured end to end with FAPI 2.0. finX does not replace your core, identity provider or API gateway.

YOUR DATA CENTRE OR PRIVATE CLOUD · ZERO-STORAGE RELAYWHO CONNECTSfinX PLATFORMYOUR SYSTEMSPartners & fintechsTPPs · super-apps · lendersYour own appsMobile · web · partner portalsThe customerAuthorises, scopes, revokesRegulator & auditFull access trailFAPI 2.0mTLS · PARGateway & Authorization ServerFAPI 2.0 · OIDC · JWS/JWE · tokensfinX EngineConsent engine · API orchestrationIntegration StudioCamel routes · SDKs · schema mappingfinX Studio · auditImmutable trail · registry · sandboxADAPTERSCAMEL · SDKCore bankingAccounts · transactionsIdentityCustomer authenticationProducts & dataProduct catalogue · reportingSIEM & monitoringLogs · alerts · evidence

Scroll the diagram sideways →

FAPI 2.0OAuth 2.0 + OIDCmTLSPARPKCEDPoPJWS + JWEOpenAPI 3.0ISO 20022 alignedISO 27001 aligned

Production-ready, deployed your way

Performance
Cached consent lookups, instant invalidation on revoke, a stateless gateway that scales out.
Availability
Active-active, no single point of failure, zero-downtime upgrades and automated failover.
Resilience
Circuit breakers, retries and backpressure protect legacy cores.
Deployment
Containerised: your cloud tenancy, on-premises or hybrid, with local regions for data residency.

How it works

One consented data request, end to end

Every step is secured with FAPI 2.0. Customers can revoke consent at any time, and every access is recorded.

  1. 1Request

    The customer asks a partner app to share their account data.

    Customer
  2. 2Secure call

    The partner calls finX over mTLS with DPoP-bound tokens.

    Partner
  3. 3Consent

    A pushed authorisation request starts the consent flow.

    finX
  4. 4Approve

    The customer approves or denies on your consent screen.

    Customer
  5. 5Authorise

    The active consent scope is checked on every call.

    finX
  6. 6Fetch

    Bank data is fetched and mapped to the agreed schema.

    Bank
  7. 7Respond

    A signed, encrypted response goes back to the partner.

    finX

Product preview

finX in action, for every participant

One platform, three views. The customer stays in control: they choose what to share and for how long, sign in only at their own bank, and can renew or revoke any consent at any time.

Customer app · home: One view of balances, spending and insights across every bank and provider the customer connects.
CustomerCustomer app · home
One view of balances, spending and insights across every bank and provider the customer connects.
Customer app · consents: What is shared, when it expires and when it was last used, with renew and revoke in one place.
CustomerCustomer app · consents
What is shared, when it expires and when it was last used, with renew and revoke in one place.
Data consumer console: Admin view of customers with linked banks, active consents, data calls and alerts.
Data consumerData consumer console
Admin view of customers with linked banks, active consents, data calls and alerts.
Integration Studio: Consent submissions, grant rate and trends by data consumer.
Data providerIntegration Studio
Consent submissions, grant rate and trends by data consumer.
Illustrative screens with sample data. Bank names are fictional.See finX running live

What you get

One platform for open finance and partner APIs

Take the full stack or individual modules, white-label ready, all configured from the same console.

FAPI authorisation server

Bank-grade security, out of the box

OAuth 2.0, OIDC, mTLS, private_key_jwt and PAR, with PS256 signing and optional JWE. Certificates, key rotation and JWKS hosting are automated.
Consent management

Capture, govern and revoke consent

A schema builder and published approval screens. Every grant and revocation from one console, with compliance exports on demand.
Integration Studio

Map the core once

Apache Camel templates and SDKs in Java, Python and Node.js map legacy core APIs to your schema, so a new API is a mapping change.
Partner sandbox

Partners integrate before production

OpenAPI 3.0 specs, mock data, a full FAPI 2.0 test suite and a Postman collection for self-service onboarding.
Consent notifications

Customers informed on WhatsApp

Consent confirmations, revocation alerts, 7-day expiry warnings and data-access alerts via Infobip, with SMS or email fallback.
Sharing intelligence

Turn data sharing into insight

Providers see which partner apps access their customers' data and why consents are revoked; unusual requests are flagged.

Use cases

Start with one use case. Reuse the platform for the next.

Every new use case runs on the same security, consent and audit foundation, so each release is faster than the last.

01

Customer-permissioned data sharing

Share account and transaction data with partners on the customer's consent, FAPI-secured.

Reuses FAPI server · consent engine

02

Embedded finance & BaaS

Expose bank products to fintechs, super-apps and merchants through governed API channels.

Reuses Gateway · Integration Studio

03

Partner & fintech onboarding

Onboard, test and monitor partners in days, self-service from day one.

Reuses Sandbox · developer portal

04

Cross-sector data APIs

The same FAPI-grade pipes for insurance, wealth, telco or any consent-driven integration.

Reuses Auth stack · zero-storage relay

05

Internal API governance

One consent and audit fabric for inter-department and subsidiary data sharing.

Reuses Audit trail · registry

06

Digital banking foundation

Consent, identity and audit as the base for the bank's digital stack.

Reuses Full platform

Questions

Answers before you ask

Consent, authorisation and the first read endpoints are the usual first milestone, in weeks rather than a multi-year programme. The pace mostly depends on how much of your core is already exposed through a supported interface.

Get started

Request a demo

Tell us about your institution and we will schedule a short technical walkthrough of finX.

Your path to a first release

  1. 1
    Readiness assessmentFree
    A compliance readiness review of your current position.
  2. 2
    Scoping workshop1 day
    Core interfaces, data schemas, infrastructure and timeline.
  3. 3
    Sandbox & proposal
    Test finX APIs in the demo environment; a tailored proposal with timeline and cost.
  4. 4
    First APIs live
    Go live with partners, then expand use case by use case.

Loading security check…

Your details stay with VKraft and are used only to answer this enquiry.