Top-Up, transfer, convert and pay out, with real-time API status and tracking at each leg of the payment.
This is what the middle looks like on the NGPES platform, step by step, with the controls named.
Fiat via Top-Up through the linked IBAN, or stablecoins via Receive from a whitelisted source.
Source verification on the way in. Counterparty verification before anything goes out.
On-ramp at the entrance, Swap between supported stablecoins, off-ramp at the exit.
Send to a counterparty wallet, or Make a Payment to a bank account over traditional rails.
| Point | What happens |
|---|---|
| Before you can receive | The source must be whitelisted. Approval happens in advance, not at the moment money arrives. |
| On arrival from an unknown source | Funds are placed on hold. Support contacts you to establish the detail, then the funds are returned or released. |
| On a non-compliant asset | Only selected MiCA-compliant stablecoins are held. Non-compliant inbound funds can be converted as an exception, case by case. |
| Before you can send | The recipient must exist as a counterparty record, with the name and the IBAN or wallet address attached. |
| On your own external accounts | They can be registered, and are verified before use, for flows involving the same organisation. |
The pattern is consistent: verification happens before the money moves rather than as a reconciliation exercise afterwards. That is slower to set up and considerably faster to run.
The platform runs on a stablecoin settlement layer. Fiat is not held inside it. It moves in and out through a linked IBAN, and converts on the way through.
Three different conversions get confused with each other, so it is worth separating them.
Only the middle one is optional. The other two are structural, because fiat is not held on the platform at any point.
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.
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.
Funds arriving through the on-ramp or as a stablecoin transfer, source and counterparty verification, any conversion needed, then a transfer to a wallet or a fiat payment to a bank account, with all of it recorded in one history.
Sources must be whitelisted before funds can be received. Funds arriving from an unrecognised source are placed on hold while the support team establishes the detail, and are then either returned or released.
Confirm this with the team for your specific flow. The documented actions are initiated rather than described as automatic on arrival.
Up to three: on-ramp at the fiat entrance, an optional Swap between supported stablecoins, and off-ramp at the fiat exit. The first and last are structural because fiat is not held on the platform.
A fiat top-up converts 1:1 where the fiat currency and the stablecoin denomination are the same, before any applicable fees.
Supported stablecoins to a registered counterparty's wallet, or fiat to a registered bank account over traditional rails.
Every top-up, transfer, payment and swap sits in Activity, visible alongside a real-time dashboard, and the full history exports to CSV or Excel.
Start to finish, including the checks. It is the fastest way to see whether this fits.
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)
