USDC significant e-money token: the EBA's October 14 label changes who supervises the reserves — the MiCA rule merchants should read is the one that counts their checkout

What the EBA decided: USDC is the first significant e-money token

On Tuesday, October 14, 2026, the European Banking Authority published a short press release: it has classified USDC as the first significant e-money token in the European Union. E-money tokens (EMTs) are MiCA's legal name for stablecoins pegged to a single official currency. According to the EBA, 45 of them have been notified in the EU so far. USDC is the first to move into the "significant" tier.

The practical change starts on November 12, 2026, when USDC moves to what MiCA calls dual supervision. The EBA takes direct responsibility for four areas: own funds, the reserve of assets, liquidity requirements, and recovery and redemption plans. France's Autorité de Contrôle Prudentiel et de Résolution (ACPR), which supervises Circle's European e-money institution, keeps governance, qualifying holdings, fit-and-proper assessments, outsourcing and conflicts of interest.

The release also notes that USDC is issued in the EU by Circle Internet Financial Europe SAS and in the United States by Circle Internet Financial, LLC — the same token from two issuers. To supervise that cross-border structure, the EBA signed a memorandum of understanding with the New York State Department of Financial Services. Circle reported roughly $73 billion of USDC in circulation at the end of the second quarter.

How a stablecoin becomes "significant"

MiCA Article 56 tells the EBA to classify an e-money token as significant when it meets at least three of the seven criteria in Article 43(1), either in its first reporting period or in at least two consecutive reports. The criteria:

• more than 10 million holders;
• more than €5 billion in issued value, market capitalisation or reserve of assets;
• more than 2.5 million transactions and €500 million per day on average;
• an issuer designated as a gatekeeper under the Digital Markets Act;
• significance on an international scale, including use for payments and remittances;
• interconnectedness with the financial system;
• an issuer that issues at least one other token and also provides at least one crypto-asset service.

The EBA didn't say which three USDC met, and it reassesses the classification every year. Article 56(2) adds a detail that fits USDC's two-issuer structure: when several issuers issue the same token, the criteria are assessed after aggregating the data from all of them.

What "significant" changes for USDC's issuer — and what it doesn't change for you

Article 58(1) lists what significance adds. Most of it is borrowed from MiCA's stricter regime for asset-referenced tokens:

• Reserve rules (Articles 36 to 38): the reserve-of-assets regime for asset-referenced tokens, including legal and operational segregation from the issuer's own estate, replaces the general e-money rules.
• Reserve audits every six months: an independent audit of the reserve twice a year, counted from the date of classification.
• Liquidity management and stress testing (Article 45(3) and (4)): a liquidity policy built for stress scenarios, and regular liquidity stress tests whose results can lead the EBA to tighten the requirements.
• Higher own funds (Article 45(5)): 3% of the average amount of the reserve assets.
• Custody across providers (Article 45(2)): the token must be holdable by different licensed custodians on fair, reasonable and non-discriminatory terms.
• A remuneration policy (Article 45(1)) that doesn't reward relaxing risk standards.

Circle's own reading adds a number. In its October 1 submission to the European Commission's MiCA review, Circle wrote that MiCA requires e-money token issuers "to hold a minimum of 30% of reserve assets in commercial bank deposits, rising to 60% for issuers of EMTs classified as 'significant.'" Circle argues that floor "should be reconsidered and replaced with a less rigid minimum asset liquidity requirement," and it also objects to a 35% cap on exposure to any single sovereign and a cap of 1.5% of a bank's total assets per banking counterparty.

For a business that holds USDC, that's the issuer-side change worth understanding. When more of the reserve sits in bank deposits, more of it depends on banks, and the EBA is now the supervisor watching that mix. The trade-off isn't new to USDC. In March 2023, when Silicon Valley Bank failed with part of Circle's reserves on deposit, USDC traded below 90 cents for a weekend before it recovered. Deposits are the most liquid reserve asset until the bank holding them isn't.

What doesn't change is everything on the merchant's side of the counter:

• USDC stays a MiCA-authorised e-money token. Significance is a supervisory tier, not a licence or a sanction. Nothing in the EBA's release restricts who can accept, hold or transfer USDC.
• Redemption works the same. Under Article 49, holders have a claim against the issuer, which must redeem at par, at any time and without a fee.
• Your European customers can still pay in it. EU-licensed platforms can keep servicing USDC. They can't keep servicing the non-MiCA stablecoins ESMA moved against on October 8.

The MiCA rule merchants should read: the cap on everyday payments

