Operation plane · M14 · Payments

Local charging, certified in the ledger.

Multi-method charging, corporate accounts, and driver settlement — with every payment certified in the ledger. The registry certifies that the payment happened without ever seeing the sensitive data behind it.

See the Ledger Request a demo

Anti-fraud

The driver can't alter the amount.

Every payment lands in the ledger. The amount is set by the node, not the driver — and the registry certifies that the payment happened without ever seeing the data behind it.

The amount is locked. Fares are computed by the node and presented to the rider — the driver app can charge the trip, never rewrite the number.
Every payment lands in the ledger. Each charge becomes an auditable entry — method class, amount, and a hashed reference — so there's a single record of truth for the trip.
Certified without exposure. The registry certifies that the payment happened. Cross-node certification through the signed ledger is a network-plane capability — roadmap, not yet live.
Cash is reconciled, not ignored. Cash trips are recorded and reconciled against the driver's balance — so the books balance whether or not a card was tapped.
Certified in the ledgerlive feed
14:02:110x9f…a12cCard charge · tokenized · TRP-8841$18.40
14:02:090x71…ee03Platform fee · TRP-8841$2.20
14:02:000x4d…b8f1Driver payout · A. Morales$16.20
14:01:480x2a…7c90Cash charge · reconciled · TRP-8839$11.10
14:01:310x6e…d4a5Corporate voucher · Norte Logística$24.00

// Sample entries. Local certification runs on your node today; the signed, network-wide ledger that lets other nodes verify a payment is roadmap.

Privacy by design

Card data never reaches your ledger.

Card data is tokenized at the gateway. The ledger only stores a hashed reference, the amount, and the method class — so a payment can be certified without anyone downstream holding the card.

Tokenized at the gateway

Card numbers are exchanged for a gateway token before they reach your systems. The platform charges the token; the raw card is never stored on the node.

Hashed reference only

The ledger holds a hashed reference, the amount, and the method class — cash, card, or wallet. Enough to certify and reconcile a payment, nothing more.

Certified, not exposed

The registry certifies that the payment happened without seeing sensitive data — the proof travels, the card details don't.

In the driver app

Commissions, balance, debt, and receipts.

Drivers settle from their own app — commissions, running balance, any debt carried forward, invoices, and receipts, all in one place. Whatever the method, the amount they see is the amount certified in the ledger.

Commissions & balance. Commission is computed per trip and netted into a running balance the driver can see at any moment — no end-of-week surprises.
Debt carried forward. If a cycle ends negative — a refund, a cash shortfall — the debt is carried transparently into the next, never silently written off.
Invoices & receipts. Every settled trip produces a receipt; corporate trips produce an e-invoice — generated in the app, not chased after the fact.
One source of truth. The number the driver sees is the number certified in the ledger — cash, card, or wallet, the books agree.

// All figures, IDs, and references are illustrative sample data. Local charging, settlement, and receipts run on the node today; cross-node certification through the signed ledger is roadmap.

Operation plane · M14

See where every payment is certified.

Charging happens on your node; the ledger is what makes a payment provable across the network. See how the ledger is designed to certify a payment without ever seeing the data behind it.

See the Ledger Request a demo