Provenance
Payer, network, transaction hash, sending wallet and the screening outcome recorded at the time, not reconstructed afterwards from memory.
Universal payment account
Routing & normalisation
Routing & execution
Local currency settlement
Reconciliation & records
Platform & embedded accounts
Solutions
Reconciliation & records
The part nobody demos. A payment intent says what money is for before it arrives, so an arrival reconciles itself — and at year end somebody can still explain where it came from and what it was worth when it landed.
The problem
Money arrived is not the same as knowing what it was for.
Without an intent, all a system can tell you is that money arrived. With one — invoice, expected payer, expected amount, expiry — the arrival matches itself, duplicates are caught, and a short payment becomes a decision rather than a mystery.
01
02
Valuation
The reference rate with its published source and timestamp, alongside the rate the partner actually executed at. Two numbers, so the gap is visible rather than inferred.
03
Cost of receipt
Network cost, normalisation cost, liquidity and execution cost, and our fee, each on its own line. One total at the bottom, in your own currency and as a percentage.
For the bank
The question you will eventually be asked.
Nigerian banks do freeze inflows, particularly where a counterparty is later linked to fraud. We cannot promise it will never happen to you, and anybody who does is overselling. What we can do is make sure you hold the documentation yourself rather than an assurance from a desk.
Where did this money come from?
The sending wallet, the chain, the transaction hash and the time. Screened before anything moved, with the result recorded permanently — including the times it came back clean.
What was it worth when it arrived?
A named public reference rate at a stated timestamp, and the executable rate the partner transacted at. If a reference cannot be verified against a published source at that moment, the record says so rather than filling the gap with an estimate.
Who held it, and when?
Custody sat with a licensed partner throughout. Nomapay never controlled the asset. Transport between chains was issuer-native, so at no point was the value a claim on a third-party contract.
How long did it take?
Measured from detection to bank credit, not quoted from a marketing page. Recorded per payment, so a pattern of slow settlement is visible to you as soon as it is visible to us.
On the roadmap
What finance teams will want, and when.
None of this has shipped yet. It is listed here so you can tell whether we are worth waiting for, and so we cannot quietly drop it later.
FirstShipping first
The per-payment record
One page per payment with every figure above. Part of the first build, because without it there is no product worth selling.
AfterPlanned
Monthly reconciliation export
A pack your accountant can import without rebuilding it by hand. Built once ten payments have been done and we know what the pack actually needs to contain.
AfterPlanned
Compliance pack
Provenance and chain of custody per inflow, written for the person at your bank who asks rather than for us.
LaterPlanned
Batch payouts
Paying twelve contractors from one funded balance instead of twelve transfers. The account is built for both directions; this is the half that comes second.
Show us the report you have to produce.
If we cannot fill it in from what we record, our record is wrong. Tell us what your accountant or your bank asks you for.