The parts we build, run and hand over.
Each block below is a system we design, implement and operate. They compose into a working product, or drop into one you already have.
Bank & rail integrations
PSD2 account information and payment initiation, plus direct rail and processor integrations. Consent capture, token refresh, sandbox-to-production certification and one normalised model across every institution.
Initiation & routing
Payment orders with idempotency keys, routing rules per corridor and currency, status webhooks, retries and returns. Every terminal state is explainable.
Accounts & ledger
Double-entry postings, balances, holds and limits, multi-currency, end-of-day close. Statements and reconciliation files that finance can actually tie out.
Origination & servicing
Applications, offers, disbursement, repayment schedules and collections events — wired to the same ledger rather than a spreadsheet beside it.
Scoring inputs
Transaction categorisation, affordability signals and external data pulled into one feature set your credit policy or model can consume.
Back office & reporting
Case handling, manual interventions with a full audit trail, regulatory and management reporting, and dashboards that read from the ledger.
Three ways to take it
The technology is the same. What differs is who owns it afterwards.
Build with us
We design and implement against your requirements, run it while you scale, and hand over source and runbooks.
Best when the product is your own and the requirements are specific.
Licence the stack
Take the platform under licence, deployed in your infrastructure, with our team supporting releases and upgrades.
Best when time to market matters more than owning the code.
White-label
Your brand, our operation. You define the product and the customers; we run the systems behind it.
Best when you have distribution and do not want an engineering org.
What every delivery includes
These are not upsells. A system that moves money without them is not finished.
- Audit trailEvery state change attributable to an actor, a reason and a timestamp.
- ReconciliationDaily tie-out between internal ledger and external statements, with breaks surfaced, not hidden.
- IdempotencyRetries and duplicate callbacks can never move money twice.
- ObservabilityMetrics, structured logs and alerting on the flows that matter, from day one.
- Data protectionGDPR-aligned handling of personal and transaction data, with retention defined per data class.
Want the detail behind a specific block?
We will walk through the design, the failure modes and what it takes to run it.