Receive and send across bank and stablecoin networks. We manage the rails underneath.
A defined set of supported assets and networks, never “any chain”. In private beta — here is where we are.
Rails in and out
Stablecoin rails are what the private beta covers. Bank rails are what the account was built to hold alongside them, and they open as each licensed partner is signed. Your customer only ever sees what is genuinely available at that moment.
Settlement currencies
Nigeria is the first corridor and the one we are proving. Everything after it needs a licensed settlement partner in that country, so the list grows one signed agreement at a time — never by announcement.
Your customer pays the account. Between that and money in your bank, this is the whole job — and today it is somebody’s job in your office.
We watch the supported networks for arrivals against your account, each with its own confirmation policy and explicit reorg handling.
The sending wallet is checked before settlement. An adverse result stops the payment and escalates to a person.
The arrival is reconciled against the invoice you were expecting — including when it lands short, which becomes your decision rather than a mystery.
Routed where a route is needed, converted through a licensed partner, and paid into your verified corporate account.
On every rail, the account details are the identity — a wallet address here, a sort code there — so each new network means new payment details and a new chance to send $40,000 somewhere irreversible. We invert that. The Nomapay account is permanent, for money arriving and money leaving; what sits underneath it is ours to manage.
Please pay invoice INV‑1034 to Nomapay account NP‑847291
One line. Every customer, every invoice, every supported rail — and it does not change when the endpoints underneath it do.Inbound
$40,000 into NP-847291
Payment detected
Illustrative. Assets, networks, costs and timings are examples of how the account resolves a payment, not records of real transactions. The supported set is shown dynamically at the point of payment.
Not a menu of everything we can accept. The page asks what they hold, then gives a single address on a single network with the exact amount and an expiry. What else we could have taken, who issued the address and what happens after it lands are all concealed.
Your client does not sign up for anything, install anything or connect a wallet. They open a link.
A blockchain has never heard of NP‑847291. The reference exists so you have one thing to communicate and one thing to reconcile against.
Detected, screened, matched to your invoice, paid. It does not go quiet after the send.
A remittance advice their own books can use, not a block explorer link. Paying you should be easy for them, or you are the one who loses the invoice.
Illustrative. The addresses are shaped like real ones but encode nothing, and the code is a placeholder.
Deciding how money moves is the part you are trusting us with. What matters is not how clever it is, but what we promise never to do while we are deciding — and whether you can check afterwards that we kept to it.
Executed on arrival. Waiting means holding a position, and holding is the line this company is built to stay behind.
If no acceptable route exists, nothing is attempted and a person is told. A router that guesses under pressure is how money goes missing.
Where value must move, it moves natively. We do not put your funds behind a claim on somebody’s contract to save a few dollars.
Transport is passed through at cost. Otherwise the cheapest route for you and the best one for us stop being the same route.
The receipt is not a confirmation line. It is the financial explanation, and it is a core feature rather than a footnote.
Total cost of receiving ₦535,400 · 0.83%. Illustrative example, not a quote. If a reference rate cannot be verified against a published source at that timestamp, the record says so rather than estimating.
How much real payment volume arrives through an asset or network the receiver cannot use? We have not measured it yet, so the thresholds are written down before we do — and frequency alone would mislead us. A 20% mismatch on $2,000 payments is irrelevant; a 5% rate on $500,000 payments is an excellent business.
How your customers pay, on what networks, how often and at what size. In parallel: Nigerian counsel on what this activity legally is, and partners who can hold and convert under their own permissions. Fewer than five of thirty with a real mismatch and the routing product does not get built.
Real accounts, twenty-plus real payments, monitored and settled manually with a spreadsheet for a ledger. The customer sees the finished product; the backend is a person.
Detection, screening, matching, routing, ledger, receipt and reconciliation. Operators stay for exceptions. More assets, more networks and other rails come after, driven by demand rather than by what is interesting.
Not crypto traders, not consumers, not anyone whose flows we cannot explain. A registered business with a corporate bank account and international revenue.
Software agencies, dev shops, BPOs, remote staffing firms, consultancies, creative studios and export businesses invoicing customers in another country, in whatever that customer holds.
Roughly $1,000 to $100,000 and above per payment. The exact floor is something we intend to determine experimentally rather than assert.
You would rather not force a customer onto one network to get paid. If your finance team is happy issuing three sets of payment details, you do not need us.
Retail consumers, crypto and P2P traders, anonymous users, gambling and high-risk merchants, sanctioned jurisdictions, or businesses with flows they cannot explain.
Drag or scroll sideways
The same payment account underneath, reached from wherever you sit. Find yours below — each one says what you get before it asks you for anything.
Illustrative pairs. Your customer sends what they hold — a stablecoin, a coin, or their own currency — and you are paid in the one you bank in. Corridors open one at a time, and which are live is stated, not implied.
You raise an invoice and send one line. Whatever your customer holds, it arrives attributed to that invoice and settles in your own currency.
The month-end reconstruction happens once instead of per client — and it is free, permanently, because your clients are the ones paying.
A payroll platform, marketplace or accounting tool gets acceptance and settlement without indexing a single chain.
A separate layer, for a separate question. Before money moves across a border, somebody has to know the shipment behind it exists — and almost nobody can check. Proof registers trade documents, verifies them against sources with no stake in the deal, and issues signed facts anyone can confirm without asking us.
Documents are fingerprinted, never stored. The registry answers one question: has this been seen before, by anyone?
Against the carrier’s own system, an inspector nobody chose, and registries with nothing to gain. Never against a document a party emailed us.
Each verified condition becomes a signed credential that stays valid, and checkable, without us.
Anchored on a public chain, so first-registration time is something nobody can forge — including us.
Proof states facts. It never gives instructions. It holds no funds and no keys, decides no disputes, keeps no upgrade key over any contract it publishes, and is never priced as a share of the value moved. A credential says what is true; somebody else decides what to do about it.
That question matters more than “would you use this”. Tell us how your foreign customers pay you today, and whether you would send them one payment destination instead.