The significance label got the headlines. The rule that actually involves merchants has applied to USDC since MiCA's stablecoin titles took effect on June 30, 2024, and it doesn't depend on the label at all.

Article 58(3) of MiCA is one sentence: "Articles 22, 23 and 24(3) shall apply to e-money tokens denominated in a currency that is not an official currency of a Member State." USDC is a dollar token, so those provisions apply to it whether or not it's significant. Together they're the EU's guardrail against a foreign-currency token becoming everyday money inside a European currency area:

• Article 22 — the count. Every quarter, the issuer of a token above €100 million reports holders, issued value and reserve size, and the average number and value of transactions per day. It also reports an estimate of how many of those transactions are "associated to its uses as a means of exchange within a single currency area" — in plain language, payments for goods and services.
• Article 23 — the cap. If that estimate averages more than 1 million transactions and €200 million per day in one currency area over a quarter, the issuer must stop issuing the token. Within 40 working days it must submit a plan to bring use back under both numbers. The regulator uses the issuer's figure, its own estimate or the ECB's, "whichever is higher," and can require changes "such as imposing a minimum denomination amount."
• Article 24(3) — the backstop. If the ECB says the token threatens payment systems, monetary policy transmission or monetary sovereignty, the regulator must limit the amount issued or impose a minimum denomination.

Two details are easy to miss. First, the cap says "respectively": a token has to cross both thresholds, not just one. Second, the remedy the law names is a minimum denomination, a floor on payment size. That lever lands squarely on small, everyday payments: a coffee, a haircut, a parking fee. A treasury transfer wouldn't notice it. A café would.

How MiCA counts a payment — and where your checkout sits

The counting method is set out in Commission Delegated Regulation (EU) 2025/298, the technical standard for estimating means-of-exchange transactions. It applies to non-euro e-money tokens like USDC "mutatis mutandis." Its Article 3 starts from every transaction in the quarter and deducts:

1. exchanges for money or other crypto-assets with the issuer or a crypto-asset service provider, such as buying or selling USDC at an exchange;
2. use as collateral for trading financial instruments;
3. settlement of derivative contracts;
4. other transactions that the issuer can show, on reasonable grounds, aren't payments for goods or services.

What's left is meant to be commerce. The regulation then draws the boundaries:

• On-chain and off-chain both count. A transfer between two customer accounts on a platform's internal ledger is in, not only blockchain transactions.
• Custodial wallets count. Payments between two custodial wallets, and between a custodial wallet and a non-custodial one, are in.
• Self-custody to self-custody is outside the issuer's estimate. The recitals explain that payments between two non-custodial wallets are left out because "issuers may not have the necessary information to report such transactions." They still appear in the issuer's total transaction figures.
• Same currency area only. Payer and payee must both be located in the same single currency area within the EU: habitual residence for people, registered office for companies.
• Moving your own money doesn't count. Transfers between accounts or addresses belonging to the same person are excluded.

The issuer calculates the figures for each currency area as of March 31, June 30, September 30 and December 31. Under Article 22(3), crypto-asset service providers must give the issuer the data it needs, including transactions settled off the ledger.

Now place a few real businesses in that method:

• A café in Lisbon taking USDC through a custodial gateway. The gateway's wallet is custodial, and café and customer are both in the euro area, so every sale counts toward the euro-area estimate.
• The same café settling to its own wallet, with the customer paying from an exchange app. The customer's wallet is custodial, which makes it a custodial-to-non-custodial payment. It still counts.
• The same café, with the customer paying from a self-custody wallet. Non-custodial to non-custodial puts the payment outside the issuer's reported estimate, but not outside the rule. Article 23(2) lets the regulator use the ECB's estimate if it's higher, and the ECB doesn't depend on what the issuer can see.
• A design studio in Madrid invoicing a client in New York. The payer isn't in the euro area, so the payment isn't part of the euro-area figure, whatever wallets are involved.
• A shop in Warsaw paid by Polish customers. This is counted separately. Each currency area is measured on its own, and the threshold is the same €200 million a day for Poland as for the euro area.

None of this is a way around anything, and no business should design its payment flows to stay out of a count. The cap binds the issuer, not you, and your obligations as a merchant don't change with how a payment is classified. The useful reading is simpler: MiCA measures dollar-token payments where it has visibility, at regulated intermediaries, and your checkout is part of what it measures.

How far is USDC from the cap?

