The technical work behind a digital euro has been visible for some years: settlement architecture, offline functionality, privacy design, the role of supervised intermediaries in distribution. Much of it is now reasonably well specified. The remaining questions are political, and they happen to be precisely the questions that determine the instrument’s effect on bank balance sheets.
Two parameters dominate: how much a holder may hold, and whether the holding earns interest. Everything else — distribution model, compensation for intermediaries, offline limits — is second order by comparison.
Why the two parameters decide the outcome
A non-remunerated digital euro with a modest holding cap is, economically, cash in a different form factor. People hold it to spend it. The aggregate balance is small relative to deposits, it does not migrate in a stress because it earns nothing, and the impact on bank funding is correspondingly limited.
A remunerated instrument with a high or absent cap is a different animal: a risk-free, interest-bearing central bank liability available to retail holders. Such an instrument competes directly with deposits, and it competes hardest exactly when banks least want it to, because a flight to a risk-free asset is what a deposit run consists of. This is the reason the design discussion has converged on a low or zero remuneration and a cap: the financial-stability argument is not subtle.
Holding limits and remuneration are not implementation details. They are the difference between a payments instrument and a deposit substitute.
China Everbright Bank Europe — Group Treasury
The corporate questions are less settled
Public debate has focused on retail holders, but the rules for business accounts matter more to the clients we serve and have received less attention. Several questions remain genuinely open in practice: whether business holdings are capped on the same basis as retail ones, how sweeping between a digital euro wallet and a commercial bank account will work intraday, and whether the instrument will be usable for the payment types that dominate corporate flows.
The sweep mechanics are the pivotal issue for treasury usability. A corporate treasurer cannot manage a payment instrument whose balance is capped and whose overflow behaviour is unpredictable. If automated linkage to a commercial account is clean and intraday, a digital euro can sit inside existing cash management with little disruption. If it is not, the instrument will be used for a narrow set of flows and ignored for the rest.
What banks are actually preparing for
From our side, preparation is mostly unglamorous: distribution integration, onboarding and identity processes, reconciliation and the customer-facing experience of moving value between a wallet and an account. The liquidity planning question — how much deposit funding might migrate and how fast — is genuinely dependent on the parameters, which is why we model scenarios rather than a central case.
- Track the business-account parameters specifically; the retail debate is a poor proxy.
- Ask providers about intraday sweep design, not just wallet functionality.
- Include a deposit-migration scenario in liquidity planning, sized to the prospective cap rather than to a guess.
- Do not defer integration work pending final parameters: the onboarding and reconciliation build is parameter-independent.
What it means for clients
- Corporate treasurers should follow the business-account holding rules rather than the retail cap debate.
- Cash management reviews should ask how a wallet balance would be swept to and from operating accounts intraday.
- Financial institution clients should size a deposit-migration scenario against the prospective cap.
