Receive

Accept crypto payments in supported stablecoins, with a euro exit

A narrow supported list of MiCA-compliant stablecoins, controls over who is allowed to pay you, and a euro exit through a linked IBAN.

Here is the direct version of the answer for a regulated European provider: not every digital asset, a narrow supported list, and a euro exit through a linked IBAN.

  • 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 we cover

Not crypto generally

The platform holds selected MiCA-compliant stablecoins. It is not a route to accept any digital asset a customer offers.

Stablecoins, specifically

Assets that reference a fiat currency and are backed by reserves, so they work for payment, not speculation.

Controlled receiving

Sources are whitelisted in advance. Unknown inbound funds are held while support contacts you.

A euro exit

Make a Payment converts the balance to fiat and pays a bank account over traditional rails.

Why volatile assets are the wrong instrument anyway

Even where a provider will accept them, taking payment in a volatile digital asset creates a problem the business then has to manage.

  • The invoice value moves. An amount agreed on Monday is a different amount on Wednesday, and somebody has to decide who wears the difference.
  • It becomes a position, not a receipt. Holding it is a decision to be exposed to that asset, which is rarely what the sales team intended.
  • The accounting is harder. Valuation at receipt, at conversion and at period end all need a policy behind them.

A stablecoin removes all three, because the value referenced does not move while the payment is in flight. That is the entire reason the supported list looks the way it does.

How your money moves

Accepting is one of five actions, and the ones after it decide whether the money is usable.

  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.

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.

What to settle before your first payment

  1. 1Confirm the asset. Which supported MiCA-compliant stablecoin, named specifically, agreed with the payer.
  2. 2Confirm the network. Different supported networks mean different wallet addresses, and a mismatch is the most common way a transfer goes missing.
  3. 3Whitelist the payer. Sources must be approved before funds can be received, so this happens before you invoice.
  4. 4Decide your holding policy. Do you keep the balance as a stablecoin, or convert to euro on receipt? Both are valid. Choosing deliberately is what matters.
  5. 5Agree the timing expectation. If euro in a bank account is the end goal, the final leg runs on external banking rails.

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 my business accept crypto payments?

Through NGPES you can receive selected MiCA-compliant stablecoins into a custodial wallet from whitelisted sources, then hold, swap or convert them to euro and pay a bank account. It is not a route to accept any digital asset a customer might offer.

Why only stablecoins?

Because they reference a fiat currency and are backed by reserves, so the value does not move while the payment is in flight. That makes them a payment instrument rather than a position your finance team has to manage.

Which assets are supported?

Selected MiCA-compliant stablecoins. The list is deliberately narrow, so confirm the specific asset with the team before you put wallet details on an invoice.

What if a customer sends something unsupported?

The source check runs first and unrecognised inbound funds are held while support contacts you. Non-compliant assets can be converted to a compliant stablecoin as an exception, or returned to the sender.

How do we get euro from it?

Make a Payment converts the balance to fiat, instantly, and sends it to a registered bank account over traditional rails.

Do we need a wallet of our own?

No. The custodial wallet on the platform is where the balance sits, and every action runs from it.

How does this reconcile?

Receipts, swaps, conversions and payments all appear in Activity, and the full history exports to CSV or Excel.

Find out whether your customers' assets are actually supported.

It is a short conversation and it decides everything downstream.

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.