Nobody outside the supervisors knows. The quarterly estimates go to the issuer's national supervisor, which shares them with the ECB. They aren't published, and neither the EBA's release nor Circle's submission gives a figure.

The public evidence points to a long way. In its November 2025 Financial Stability Review, the ECB estimated that "only around 0.5% of volumes are organic retail-sized transfers," and concluded that stablecoin use "seems to be primarily driven by their role within the crypto-asset ecosystem." Most USDC movement in Europe is trading and treasury, and the methodology strips both out.

But the cap is the one MiCA provision that grows with merchant adoption. Every European café, salon and online store that adds USDC at checkout feeds the same counter. If dollar stablecoins catch on as everyday money inside the euro area, the EU has already decided how it will slow them, and its named tool, a minimum payment size, would hit the smallest tickets first.

Euro-denominated e-money tokens aren't covered by Article 58(3) at all, because the euro is an official currency of Member States. For a business whose costs are entirely in euros, that's a real argument for euro tokens and an honest one to raise with your advisers. Payzum's auto-convert targets USDC or USDT today, not euro tokens.

Where Payzum fits — and where it doesn't

Payzum is a non-custodial, crypto-only payment processor. Customer payments settle directly into wallets the merchant controls; Payzum never holds, pools or controls the money. Settlement is the payment. That's why the EBA's decision lands lightly on a Payzum merchant:

• There's no Payzum balance. None of your money sits with an intermediary while USDC's supervision changes hands, so there's nothing for a provider to freeze, delist or force-convert.
• Your receiving address is your own wallet. In the language of Delegated Regulation 2025/298, it's a non-custodial wallet: you control the means of access. How any given payment is classified then depends on the payer's side and on MiCA's method. We don't engineer it.
• You choose what lands. With optional auto-convert, accepted crypto settles in your wallet as USDC or USDT. For an EU business, USDC is the MiCA-compliant one of the two.
• Fast, final and priced plainly. Confirmations take about 0.4 seconds on Solana and around 2 seconds on Base or Polygon, with no chargebacks. Payzum charges 0.5% per processed sale plus on-chain network gas.

And where it doesn't fit, plainly:

• Payzum doesn't give legal advice. Which tokens your business accepts in the EU, and what your obligations are, are questions for your counsel.
• It doesn't settle to a bank account. Payzum is crypto-only. You turn USDC into euros at a licensed provider of your choice.
• It doesn't settle in euro stablecoins. The auto-convert targets are USDC and USDT.

How it works, step by step

1. Connect wallets you own. Create an account and add receiving addresses on the networks you need. For USDC that means Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain or Avalanche, and you can add Bitcoin too.
2. Choose how you charge. In person, use the POS: a new QR for every sale, any phone as a terminal and PIN-protected cashiers. Online, use hosted checkout (redirect, modal or inline), payment links and buttons, invoices with expiration and overpayment detection, subscriptions, or a drop-in plugin for WooCommerce, Magento, PrestaShop, Shopware and others.
3. Set your settlement token. Turn on auto-convert so accepted crypto settles as USDC, or receive exactly what the customer sent.
4. Wire it into operations. Signed webhooks feed your order and accounting systems. 2FA and a full audit log cover access. Stablecoin payouts on EVM networks pay suppliers and contractors from your own wallet.

USDC through a custodial gateway vs USDC settled to your own wallet

Fair objections

"'Significant' sounds like a warning. Should we stop accepting USDC?"

No. Significance means more supervision: the EBA watches reserves, liquidity and own funds directly, and the reserve is audited twice a year. It isn't a licence or a penalty, and nothing in the decision restricts accepting USDC.

"Is the cap going to stop USDC next quarter?"

There's no public sign of it. The figures aren't published, and the ECB's own data says retail-sized payments are a tiny share of stablecoin volume. It's worth watching, not worth panicking over. Just remember that the counter moves with merchant adoption.

"Doesn't a 60% bank-deposit floor make USDC riskier?"

It shifts the risk more than it adds to it: deposits are liquid until the bank holding them isn't, as March 2023 showed. For a merchant, the practical lever is how long you hold. Settling to your own wallet lets you convert or move funds on your own schedule, weekends included, instead of waiting on a provider's payout window.

"Shouldn't a euro-area business just use a euro stablecoin?"

If all your costs are in euros, it's a fair question, and Article 58(3) doesn't apply to euro tokens. It's also a demand question: what do your customers actually hold? Payzum's auto-convert targets USDC and USDT, not euro tokens. If euro settlement is a must, tell us on a call and we'll be straight about what fits.