Skip to content

About us

The software financial services run on

We build payment rails, identity verification and the ledger behind them, then hand the brand, the pricing and the network to you.

The situation

The shop on the corner is running a bank branch

Not officially. Not with a licence on the wall. But functionally — cash goes in, a balance moves, someone walks out with the money they needed.

Counter ledger

₹0CASH ACCEPTED
  1. 01
  2. 02
  3. 03

  1. Cash in

    A customer hands over notes at the counter.

    CASH ACCEPTED

  2. A balance moves

    Somewhere behind the counter, a ledger changes.

    LEDGER POSTED

  3. Money out

    They leave with what they came for.

    SETTLED

What they care about

  • Did the transaction go through?
  • If it did not, is my money safe?

What they never think about

  • Payment rails
  • KYC pipelines
  • Webhook signatures

What we sell

One catalogue, two ways in

The difference is ownership, not capability. Nothing behind the curtain changes with the tier.

A branded platform

Take the whole thing and put your own name on it. Your members never learn ours.

  • Your domain and pricing
  • Your member hierarchy
  • Banking, bills, loans, insurance, travel, tax, GST, courier, legal

Raw APIs

Skip the storefront and build straight against the rails.

  • One credential set
  • One settlement report
  • Payments, payouts, AePS, KYC, travel, messaging

The same rails, the same wallet, the same reconciliation

100+ offerings across the platform and the API catalogue, one contract either way.

The hard part

What happens when the rail does not answer

Not a decline — a decline is an answer. The dangerous case is silence: a request goes out, a timeout comes back, and nobody knows whether the money moved.

  • Success

    Answered

    The rail confirms it.

    Settle it. Credit or debit as the leg requires.

  • Declined

    Answered

    The rail refuses it.

    Reverse it. A parsed refusal is the only thing that may move money back.

  • Silence

    Unknown

    No usable answer at all.

    Hold it. Money stays accounted for until a real answer arrives or a person decides.

A timeout is the single moment a payment is most likely to have already succeeded. Treating that as a failure — refunding a member whose money already left, or worse, letting them retry and pay twice — is how platforms quietly destroy the balances they were trusted with.

What we refuse to do

  • Auto-resolving a stuck payment after three days because three days is a round number
  • Quietly marking things “failed” so a dashboard looks clean

What happens instead

  • An unresolved transaction stays unresolved, and stays visible
  • A person makes the call, in a queue built for exactly that

How we work

What we hold ourselves to

Four positions that decide how our systems behave when something goes wrong, which is when it matters.

  • The money is someone else’s

    Every balance on the platform belongs to a member who earned it. That is the standard we hold ourselves to when deciding how a system should behave under failure.

  • Unknown is a real answer

    A system that reports a guess as a fact is worse than one that reports uncertainty. We keep unresolved things unresolved, visibly, until they are settled properly.

  • Your brand, not ours

    A white label that leaks its supplier is not a white label. Where we are invisible to your members, we stay invisible, and that is enforced in the software rather than left to discipline.

  • Say what is actually true

    We would rather confirm a number in writing than publish one that sounds better. That applies to settlement timings, commissions and everything else a decision gets made on.