Finance platform
A wallet ledger that
reconciles to the paisa
Atmora Wallet issues stored-value accounts, holds balances on an append-only double-entry ledger, and moves money over UPI, cards, net banking and bank transfer. Every balance change is a journal entry with an actor and a reason code, so the figure you see at 23:59 is the figure you can defend.
- Cloud
- Private cloud
- On-premise
Overview
Stored-value accounts, tiered KYC and a double-entry ledger that closes every night.
Atmora Wallet is stored-value account infrastructure: a double-entry ledger, a KYC and limits engine, and connectors to the rails that move money in and out. Accounts, journals and holds are the primitives. A wallet balance is a computed view over journal entries rather than a number sitting in a row that a failed job can quietly corrupt, which means a damaged balance can be rebuilt from history instead of reconstructed from memory. The ledger is append-only, partitioned by programme, and has been run at 3,000 transactions per second sustained with P95 balance reads at 118 ms.
It is licensable as a platform, not a finished consumer app. You get APIs, admin consoles, Android and iOS SDKs and reference apps, and you build the brand experience on top. It is the wrong choice if a single payment gateway account already covers what you need, or if you want a card programme with no ledger of your own; a wallet is worth its operational weight only when you hold customer balances, settle to several parties, or need value to move between users without touching a card network every time.
- 99.97%
- Top-ups auto-matched at first-pass reconciliation
- 38 minutes
- Daily close on a 4.1 million-account book at Cordage Bank
- 118 ms
- P95 balance read at 3,000 transactions per second
- -64%
- Drop in missing-balance support contacts after go-live
Modules
What ships in the box
- Ledger core - accounts, journals, holds, multi-currency
- KYC tiers and limit engine
- Load, transfer and payout rails
- Card issuing and network tokenisation
- Reconciliation and settlement desk
- Offers, cashback and loyalty balances
Integrates with
- NPCI UPI
- Razorpay
- Stripe
- Okta
- Twilio
- SAP S/4HANA
- Tally Prime
- Zoho Books
Capabilities
What it does
A double-entry ledger, not a balance column
Every credit has a matching debit against a named account, and balances are derived from journal entries. A ledger damaged by a bad job can be rebuilt from history rather than guessed at.
Tiered KYC with limit ladders
Minimum-KYC, full-KYC and merchant tiers each carry their own monthly load, per-transaction and closing-balance ceilings. Limits are checked before authorisation, not reported afterwards.
Idempotent money-movement API
Every debit and credit takes a client-supplied idempotency key held for 48 hours. A retried call after a network timeout returns the original result instead of moving money twice.
Mobile SDKs that tolerate dead zones
The Android and iOS SDKs queue signed intents when the device loses connectivity and replay them on reconnect, with server-side deduplication and a hard fifteen-minute expiry.
Dispute and chargeback workflow
Cases carry evidence, deadlines and provisional-credit rules. Ageing is visible per analyst, and entries for provisional credit and its reversal post automatically to the ledger.
Multi-tenant, multi-currency by construction
One deployment hosts separate programmes with their own branding, fee schedules and ledgers. Currencies keep native minor units, so JPY and BHD are not forced into two decimal places.
Reconciliation against rail statements
Nightly jobs match the ledger against acquirer, UPI and bank statement files, classify breaks by reason code, and park unmatched items in a suspense account until an analyst clears them.
Field-level access control and audit trail
Roles restrict visibility down to individual fields such as full mobile number or PAN. Every read and write lands in an append-only audit log with actor, reason code and source address.
Built for
Where this is deployed
Industry
Banking & Financial Services
Payment rails, risk engines and core-adjacent systems built by people who have run them at 03:00 on a settlement night.
Industry
Retail & E-commerce
Storefronts, stock ledgers and fulfilment logic that hold together on your busiest trading day.
Industry
Telecom & Media
OSS, BSS and delivery platforms that keep working after launch night.
Industry
Travel & Hospitality
Booking, offer and disruption systems for operators whose worst day is a fare sale during an outage.
Industry
Public Sector
Digital services that work for everyone who has to use them, including on a five-year-old phone.
FAQ
Questions we get asked
- Can we run the ledger on our own infrastructure?
Yes. The full stack deploys to your data centre or private cloud on PostgreSQL and Kafka, with the same container images we run in our hosted environment. Customers in regulated segments usually take the on-premise ledger and keep only notification and analytics services in cloud.
- Does Atmora Tech hold customer funds?
No. Funds sit with your bank or your payment service provider under your licence. Atmora Wallet records, controls and reconciles the movements; the regulatory relationship and the float remain yours, and the software is neutral about which sponsor bank you use.
- How do we migrate balances from an existing wallet?
Through a one-off opening-balance journal per account, posted against a migration control account so the total is provable, followed by a dual-run window where both systems record the same traffic and are compared daily until the break count reaches zero.