Payroll and EOR platforms
Funded in stablecoins by clients on chains you did not plan for, paying local currency on a fixed date. A wrong-chain arrival becomes a support incident across a whole company.
Universal payment account
Routing & normalisation
Routing & execution
Local currency settlement
Reconciliation & records
Platform & embedded accounts
Solutions
Give your own users a receiving account.
Issue every one of your users a persistent payment identity without building the detection, screening, matching, routing and settlement underneath it. One integration instead of an indexer, a hot wallet and a confirmation policy per network.
The trade
Six integrations you maintain, or one you do not.
Every network you add the usual way is an indexer, a confirmation policy of its own, reorg handling, a hot wallet, gas management and a new way to lose money at three in the morning. That is the same work each time, and it is not the work your customers pay you for.
6
networks you index, monitor and keep working
Reorgs, gas and confirmation policy stay your problem ours. Adding the seventh is a parameter, not a quarter.
Who this is for
Products where receiving international payments is a feature rather than the business — payroll and EOR platforms, marketplaces, fintechs, invoicing tools and B2B software serving businesses that get paid abroad.
Marketplaces
Sellers and freelancers paid at high frequency, where a fixed transport cost per payout decides whether the unit economics work at all.
Fintechs and neobanks
Adding chain coverage without adding an indexer, a compliance workstream and an on-call rotation for each one.
Invoicing and accounting tools
Products already serving businesses paid abroad, where “mark as paid” currently requires a human to check a block explorer.
African SaaS
Products whose customers are collecting foreign revenue and doing the chain-matching by hand in a spreadsheet today.
Remittance operators
Operators who want wider inbound chain coverage without negotiating custody and transport relationships themselves.
You keep the customer. We make the rail irrelevant.
Your users never see Nomapay. Your brand, your interface, your support relationship. Adding a network becomes a parameter change rather than a quarter of integration work, and the reorg handling is somebody else’s pager.
Pay a per-transaction fee, mark up our wholesale price to your users, or fold it into your own subscription. All three work.
Detected
$40,000 · USDC on Base · 10:42:13
Normalise to USDT on TronSelectedCCTP · issuer-native · 2m 09s
$18.40
Normalise to USDC on SolanaCCTP · issuer-native · 1m 46s
$21.10
Wrapped-token bridgeNot supported — we do not route through wrappers
—
Transport, at cost$18.40
Reference rate, 10:44:31₦1,610.00
Executed rate₦1,602.25
Nomapay fee, 0.35%₦224,231
Your user receives₦63,836,287
Illustrative example, not a quote. Shown here in one settlement currency; the same record is produced in whichever one the business banks in.
Why not build it yourself
You can. It is roughly: a custody relationship that can issue endpoints per customer per network, an indexer and confirmation policy for each network, reorg handling, hot wallet and gas management, wallet screening, payment-intent matching, route selection, an unknown-state machine that never blindly retries, a double-entry ledger, daily reconciliation across six systems, and someone who owns it when an execution goes quiet at 2am.
Then you maintain all of that while it is not the thing your customers pay you for.
Honest position: we are in private beta. The API is designed, not shipped, and the first payments are done by hand. If you would build against this, the most useful thing right now is telling us what is wrong with the shape.
What we ask of you
Being straight about it, since embedded infrastructure is a serious dependency.
Start with one corridor
Do not move your whole inbound volume onto an unproven integration. Take the flow that hurts most and prove it.
Expect a real contract
Service expectations, incident handling, data protection, exit terms. If we cannot sign that, we are not ready to carry your payments.
Tell us when we are wrong
Early platform partners shape what gets built. That is the trade for integrating with something this young.
Talk to us early.
Even two quarters out, the design is still being decided and your requirements can be in it.