The counter, the money and the operation.
Four layers, one system: what the teller runs, what the ledger holds, what the back office proves and how providers connect.
How it fits together.
Channels are thin fronts on one API surface; the value sits in the middle, in the catalog, the orchestration, the ledger and the gateway. Providers plug in underneath, whatever their technology.
Every service is a journey the catalog draws.
Every screen, step, rule and price comes from the catalog. Launching a new service means configuring it, not writing software.
Guided journeys with quote, payment and receipt built in Partner selection with provider marks Field validation and limits enforced from the contract
Cash that always balances.
Every counter starts the day declaring its cash and closes against the system's own count. Every pula is recorded twice, so the books always balance, and the platform checks them all day long.
Float and cash live per counter, with liquidity health Commission accrues per transaction against catalog schemes Dual-control rebalances, reversals and approvals
Author, publish, reconcile: one platform.
Admins build and publish services with a live preview; the back office clears the daily reconciliation and anything that failed; supervisors approve the sensitive moves. Every role has its own surface.
Catalog studio with dual-control publishing Daily three-way reconciliation, every exception on a deadline Provider registry, certification and health board
Author the journey live preview Sandbox test stub provider Publish with dual control distinct approver - Live at the counter minutes later
Any provider, whatever their technology.
Institutions expose themselves differently, so the gateway meets each on its own terms. A sandbox and a certification path take a partner from signed to live.
API connectors for systems with real-time interfaces File and batch for settlement files and beneficiary lists Assisted connectors that drive legacy screens where no API exists
Commercial BankAPI connectorCertified Water UtilityFile and batchNightly file Licensing AuthorityAssistedIn certification
What is in the box.
The whole inventory in one place, for the evaluator with a checklist. The story above explains how it fits; this is what you get.
The counter and journeys
Guided journeys with quote, payment and receipt built in Provider choice at the counter, with partner marks Rules and limits enforced from each contract Search and category browsing across every service Honest outcomes: pending and unsettled states, never a false success
Money and settlement
Counters open with a declared float and close with variance shown Every movement recorded twice, to the thebe Commission earned per transaction, at the rate set per service Float rebalances requested and approved by two people Settlement through the bank you appoint
Reconciliation and operations
Daily three-way match: counters, providers, bank Every exception on a deadline, worked in the back office A failed-transaction queue with retry and resolution Books checked continuously, not at month-end A full audit trail on every change
Administration and catalog
A catalog studio with live preview Publishing with a distinct second approver Provider registry, certification and health board Outlet and counter management Your brand, colours and terms, changed without a rebuild
Provider connectivity
API connectors for real-time systems File and batch for settlement files and beneficiary lists Assisted connectors where no API exists A sandbox and a certification path to go live Provider health visible before you sell
Security and access
Single sign-on for every staff role Five roles, nothing allowed unless a role permits it Two people on every risky move Each operator isolated at the database itself A retry can never move money twice
See the four layers on your services.
A demo walks your own story: your services, your partners, your floats.
Agency One