Load a device online, pay offline, settle in batches when it reconnects, with replay protection.
In a market, on a bus, at a crowded event, the network is what fails before anything else. Card machines stop, transfers hang, and the sale moves to cash or doesn't happen.
Offline payments let a customer move value onto their device while they're online, then pay another device phone to phone or at a POS with no network at all. Both devices sign the payment. When either reconnects, the batch settles and the payee is credited.
The money never lives on the phone. It sits in a device account on the ledger, which the device can spend against while disconnected. Bridge always knows the true balance, and a device can't create value.
Online, the customer moves value from their main account into a device account on the ledger.
Phone to phone or at a POS, over QR, NFC or Bluetooth. Both devices sign the payment.
Both devices keep the signed payment until one of them is back online.
The batch settles; replays are rejected and caps are enforced from settled history.
The payee's account is credited, and you get a signed webhook.
The device holds a claim and a signing key, not money. It can't mint value.
Every payment carries both signatures, verified at settlement.
A payment presented twice settles once.
How much a device can hold and spend offline is derived from what it has settled before.
From any other device. Caps keep the value on any one device small.
Customer phones pay each other or pay a merchant's terminal.
Illustrative businesses, not customers. Figures are made up to show the flow.
A wallet app for traders at Balogun Market · Merchants & e-commerce
On busy days the network jams by mid-morning. Traders lose sales to customers without cash.
Sales don't wait for the network.
A transport company running Lagos–Ibadan routes · Transit
Conductors collect cash fares between towns where there's no signal, and cash goes missing.
Fares are collected without cash, even with no signal on the road.
A microfinance bank's agent network in rural Niger State · Banks, MFBs & PSBs
Agents' POS terminals fail when coverage drops, and customers walk away.
Agents keep serving customers when the network doesn't.
Endpoints in the Offline payments API reference, with every parameter and response.
State changes arrive as signed webhooks. How webhooks work
POST /offline/deposit
Bridgecurl -X POST "https://api.bridgemoni.com/offline/deposit" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" \
-H "X-Idempotency-Key: a-unique-key-per-intent" \
-H "Content-Type: application/json" \
-d '{
"amount": {
"amount": "250000.00",
"currencyCode": "NGN"
},
"narration": "March payroll",
"deviceId": "a7f3-k2m9-4c1d-8e5b"
}'In a device account on the ledger. The phone holds a claim on it and a signing key, not the money.
Both payments look valid offline, but whichever settles first succeeds and the other is rejected. Caps limit the exposure.
The offline endpoints are live. Mobile and POS SDKs are on the way: see SDKs.
Freeze it from another device. Value already on it that hasn't settled can be lost, which is why caps keep it small.
We'll come back with what's live for you today, and what's next.