Banking and insurance
Expose your APIs and your agents while keeping track of every decision.
Flexway helps you meet your sector's traceability, resilience and strong authentication requirements, on your own infrastructure.
What Flexway decides, on your infrastructure
Who calls, what Flexway decides, what is called: each route is a use case of your sector. Dashed: what is coming.
Architecture for banking and insurance: third-party providers, online banking and AI agents go through Flexway, on your infrastructure. Flexway audits every decision, bounds agent delegation with an exchanged token, cuts off a failing upstream and identifies each provider by its client certificate, in front of core banking, payment services and claims management. A provider without a declared certificate gets a 401. Coming: sender-constrained tokens.
- Third parties
- Licensed third-party providers: each is identified by its client certificate, and every decision is audited.
- Online banking
- Your online bank: its calls to the core banking system go through Flexway, under identity, quota and circuit breaker.
- AI agents
- AI agents: they call MCP tools and models through Flexway, under the same identity, quota and audit as an API.
- Client certificate (mTLS)
- The client certificate (mTLS) identifies each partner and binds it to its tenant, passed on proven to your services.
- Sender-constrained tokens
- Planned: Tokens bound to their holder (mTLS or DPoP): a stolen token is useless without its holder's key.
- Chained decision audit
- Every authorization decision is logged in a chained, verifiable audit, without request content.
- Bounded agent delegation
- An agent acts on a person's behalf for a bounded time and depth; the token is exchanged (RFC 8693), revocable in cascade.
- Circuit breaker per upstream
- A circuit breaker and a bulkhead per upstream, with shedding: one slow service does not bring the others down.
- Core banking
- Your core banking system: it receives only authenticated, audited calls protected by a circuit breaker.
- Payment services
- Your payment services: behind Flexway, each call keeps its identity and its audit.
- Claims management
- Your claims management: called by agents whose delegation is bounded and audited.
- Line: one route
- Interchange: shared decision
- Request
- Model or tool call
- Refusal
- Your infrastructure
- Planned
- Client certificate (mTLS)identity of each provider
- Sender-constrained tokensplanned
- Chained decision auditwho, on whose behalf, why
- Bounded agent delegationexchanged token, lifetime, depth
- Circuit breaker per upstreambulkheads, load shedding
1A third-party provider initiates a payment
What Flexway decidesIts declared client certificate identifies it; without a certificate, or with an undeclared one, the request gets 401 before any service.
What is protectedOnly identified providers reach your payment services.
2An AI agent handles a claim for a customer
What Flexway decidesThe token is exchanged (human subject, agent actor); delegation is bounded in lifetime and depth.
What is protectedThe upstream never receives the caller's token; every decision goes into the chained audit.
3An upstream slows down in the middle of the day
What Flexway decidesThe circuit breaker opens, bulkheads cap in-flight requests, load shedding protects the rest.
What is protectedAn incident stays contained to one upstream.
Third parties
Licensed third-party providers: each is identified by its client certificate, and every decision is audited.
Routes through here
Online banking
Your online bank: its calls to the core banking system go through Flexway, under identity, quota and circuit breaker.
Routes through here
AI agents
AI agents: they call MCP tools and models through Flexway, under the same identity, quota and audit as an API.
Routes through here
Client certificate (mTLS)
The client certificate (mTLS) identifies each partner and binds it to its tenant, passed on proven to your services.
- Decision
- identity of each provider
- Catalogue features
- API keys and client mTLS as first-class identities
Routes through here
Sender-constrained tokens
Planned: Tokens bound to their holder (mTLS or DPoP): a stolen token is useless without its holder's key.
- Catalogue features
- Sender-constrained tokens: mTLS (RFC 8705) or DPoP (RFC 9449)
Chained decision audit
Every authorization decision is logged in a chained, verifiable audit, without request content.
- Decision
- who, on whose behalf, why
- Catalogue features
- Chained audit log of authorisation decisions
Routes through here
Bounded agent delegation
An agent acts on a person's behalf for a bounded time and depth; the token is exchanged (RFC 8693), revocable in cascade.
- Decision
- exchanged token, lifetime, depth
- Catalogue features
- RFC 8693 token exchange: human subject, agent actor ; Delegation bounded in time and depth, cascading revocation
Routes through here
Circuit breaker per upstream
A circuit breaker and a bulkhead per upstream, with shedding: one slow service does not bring the others down.
- Decision
- bulkheads, load shedding
- Catalogue features
- Circuit breaker with half-open state ; In-flight request cap per upstream (bulkhead) ; Adaptive load shedding under saturation
Routes through here
Core banking
Your core banking system: it receives only authenticated, audited calls protected by a circuit breaker.
Routes through here
Payment services
Your payment services: behind Flexway, each call keeps its identity and its audit.
Routes through here
Claims management
Your claims management: called by agents whose delegation is bounded and audited.
Routes through here
What the sector requires
- PSD2 · open bankingAuthenticated partners
- Third-party providers access by client certificate, bound to a tenant and to operations; an agent presenting an OIDC token has it exchanged for the upstream that requires it, never relayed.
- Internal controlAuditable decisions
- Who called what, on whose behalf, and why the request was accepted or refused: a chained audit, without request content.
- DORAResilience and incident detection
- Circuit breakers and bulkheads per upstream, load shedding, alerts, SLOs and traces in the console.
- AI ActAgents under control
- A bounded agent chain, tools declared in the contract, cost per agent; per-user budgets planned.
How Flexway answers
Authenticated partners
- API keys and client mTLS as first-class identitiesDelivered · v0.1.0
- RFC 8693 token exchange: human subject, agent actorDelivered · v0.1.0
Auditable decisions
- Chained audit log of authorisation decisionsDelivered · v0.1.0
Resilience and incident detection
- Rate per caller (token bucket)Delivered · v0.1.0
- In-flight request cap per upstream (bulkhead)Delivered · v0.1.0
- Circuit breaker with half-open stateDelivered · v0.1.0
- Quota per tenant per day and monthDelivered · v0.1.0
- Adaptive load shedding under saturationDelivered · v0.1.0
- Built-in alerts: thresholds per upstream or operation, webhook notificationDelivered · v1.3.0
- W3C traces propagated end to endDelivered · v0.1.0
Agents under control
- Delegation bounded in time and depth, cascading revocationDelivered · v0.1.0
- MCP surface: the contract's operations offered as toolsDelivered · v0.1.0
- MCP federation: existing MCP servers under the same authorisation, quota and auditDelivered · v0.1.0
State in Flexway's latest published release; a feature is marked delivered only with its release.
What Flexway does not do
- Flexway is not, on its own, enough to make an organisation meet its obligations: it provides controls and traces that your compliance process uses.
- No financial-grade security profile (such as FAPI) is claimed to date.
Let's talk about your gateway
Flexwiz is a young company: you talk directly with the person who founds it. Tell us what you want to run through Flexway. We talk about your infrastructure and your digital sovereignty requirements.
Online booking is coming soon; until then, an e-mail is enough.