Case study · In production

CaQeh

A peer-to-peer liquidity marketplace, built and operated by Taxel. The clearest example of how we work, because we carry it in production ourselves.

What people actually use

A participant sets the payment method they want to use, sees who is available nearby, and matches. Settlement runs over the rail they already trust: mobile money, a bank, or a card.

CaQeh — matching and payment flow

How a payment actually settles

Two participants are matched on proximity and availability. Value then moves over the rail they already use — mobile money, a bank, or a card — with limits, checks, and an audit trail applied on the way through.

Participants Participant A needs cash Participant B holds value CaQeh Matching engine proximity + availability Trust & safety limits, checks, audit trail Settlement rails Mobile money Bank transfer Card
CaQeh — matching and multi-rail settlement

The problem

Moving between cash and digital value is still awkward in many markets. People hold balances on one rail and need value on another, and the gap between them is filled informally, inconsistently, and often at poor rates.

What that demands

  • Matching participants who hold value against those who need it
  • Settling across rails that behave differently from each other
  • Enough trust and safety for strangers to transact

What we built

A peer-to-peer liquidity marketplace that matches people who need cash or digital payment support with nearby participants, settling over familiar rails — mobile money, banks, and cards.

Core system

  • Marketplace matching between participants
  • Multi-rail settlement across mobile money, banks, and cards
  • Trust and safety controls on live value movement

Around it

  • Structured logging, metrics, and alerting
  • Versioned releases with tested rollback paths
  • Audit trails on privileged actions

What operating it involves

We did not hand CaQeh over. Taxel hosts it, monitors it, releases to it, and is accountable when something breaks — which is a materially different commitment from delivering a build.

Day to day

  • Hosting and production operations
  • Monitoring, alerting, and incident response
  • Release, rollback, and change control
  • Security controls on live payment paths

Why it matters to clients

Visit caqeh.com

Where the practice is proven

CaQeh is where our operations, security, and release practices are proven before we apply them to client systems. See how an engagement runs →

Building something that has to stay up?

Tell us what you are running or what you need to ship. We respond from hello@taxeltech.com.