Onboarding and verification
Legal entity, directors and beneficial owners, business category, expected volume and ticket size, source of funds, and the settlement bank account. No production funds move before the business is verified.
How it works
From payment intent to money in the bank.
Your customer pays a Nomapay account rather than a wallet address. Everything below happens between that payment and the money landing in your Nigerian corporate account, and none of it is yours to operate.
Before the money moves
Onboarding, then an account, then an intent.
The account is a persistent payment identity attached to a verified business. It is created once. The intent is created per invoice, and it is what lets an arrival reconcile itself.
01
02
The Nomapay account
A permanent number — NP-847291 — mapped to payment endpoints on each supported asset and network. Endpoints can rotate underneath for security or operational reasons without your identity changing.
03
The payment intent
Invoice reference, expected payer, expected amount, accepted assets, expected settlement currency and an expiry. This is the difference between knowing money arrived and knowing what it was for.
After they pay
Detect, screen, match, route, convert, settle, reconcile.
04
Detect
We index the supported networks and watch for arrivals against your endpoints. Each network has its own confirmation policy, and reorgs are handled explicitly — a payment is not final because it appeared once.
05
Identify
Account, intent, asset, network, sender, amount, transaction hash, block, confirmations, timestamp. Parsed and recorded, not inferred later.
06
Screen
Sanctions, known illicit addresses, mixers, ransomware and stolen-funds exposure, darknet exposure, fraud indicators. Clear, review or blocked — and the result is retained as part of the transaction record.
07
Match
Destination, amount, asset, expected payer, timing and any invoice reference. A payment that lands $50 short inside your tolerance is flagged as matched with variance, and you decide.
08
Route
Which path through approved infrastructure gives the best net outcome — not the cheapest hop. Where a route is needed at all, we prefer native or canonical movement over wrapped representations.
09
Convert and settle
Conversion through an approved partner, then your own currency to your verified corporate account. Reference rate, executable rate, provider fee, network cost, our fee and slippage all recorded.
Then reconciliation. Every day, across the blockchain, our ledger, the liquidity partner, the conversion provider, the settlement provider and the bank. Every difference raises an exception, and no unexplained difference is allowed to sit indefinitely.
Payment states
A payment is never a boolean.
It moves through named states, and the product must never hide uncertainty by rounding one of them up to “completed”.
CREATED → AWAITING_PAYMENT → DETECTED → CONFIRMING → SCREENING
→ MATCHED → ROUTING → NORMALIZING → CONVERTING → SETTLING → SETTLED
// branches
SCREENING → REVIEW | BLOCKED
ROUTING → ROUTE_UNAVAILABLE
CONVERTING → FAILED
SETTLING → FAILED
ANY AMBIGUOUS STATE → UNKNOWN
UNKNOWN is a first-class state. If a provider times out after we send an execution instruction, we do not know whether it executed. Blindly retrying a $500,000 conversion sends it twice. So we query the provider, reconcile, determine whether execution actually happened, and retry only once the original is definitively confirmed not to have happened. Every external operation carries an idempotency key, so a retried request returns the original result rather than creating a second payment.
Routing
Optimised for net customer outcome, not cheapest bridge.
A route is scored on what actually lands, discounted for what could go wrong. Cheap and unreliable loses to slightly dearer and certain, every time.
What the score weighs
Net amount received in your currency, execution certainty, settlement speed, compliance confidence, provider reliability and operational risk. A route is only eligible if the provider supports the asset and network, screening is clear, liquidity covers the amount and expected settlement is inside threshold.
Deterministic first
V1 is rules plus real transaction data, ranked on net settlement, reliability and speed. No machine learning decides where your money goes until there are enough real transactions to have learned anything. Predictive routing is a later version, not a launch feature.
Never built
A proprietary bridge
Cross-chain transport is infrastructure that already exists. We consume it and own the identity, detection, screening, routing, settlement and experience instead.
Gas is a decision, not a surprise
Some routes need network gas. Whether it is available, who pays it and whether it comes out of proceeds is resolved before execution — and the customer sees the final economic impact either way.
The boundary
Nomapay orchestrates. Regulated infrastructure holds and moves.
The account identifies where incoming value belongs. It does not imply that Nomapay is storing your money, and we avoid unnecessary balance-sheet exposure by design.
OursNomapay
Identity, detection, screening, matching, routing, ledger, receipt
Every decision about where value should go, and the permanent double-entry account of what happened.
TheirsPartners
Custody, conversion, payout
Performed by licensed or authorised partners under their own permissions.
NeverNever
Pooled wallets, indefinite balances, lending, yield
No customer funds held indefinitely, no omnibus balances we do not control, no lending of customer balances, no proprietary custody without a legal basis.
Would you send a customer here?
Tell us how your foreign customers pay you today, and whether you would replace those instructions with one account number.