Companies with distributed teams hit the same problem every month. The amounts are modest, the recipients are in a dozen countries, and the bank fee plus the exchange spread takes a visible bite out of what each person is owed.
Stablecoin rails change that arithmetic. Here is which parts they change, which parts they do not, and what to confirm before you move a payroll onto them.
A transfer costs what the network costs. Paying someone twelve time zones away is not more expensive than paying someone nearby.
The stablecoin transfer settles instantly within the platform once funds are available. Fiat arrival still depends on the recipient's bank.
Someone who wants ordinary money gets ordinary money, through Make a Payment to their bank account.
Rails are not a payroll product. Contracts, tax and social contributions are exactly as they were.
The workbook that sent us here flagged payroll as a capability to confirm, and the product documentation does not describe one. So here is the position as it stands rather than a pitch.
What the platform does give you is the cost structure, verified destinations and a single reconcilable record. Whether that adds up to a payroll solution depends entirely on your headcount and your approval requirements.
| Cost | Traditional route | On stablecoin rails |
|---|---|---|
| Transfer fee | Per payment, often flat, painful on small amounts | A network fee, unrelated to the amount or the distance |
| Exchange spread | Usually the largest cost, rarely itemised | Applies at the fiat legs, not to the transfer itself |
| Intermediary deductions | Correspondent banks may take their own cut | None in the middle |
| Time to arrive | Days, and longer across a weekend | Instant on the stablecoin leg, bank pace on the fiat leg |
| Your team's time | Chasing, matching, re-sending failed payments | One history covering every payment |
For a contractor owed a few hundred euro a month, the fee and the spread together can be a meaningful percentage of the payment. That is the case where the rail genuinely matters, and it is also the case where a per-payment setup burden hurts most.
A payment to a team member runs the same route as any other payment.
| Send | Make a Payment | |
|---|---|---|
| They receive | A supported stablecoin in their wallet | Fiat in their bank account |
| They need | A wallet address on a supported network | A bank account and an IBAN |
| Suits | People already comfortable holding stablecoins | Everyone else, which is most people |
| Speed to them | Settles instantly within the platform once funds are available | Depends on their bank and country |
Most teams end up mixed, and the useful part is that both routes run from the same balance. You are not funding two systems to pay one group of people.
Most of the operational risk in cross-border payments comes from paying the wrong party, or taking money from a source you cannot account for. NGPES makes both a deliberate step.
Worth stating clearly, because the word payroll carries a lot of expectations.
This is a payment rail, and it sits underneath whatever payroll or contractor management system you already run. Anyone selling it as a replacement for that system is selling you something else.
Here is what each leg takes.
| Leg | Timing |
|---|---|
| Stablecoin transfer | Settles instantly within the platform, once funds have been received and are available. |
| Stablecoin to fiat conversion | Instant. |
| Fiat arriving at the recipient | Depends on the destination currency, the geography and the external banking rails involved. NGPES does not control this leg. |
| Fiat top-up | Depends on the inbound transfer reaching your linked IBAN. |
The digital asset layer is instant once liquidity is available, and the fiat legs at either end move at the speed of the banks involved. That is a large improvement on a correspondent banking chain, and it is not the same as end-to-end instant.
This is what the platform supports today.
| Position today | |
|---|---|
| Stablecoins | Selected MiCA-compliant stablecoins only. Assets outside that set are not held on the platform. |
| Non-compliant assets | Funds arriving in an asset that is not MiCA-compliant can be converted into a MiCA-compliant one, as a case-by-case exception, not a standing service. |
| Fiat | Moves in and out through the linked IBAN via on-ramp and off-ramp. Fiat balances are not held on the platform. |
| Swap | Between supported MiCA-compliant stablecoins only. |
| External accounts | You can register your own external bank accounts and wallet addresses. They are verified before use, and only for flows involving the same organisation. |
| Team management | Announced as coming soon. Not available yet. |
If a particular asset, currency or corridor matters to your business, ask us before you build around it.
Where NGPES is authorised today.
NGPES is based in France and the platform supports selected MiCA-compliant stablecoins only, by design. Services will become available only upon obtaining the relevant CASP and EMI authorisations.
What NGPES states today.
| What NGPES states | |
|---|---|
| Reach | Funds move across 150+ countries via SEPA, SWIFT and local rails. |
| Stablecoin settlement | T+0. |
| Fiat settlement | T+1. |
| Processing | 24/7/365, with no end-of-day batch. Everything is processed in real time. |
| Conversion | Instant conversion between fiat, in USD, EUR and GBP, and stablecoins. |
| Exchange | 24/7 fiat to stablecoin exchange, with OTC support. |
For a per-country arrival time, a fee, or the supported asset and network list, talk to the team.
Payroll is not a stated use case in the current platform documentation, and there is no bulk or batch upload. Payments go individually to registered counterparties. Confirm the mechanics with the team before you move a payroll onto it.
The transfer cost is driven by the network, not the distance or the amount, so small cross-border payments stay viable. The saving is largest on modest amounts to many countries.
No. Make a Payment converts your balance to fiat and pays their bank account over traditional rails, so nothing changes for them.
Once. Each recipient exists as a counterparty record with the routing details attached, and that record persists.
Not stated in the current documentation. It is worth confirming, because it decides whether small monthly amounts are viable.
No. It is a payment rail, not a payroll system. Gross to net, filings and payslips stay with whatever system you use today.
Every payment sits in Activity alongside the top-ups that funded it, and the full history exports to CSV or Excel.
Those two numbers decide whether this works for you today or whether it does not.
NGPES, Next Generation Payment EcoSystem, is a B2B payment infrastructure that enables businesses to send, receive, hold and move money efficiently across borders. Both fiat currencies and regulated stablecoins are integrated, for faster settlements, lower costs, and enhanced transparency. NGPES is based at 35 avenue de Friedland, 75008 Paris, and was ranked 83 in the Finance Innovation Fintech100 2025.
Interested in our solution? Talk to our team, or email sales@ngpes.com.
.avif)
.avif)
