USDT payments

USDT payments and the compliant route under MiCA

Most businesses trading outside Europe are offered USDT at some point. NGPES is a France-based payment provider built on MiCA-compliant stablecoins, with a defined process for inbound assets that sit outside that set, so a payment your counterparty has already sent does not simply fail.

Talk to us before you invoice and we will confirm the asset, the network and the wallet address to put on it, so the payment arrives as a normal receipt rather than an exception.

  • 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 we handle an inbound USDT payment
  • 1The offerYour counterparty proposes USDT because it is what they hold.
  • 2The constraintNGPES holds selected MiCA-compliant stablecoins only.
  • 3The checkWe check the source. Unknown sources are held rather than rejected.
  • 4The exceptionWe can convert a non-compliant asset into a compliant one, case by case.
  • 5Or the returnWhere conversion is not appropriate, we return the funds to the sender.
Services will become available only upon obtaining the relevant CASP and EMI authorisations.

The short version

What is supported

Selected MiCA-compliant stablecoins. That is the entire set the platform holds.

Where USDT sits

Outside the MiCA-authorised set, which is why it is not simply held and used like a supported asset.

What can happen

Inbound funds in a non-compliant asset can be converted to a compliant one as an exception, not as a standing service.

What to do

Agree a supported asset with your counterparty before invoicing. It converts an exception into a normal receipt.

What NGPES can hold, and why

MiCA sets the conditions under which stablecoins may be offered in the EU, covering authorisation of the issuer, the reserves behind the token, and the holder's right to redeem. Assets that meet those conditions and assets that do not are treated differently by any regulated European provider.

This is not a judgement about USDT's usefulness or its liquidity, both of which are considerable. It sets out what a France-based provider with EMI and CASP authorisations in progress can hold on your behalf.

The practical version for a business: the regulatory status of the asset your counterparty wants to pay in is now an operational fact that affects whether the payment lands cleanly, how long it takes, and whether a person has to intervene.

How we handle it when USDT arrives

  1. 1The source check runs first. If the payer is not whitelisted, the funds are placed on hold regardless of the asset.
  2. 2Support makes contact. The team gets in touch to establish the details behind the transfer.
  3. 3Conversion, as an exception. Funds in an asset that is not MiCA-compliant can be converted into a MiCA-compliant stablecoin. This is handled case by case.
  4. 4Or a return. Where conversion is not appropriate, the funds are returned to the sender.
  5. 5Then it is ordinary. Once converted, the balance behaves like any other supported stablecoin: send, swap, or convert and pay out as fiat.

The route works. It is slower than a standard receipt and it needs a person to review it, which is why we agree the asset with you up front.

What to put on your invoice

  • The supported stablecoin, named. Not the word stablecoin. The specific asset, confirmed with the team.
  • The network. Different supported networks mean different wallet addresses, and a mismatch is how transfers get lost.
  • The wallet address for that network. Taken from the platform, not from an old email.
  • The payer, already whitelisted. Sources must be approved before funds can be received, so this happens before you invoice, not after they pay.

Four lines, agreed once per counterparty. It is the difference between a payment that lands and one that sits on hold while somebody works out what to do with it.

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 by on-ramp and off-ramp. Dedicated IBANs, and holding fiat balances against them, arrive with the EMI authorisation.
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.

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. Once the EMI authorisation is granted, one organisation account will hold subaccounts per team, function or payment flow, each with its own balances and transaction history, 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.

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 I accept USDT payments through NGPES?

NGPES holds selected MiCA-compliant stablecoins, and USDT sits outside the MiCA-authorised set. If a counterparty sends it, we can convert it into a compliant stablecoin as an exception, not as a standing service, so talk to us before you invoice in USDT.

Why can a European provider not just hold it?

MiCA sets conditions covering issuer authorisation, reserves and redemption. A regulated European provider treats assets inside and outside that framework differently, and that is a legal position rather than a preference.

What if a counterparty sends USDT anyway?

Our source check runs first, and funds from an unrecognised source are held while our team contacts you. From there we either convert them into a compliant stablecoin as an exception, or return them to the sender.

Can I use Swap to convert USDT myself?

Swap operates between supported MiCA-compliant stablecoins. We handle an asset from outside that set as an exception rather than through the normal swap function.

What should I ask a counterparty to send instead?

A supported MiCA-compliant stablecoin, on a supported network, agreed before the invoice goes out.

Does this slow the payment down?

An exception needs review, so yes, compared with a standard receipt in a supported asset. That is the main practical cost.

Where do I see what happened to it?

Every receipt, conversion and payment appears in Activity, and the full history exports to CSV or Excel.

Talk to us before you invoice.

We will confirm the asset, the network and the address, so the payment lands first time.

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.