Wallet and IBAN infrastructure

A crypto business account for fiat and supported stablecoins in one place

One account and one identity, rather than a bank on one side and an exchange account on the other.

This is what an NGPES account gives a company, and where its edges are.

  • 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 the account contains

A custodial wallet

The operational object. Supported stablecoins are held here and every action runs from it.

A dedicated IBAN

Linked to the wallet, connecting it to traditional fiat rails for on-ramp and off-ramp.

Subaccounts

Separate balances and transaction histories per team, function or payment flow, under central control.

Counterparty records

The list of who you may pay and who may pay you, with routing details verified in advance.

What the balance is actually made of

The most important thing to understand before opening one, because it shapes your treasury policy.

The platform holds supported stablecoins. It does not hold fiat. When euro arrives at your linked IBAN it is processed through the on-ramp and converted into a supported stablecoin, and that is what appears as your balance. When you need euro out, the balance converts back and leaves through traditional rails.

The account is a stablecoin account with a compliant euro entrance and exit, not a euro account with a crypto feature attached. Whether that suits you depends on whether your business is comfortable holding a stablecoin balance between transactions, which is a real question and one worth answering internally before onboarding rather than during it.

How your money moves

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.

  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.

Running it as a finance function

  • Structure it before you use it. Decide which flows deserve their own subaccount. Retro-fitting that separation once transaction history exists is harder than setting it up on day one.
  • Register counterparties in advance. Payments only go to recorded counterparties, so the setup work belongs in onboarding rather than on the day a payment is due.
  • Whitelist your payers. Sources have to be approved before funds can be received, which means telling the platform about a new customer before you invoice them.
  • Export on a schedule. The full transaction history exports to CSV or Excel. Doing that monthly is far less painful than doing it annually.
  • Watch the dashboard. Balances, activity and account-level liquidity are visible in real time, which removes most of the reasons finance emails operations.

None of this is exotic. It is the same discipline a company applies to its bank accounts, applied to an account whose balance happens to be a stablecoin.

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

What is a crypto business account?

A company account holding supported stablecoins in a custodial wallet, with a dedicated IBAN attached for moving fiat in and out, plus counterparty controls, subaccounts and a full transaction record.

Does the account hold euro?

No. Fiat is not held on the platform. It arrives and leaves through the linked IBAN and converts into a supported stablecoin on the way in.

Can we split funds across departments?

Yes. Subaccounts each keep their own balances and transaction history while the organisation retains central control.

Who can we pay from it?

Counterparties recorded in the platform, with the name and the IBAN or wallet address attached. Payments cannot be sent to an unrecorded destination.

Can we connect our existing bank accounts?

You can register your own external bank accounts and wallet addresses. They are verified before use and support flows involving the same organisation.

Can we invite colleagues and set permissions?

Team management is announced as coming soon rather than available today.

What does the accountant get?

A real-time dashboard and a full transaction history covering top-ups, transfers, payments and swaps, exportable to CSV or Excel.

See how the account would be structured for your business.

Bring your entity structure and your payment flows. That is the conversation that matters.

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.