KibiPay — payments infrastructure for every rail

KibiPay gives banks and fintechs one signed REST API across every rail — UK schemes (Faster Payments, Bacs, CHAPS — simulated), a live Mojaloop switch for mobile money, and Solana for crypto settlement — held together by a genuine double-entry ledger, per-rail floats, an FX service, and a treasury that rebalances through a USDC-on-Solana reserve. Durable workflows run on Temporal.

What KibiPay does

KibiPay routes each payment to the right scheme by destination and settles it against a real double-entry ledger, so one integration reaches domestic instant rails, cross-border instant rails (SEPA Instant, TCH RTP), Mojaloop mobile money, and on-chain USDC. A cross-rail Directory resolves aliases, handles, and QR codes; an FX desk prices cross-currency legs against a verifiable quote; and Request-to-Pay and variable recurring mandates cover pull payments.

Who it's for

Banks, fintechs, and platforms that need to move money across many rails without building a separate integration for each — and AI agents that need to transact over those rails programmatically through the external MCP server, with per-agent spend caps and consent.

Compliance built in

Every payment is screened for fraud and AML at a single choke point before it settles: self-hosted OFAC and EU sanctions screening plus real-time transaction monitoring, with ISO 20022 messaging (pain.001 / pacs.008) throughout. Operators get one console — a control tower, hold queue, audit chain, and end-of-day reconciliation — that turns the usual late-night payments incident into a click.

For developers

Read the API documentation and the OpenAPI spec (typed problem+json errors, cursor pagination, rate-limit headers), see agent guidance in llms.txt, explore the payments blog, try the customer pay surface, or open the operator console.

Loading the interactive experience…