Client onboarding
Each new Maqsafy client gets a unique on-ledger identity, issued as an NFT on ROX. Their wallet can then hold and move value.
Identity NFTWallet linking
Integration service, always on
Every Maqsafy wallet movement,
Every Maqsafy wallet movement,
settled on ROX. Exactly once.
The bridge picks up every client, top-up, transfer and payment in Maqsafy, carries it out on the ROX ledger in the right order and reports the result back. It never loses work and never sends anything twice.
Maqsafy
Wallets & payments
The Bridge
Order, verify, retry
ROX
Ledger of record
Persist firstSaved before anything is sent
Exactly onceIdempotent by design
Verified retriesChecks ROX before acting again
Fully auditedEvery manual action is logged
What it does
Three pipelines, one source of truth.
Maqsafy is where students, parents and merchants use their wallets. ROX is the ledger behind them. The bridge keeps the two in lockstep.
Money movement
Top-ups, transfers between wallets and purchases become matching ledger operations, carried out in strict order for each purchase or transfer.
MintTransferBurn
Confirmation loop
When ROX settles an operation, the bridge records the outcome and tells Maqsafy. Users see an accurate balance, and nothing is left half-done.
Settlement eventsStatus sync
How it works
From a tap in Maqsafy to a settled ledger entry.
Every item follows the same four-stage lifecycle, and each stage is safe to repeat.
1
Collect
New clients and wallet activity are pulled from Maqsafy continuously, in small batches with automatic backoff.
2
Persist
Each item is checked for duplicates and saved before anything is sent, so even a crash mid-flight loses nothing.
3
Execute
Operations run on ROX grouped by purchase or transfer, each with a deterministic key so a repeat can never double-spend.
4
Confirm
Settlement events from ROX close the loop, and Maqsafy is notified with retries until it acknowledges.
Reliability
Built for money, where "probably" isn't good enough.
Networks drop and services time out. The bridge expects that, and recovers without anyone stepping in.
Idempotent operations
The same transaction always carries the same key. Retries are safe because ROX recognises work it has already done.
Verify before retry
Before redoing anything, the bridge asks ROX what actually happened. Steps that already settled are kept, and only what's missing is re-sent.
Automatic recovery
Failed work is retried on a schedule with backoff, and a background reconciler clears blockages on its own.
Ordered execution
All the legs of a purchase or transfer finish before the next one starts, so balances never race each other.
Stuck-work detection
Anything that stalls is spotted, re-checked and escalated. A growing failure backlog triggers an alert before users notice.
Signed & scoped
Incoming events are signature-verified, and internal access is limited by role, so each person can only do their own job.
For the team that runs it
A calm console for the rare bad day.
When something does need a person, the operations team sees exactly what's wrong and how to fix it safely.
- Live health at a glance: throughput, backlogs and failures by pipeline.
- Step-by-step traces: every operation and its state, from first attempt to settlement.
- Guided recovery: each action shows how many items it will touch before it runs.
- Guard-railed overrides: they require a written reason and a typed confirmation.
- A complete audit trail: who did what, when, and why.
Boring infrastructure,
in the best possible way.
Every balance matches and every movement is accounted for, quietly and around the clock.