A controlled receiving point, a supported stablecoin balance, and a euro exit through a linked IBAN.
That is the stretch NGPES covers: a controlled receiving point, a supported stablecoin balance, and a euro exit through a linked IBAN.
Share your wallet address as text or a QR code. Payments arrive in your custodial wallet.
Sources are whitelisted in advance. Anything from an unrecognised source is held while support contacts you.
Keep the balance in the supported stablecoin it arrived in, or exchange it for another supported one.
Make a Payment converts the balance to fiat and pays a bank account over traditional rails.
Worth separating, because gateway is a word doing a lot of work in this market.
| Position | |
|---|---|
| A controlled receiving point | Yes. A wallet address you can share, with whitelisting on who may pay it. |
| A euro settlement route | Yes. Make a Payment converts the balance and pays out over traditional rails. |
| A hosted checkout page | Not described in the current platform documentation. Ask before assuming one exists. |
| A developer integration | NGPES states real-time API status and tracking. The public documentation is not out, so scope it with the team. |
| An exchange | No. Swap works between supported MiCA-compliant stablecoins only. |
For a business invoicing other businesses, the first two are usually what the project actually needs. If your model is consumer checkout, say so early, because that is a different conversation.
Receiving is one of five actions, and it is the ones after it that decide whether the money is useful.
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.
Most gateways optimise for taking money from anyone. In business-to-business payments that is the wrong default, and the reason is compliance rather than caution.
The trade is a setup step per payer. In exchange you stop having to explain inbound transfers after the fact, which is the expensive version of the same work.
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.
The route between a customer paying you in a stablecoin and that value being usable in your business. Here that means a controlled wallet address to receive into, whitelisted sources, and a euro exit through a linked IBAN.
Not described in the current platform documentation. If consumer checkout is central to your project, raise it with the team before planning around it.
NGPES states that real-time status and tracking are available through an API. The documentation is not published yet, so agree the scope with the team.
Selected MiCA-compliant stablecoins. Funds arriving in an asset outside that set can be converted as an exception, not as a standing service.
Make a Payment converts your stablecoin balance to fiat, instantly, and sends it to a registered bank account over traditional rails.
No. Sources are whitelisted in advance. Funds from an unrecognised source are held while the support team establishes the detail.
Every receipt, swap, conversion and payment sits in one history in Activity, exportable to CSV or Excel.
Tell us who pays you and how, and we will map it.
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)
