Payment execution

Mass payouts to counterparties across 150+ countries

For marketplaces, platforms and agencies paying long recipient lists across scattered countries, where the per-transfer bank fee makes the maths fail.

Stablecoin rails change that maths, because the cost of a transfer does not scale with distance. Here is what that looks like in practice with NGPES, including what the platform does not do yet.

  • Payment Institution today
  • EMI in progress, France
  • CASP in progress, France
  • GDPR and DORA compliant
  • ISO 27001 and SOC 2 Type II in progress
How a payment runs
  • 1Top-UpFiat arrives through the linked IBAN and is converted into a supported stablecoin.
  • 2SendStablecoins go to a pre-registered counterparty or a verified wallet.
  • 3Make a PaymentStablecoins convert back to fiat and leave over traditional banking rails.
  • 4ReceiveShare your wallet address or QR code to take stablecoins in.
  • 5SwapExchange one supported stablecoin for another inside the platform.
Services will become available only upon obtaining the relevant CASP and EMI authorisations.

What helps at volume

Cost that ignores distance

A transfer to a recipient on the other side of the world costs what the network costs, not what a correspondent chain costs.

Registered counterparties

Recipients are set up once as counterparty records. After that the routing details are already correct and verified.

Subaccounts

Payout funds can sit in their own subaccount, with their own balance and history, separate from the rest of treasury.

One export

Every payment lands in Activity and the whole run exports to CSV or Excel for reconciliation.

Be clear about the current shape of this

Most payout platforms sell on a file upload and an approval matrix. It would be easy to imply the same here and it would not be true, so here is the position.

  • There is no documented bulk or batch upload. Payments are executed to registered counterparties. If your model depends on submitting a file of thousands of rows, raise it with the team before you plan around it.
  • Approval workflows and per-payment limits are not described in the current platform documentation. If your finance controls require them, ask first.
  • Team management is announced as coming soon. Assigning who may approve what is not available yet.

What the platform does give you at volume is the economics, the pre-verified destinations and a single reconcilable record. That is genuinely useful, and it is a different claim from an enterprise payouts suite.

How your money moves

Every payment in a run goes through the same sequence.

  1. 1Top-Up. You transfer fiat to your linked IBAN. It is converted through the on-ramp and lands in your wallet as a supported stablecoin. Where the fiat currency and the stablecoin denomination match, that conversion is 1:1 before fees.
  2. 2Register the counterparty. Anyone you pay has to exist as a counterparty record first, holding the name and the IBAN or wallet address. Anyone paying you has to be whitelisted as a source.
  3. 3Send or Make a Payment. Send moves stablecoins to a counterparty wallet. Make a Payment converts stablecoins back to fiat and sends it over traditional rails to a bank account.
  4. 4Receive and Swap. Incoming stablecoins arrive at your wallet address. Swap exchanges one supported stablecoin for another without leaving the platform.
  5. 5Reconcile. Every transfer, payment, swap and top-up sits in Activity, and the whole history exports to CSV or Excel.

Where the money actually goes

Recipient typeRouteWhat they receive
Already holds a walletSendA supported stablecoin, arriving once funds are available
Wants ordinary moneyMake a PaymentFiat in their bank account, over traditional rails
Your own entity abroadRegistered external accountEither, once the account or wallet is verified

The mix matters more than people expect. If most of your recipients want fiat, the speed benefit lands mainly on your side of the transaction, in the funding and the treasury movement, rather than in how fast the recipient sees the money.

Controls built into every payment

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.

  • We pre-register your counterparties. Funds can only be sent to a party already recorded in the platform, with the routing details attached. There is no free-text payment field to get wrong.
  • We whitelist your sources. Money can only be received from parties you have approved in advance.
  • We hold unknown sources. If funds arrive from a source that is not recognised, they are placed on hold and the support team contacts you. They are then either returned or released to you.
  • Subaccounts separate the flows. One organisation account can hold subaccounts per team, function or payment flow, each with its own balances and transaction history, all under central control.
  • We keep everything on the record. The dashboard shows balances, activity and account-level liquidity in real time, and Activity exports the full history to CSV or Excel for reconciliation.

Settlement speed

Here is what each leg takes.

LegTiming
Stablecoin transferSettles instantly within the platform, once funds have been received and are available.
Stablecoin to fiat conversionInstant.
Fiat arriving at the recipientDepends on the destination currency, the geography and the external banking rails involved. NGPES does not control this leg.
Fiat top-upDepends 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.

What the platform supports

This is what the platform supports today.

Position today
StablecoinsSelected MiCA-compliant stablecoins only. Assets outside that set are not held on the platform.
Non-compliant assetsFunds 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.
FiatMoves in and out through the linked IBAN via on-ramp and off-ramp. Fiat balances are not held on the platform.
SwapBetween supported MiCA-compliant stablecoins only.
External accountsYou can register your own external bank accounts and wallet addresses. They are verified before use, and only for flows involving the same organisation.
Team managementAnnounced as coming soon. Not available yet.

If a particular asset, currency or corridor matters to your business, ask us before you build around it.

Our regulatory position

Where NGPES is authorised today.

  • Payment Institution status today
  • EMI in progress, through NGPES Payments in France
  • CASP in progress, through NGPES Digital in France
  • GDPR and DORA compliant
  • ISO 27001 and SOC 2 Type II in progress

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.

Coverage and settlement times

What NGPES states today.

What NGPES states
ReachFunds move across 150+ countries via SEPA, SWIFT and local rails.
Stablecoin settlementT+0.
Fiat settlementT+1.
Processing24/7/365, with no end-of-day batch. Everything is processed in real time.
ConversionInstant conversion between fiat, in USD, EUR and GBP, and stablecoins.
Exchange24/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.

Frequently asked questions

Can NGPES handle mass payouts?

Payments are executed to registered counterparties, and there is no documented bulk or batch upload today. If you are paying hundreds or thousands of recipients on a schedule, discuss the mechanics with the team before you build around them.

Why use stablecoin rails for small payments?

Because the transfer cost is a function of the network, not the distance, small cross-border amounts are viable at all.

Do I have to set up every recipient?

Yes. Each recipient exists as a counterparty record with the routing details attached before funds can be sent. It is set up once per recipient, not once per payment.

Is there a minimum payment size?

Not stated in the current platform documentation. Confirm it with the team, because it decides whether small-value payouts are viable for you.

Can recipients be paid in their local currency?

Make a Payment converts your stablecoin balance to fiat and sends it over traditional rails. Which currencies and countries are reachable is worth confirming for your specific list.

Can we separate payout funds from operating funds?

Yes, through subaccounts, each with its own balances and transaction history under central control.

How do we reconcile a payout run?

Every payment appears in Activity alongside the top-ups that funded it, and the full history exports to CSV or Excel.

Send us a sample of your payout file.

We will tell you which parts the platform handles today and which need a conversation.

About NGPES

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.