Platform
The Protocol-Native Banking Stack
Three layers that replace the entire legacy banking middleware stack. Protocol Engine for banking primitives. MCP Orchestration for AI agents. Composable Interface for dynamic UX.
Layer 1
Protocol Engine
Banking protocols become programmable APIs. Every operation — transfers, account openings, compliance checks — is a versioned protocol definition with built-in validation, compliance rules, and audit trails.
Native support for ISO 8583, ISO 20022, and SWIFT message types. No adapters, no translation layers — the protocol is the API.
View Protocol Docs// Define a banking protocol
const transferProtocol = protocol.define({
name: 'funds_transfer',
version: '2.1.0',
standard: 'ISO_20022',
input: z.object({
debitAccount: z.string().iban(),
creditAccount: z.string().iban(),
amount: z.number().positive(),
currency: z.enum(['AED', 'USD', 'EUR', 'SAR']),
reference: z.string().max(140),
}),
execute: async (params, ctx) => {
await ctx.compliance.screen(params);
await ctx.ledger.debit(params.debitAccount, params.amount);
await ctx.ledger.credit(params.creditAccount, params.amount);
return ctx.receipt.generate(params);
},
});Permission Boundaries
Every MCP tool call is scoped to explicit permission sets. Agents can only access operations their role allows.
Full Audit Trail
Every agent action is logged with full context — who requested it, which model decided, and what protocol executed.
Real-Time Governance
Compliance rules evaluate in real-time. Transactions that violate policy are blocked before execution, not after.
Layer 2
MCP Orchestration
AI agents call banking operations through the Model Context Protocol. Not API wrappers around chat — real transactional agents with governance boundaries, audit trails, and compliance checks at every step.
The agent governance framework ensures every AI action is permissioned, logged, and reversible. Banks maintain full control while their customers get instant, conversational experiences.
Layer 3
Composable Interface
React components that auto-generate from protocol state. No static forms, no rigid page layouts. The interface assembles itself based on context, channel, and user intent — chat, web, mobile, or API.
Chat-Native
Conversational interfaces that handle the full transaction lifecycle. No menus, no navigation — just natural language banking.
Context-Aware
UI components adapt to the user, their device, their history, and their intent. Every interaction is personalized at the protocol level.
Channel-Agnostic
One protocol definition powers web, mobile, WhatsApp, and API channels. Build once, deploy everywhere — with full fidelity.
Architecture
The Full Stack
From core banking to customer interface — five layers, one protocol.
Customer Interfaces
Chat, Web, Mobile, API
AI Agents
MCP-powered LLM agents
MCP Servers
Tool definitions & orchestration
Protocol Adapters
ISO 8583 / 20022 / SWIFT
Core Banking
Ledger, accounts, compliance
See the Platform in Action
Book a 30-minute demo and see how protocol-native banking works — from API call to customer interaction.