SOLUTIONS

Solutions for central banks, payment networks, and closed-loop payment systems

Payment systems require offline capability to be a built-in part of the system, not as a collection of vendor-specific implementations. Crunchfish enables payment systems to introduce offline capability as a Layer-2 extension that preserves native settlement and liquidity control, while enforcing common rules across all participants. Offline rules, such as reservation limits, offline spending constraints, sequencing and expiry policies, certification criteria, and verification requirements, are defined and governed once at system level.

Offline capability is a built-in part of the system.

A key scalability mechanism is the use of receive-only offline terminals as acceptance points. Offline terminals allow payment systems to scale offline acceptance rapidly across users, merchants, and agents, independently of offline wallet deployment, making offline resilience achievable at system-wide scale.

Acceptance can scale independently of offline wallet rollout.

This capability is underpinned by Crunchfish’s patented Layer-2 architecture, which protects how offline payment instructions are executed, verified, converted, and settled under the authority of the underlying payment system. The patents ensure that offline capability can be deployed system-wide without introducing parallel ledgers, uncontrolled risk, or vendor-specific lock-in.

Solutions for banks and payment applications as service providers

Service providers compete on services and experience, not on rebuilding core payment infrastructure. Crunchfish enables service providers to integrate secure offline wallets that support sending offline payments under shared system rules, without redefining risk or settlement models. Offline spending is pre-funded through reservations held in the underlying payment system and enforced locally by offline wallets. All offline payments are verified before settlement, ensuring predictable outcomes. Because rules are governed at system level, offline payments are accepted network-wide without bilateral agreements.

Service providers gain offline capability without redefining risk or settlement.

Service providers retain responsibility for their payment services and customer interfaces, while Crunchfish provides secure offline wallet functionality, without shifting settlement authority, risk ownership, or governance responsibilities. Even where service providers have not yet integrated offline wallet functionality, their users can still receive offline payments through offline terminals deployed under system governance.

Solutions for technology providers

Technology providers enable deployment across platforms, rails, and markets. Crunchfish delivers reusable offline payment components, including offline wallet SDK, offline terminal SDK, offline backend components, and Layer-2 offline protocols and APIs, that can be integrated into switching platforms, wallet platforms, POS solutions, and payment infrastructure.

The Offline Wallet SDK and Offline Terminal SDK are available for iOS and Android, enabling deployment on standard smartphones and tablets used by consumers, merchants, and agents. At the same time, the offline architecture is not bound to smartphones: the same Layer-2 protocols, risk controls, and verification logic can be implemented in dedicated payment hardware, secure elements, and embedded devices, including terminals and other specialised form factors. This device-agnostic design allows technology providers to support offline payments across mobile applications and hardware environments while remaining aligned with system-level governance and settlement.

This allows technology providers to support offline capability across customers and rails using a common architecture, reducing integration complexity and accelerating deployment, without assuming operational or regulatory responsibility.

Integrate once. Deploy offline capability to multiple system and service providers.