Software / Core Wallet Technology
Accounts, balances and a ledger that holds up.
Account and wallet management, balances, ledger functionality and payment integrations for institutions and platforms that need a dependable core.
At a glance
- Built for
- Banks, EMIs, platforms
- Currencies
- Multi-currency
- Ledger
- Double-entry, auditable
- Access
- APIs and back office
Capabilities
Accounts and wallets
Customer, corporate and internal accounts with configurable product types, statuses and permissions.
Balances and holds
Available, ledger and held balances maintained separately, so authorisations and pending items never distort the true position.
Double-entry ledger
Every movement posted as a balanced journal entry, with an immutable record for audit, reconciliation and reporting.
Multi-currency
Currency-specific accounts, FX conversion records and the reporting needed to reconcile positions by currency.
Payment integrations
Inbound and outbound payment flows connected to the relevant rails and providers, with status tracking per instruction.
Fees and adjustments
Fee schedules, reversals and manual adjustments posted through controlled workflows rather than direct balance edits.
Wallet balance
£1,284.20
GBP
£1,284.20
EUR
€4,120.00
USD
$0.00
Ledger activity
| Date | Reference | Debit | Credit | Balance |
|---|---|---|---|---|
| 12 Nov | Card purchase · Merchant 5732 | £42.80 | £1,284.20 | |
| 12 Nov | Inbound transfer · GBP | £2,000.00 | £1,327.00 | |
| 11 Nov | FX conversion · EUR → GBP | £184.62 | −£673.00 | |
| 11 Nov | Wallet top-up · Faster Payments | £750.00 | −£857.62 |
Double-entry posted
Every movement balanced to the ledger
Conceptual interface
Ledger-first architecture
Balances are a view. The ledger is the truth.
Every entry balances
Debit and credit are recorded together. A transaction cannot leave the ledger in an inconsistent state.
Nothing is overwritten
Corrections are posted as new entries, preserving the original record for audit and dispute resolution.
Built for reconciliation
Entries carry the reference data finance needs to match the ledger against providers, schemes and bank statements.
Deployment models
Your platform, your data, your controls.
Wallet and ledger technology is often close to the institution's core. Deployment and data residency are agreed before implementation, whether the platform runs in your environment or ours.
SaaS
Managed deployment with defined release and support terms.
Perpetual licence
Installed within your infrastructure under your change control.
API-first
Product and back-office operations exposed for your own channels.
Multi-institution
Separate ledgers and controls for each institution or programme.
Operating the core
A ledger-first model, from product design to daily reconciliation.
- 1
Model the product
Account types, currencies, fee schedules and controls defined.
- 2
Open accounts
Customer accounts and wallets created through API or onboarding flows.
- 3
Post activity
Payments, card activity and fees posted as balanced ledger entries.
- 4
Reconcile
Positions reconciled against providers, with exceptions routed for resolution.
Next step
Talk to the product team.
Bring the requirement, the constraints and the institutions involved. We will tell you what the implementation looks like.