E-money sits at the core of modern digital payments, enabling billions of transactions every year through wallets, prepaid cards, and mobile money platforms. Understanding how it works, who can issue it, and how it differs from bank money is essential for any merchant or developer building payment flows in regulated markets.
How E-Money Works
E-money follows a straightforward lifecycle: funds in, digital value credited, payments made, funds out. Each step is governed by strict regulatory requirements that protect the end user. The five stages below describe a typical e-money payment from issuance to settlement.
Customer deposits fiat currency
A user loads funds into their account via bank transfer, debit card, or cash at a supported location. The e-money institution receives the underlying fiat currency and places it in a safeguarded account, ring-fenced from the EMI's own capital.
E-money is issued at par
The EMI credits the customer's account with an equivalent amount of e-money — one unit of e-money for every unit of fiat received. This 1:1 parity is mandatory under e-money regulation; the issuer cannot inflate or deflate the balance.
Payment is initiated
The customer authorises a payment to a merchant or peer. If both parties hold accounts at the same EMI, the transaction settles instantly on the issuer's internal ledger. Cross-institution payments route through card networks, SEPA, or open banking rails depending on the product.
Merchant account is credited
The recipient's e-money balance is updated in real time. For merchants, funds typically appear in their digital wallet or payment account immediately, with sweep-to-bank options available on a daily or on-demand basis depending on the EMI's terms.
Redemption on demand
The e-money holder can request redemption of any unused balance at any time and at par value. The EMI transfers the equivalent fiat from its safeguarding pool back to the customer's nominated bank account, minus any contractually disclosed fees.
Why E-Money Matters
E-money has moved from a niche product for prepaid cards to the backbone of consumer and business payments across the globe. Its growth reflects both technological adoption and regulatory maturation that has made it a trustworthy alternative to traditional bank accounts.
The global stored-value and e-money market processed approximately $8.6 trillion in transaction volume in 2023, with compound annual growth projected above 12% through 2028 (Statista, Digital Payments Report 2024). In the EU alone, the European Banking Authority's public register lists over 300 authorised e-money institutions as of early 2025, up from fewer than 200 a decade ago. Globally, the GSMA Mobile Money Report 2024 estimates that more than 1.75 billion registered mobile money accounts — the majority of which operate on e-money models — are active in emerging markets, providing financial access to populations that traditional banking has failed to reach.
PSD2 has been a significant catalyst in Europe, establishing a unified legal framework that allows EMIs to passport their authorisation across the EEA, reducing the cost of cross-border expansion and intensifying competition with incumbent banks.
Regulatory baseline
The EU E-Money Directive 2 (EMD2, 2009/110/EC) and the UK's Electronic Money Regulations 2011 are the primary legal frameworks governing e-money issuance. Both require minimum own funds of €350,000 (or equivalent), ongoing safeguarding of 100% of customer funds, and AML compliance proportionate to transaction volumes.
E-Money vs. Bank Deposits
E-money and bank deposits are both denominated in fiat currency, but they differ substantially in legal treatment, interest accrual, protection mechanisms, and who can issue them. Merchants and developers choosing between an EMI account and a business bank account should understand these distinctions clearly.
| Attribute | E-Money | Bank Deposit |
|---|---|---|
| Issuer | Licensed EMI or bank | Credit institution (bank) only |
| Backing | 100% safeguarded fiat reserves | Fractional reserve; lent to borrowers |
| Interest | Cannot accrue interest by law | May earn interest |
| Deposit protection | Safeguarding obligation (not FSCS/DGS) | FSCS/DGS up to local limit (e.g. £85k, €100k) |
| Speed of payment | Often instant (closed-loop) | Dependent on rail (SEPA, CHAPS, etc.) |
| Account opening | Lighter KYC, no branch required | Full KYC, credit assessment common |
| Regulatory framework | EMD2 / EMRs + PSD2 | CRD/CRR + national banking law |
| Passporting (EU) | Available via EMD2 | Available via CRD |
A payment institution occupies adjacent space — it can move money but cannot issue e-money or hold customer funds beyond execution timelines without additional authorisation.
Types of E-Money
E-money products vary by the medium through which value is stored and accessed. Understanding the distinctions helps when evaluating which product type fits a given use case or integration.
Hardware-based e-money stores value on a physical chip, such as a prepaid card or NFC-enabled device. The balance exists on the card itself and can be used offline, making it suitable for transit systems and low-connectivity environments.
Software-based e-money stores value on a server and is accessed through a mobile app, web dashboard, or API. This is the dominant model for consumer wallets, business payment accounts, and embedded finance products. Settlement relies on internet connectivity and the issuer's ledger.
Mobile money is a subset of software-based e-money designed for feature phones and USSD networks, widely deployed in sub-Saharan Africa, South and Southeast Asia. Providers like M-Pesa operate under e-money or equivalent licensing frameworks.
Prepaid card programmes sit at the intersection of hardware and software: value is held on the issuer's server but accessed via a physical or virtual card running on Visa or Mastercard rails. This model is common for corporate expense management and consumer reward schemes.
Best Practices
Effective use of e-money requires both commercial discipline and technical rigour. The obligations and opportunities differ depending on whether you are accepting it as a merchant or building on top of an EMI's infrastructure as a developer.
For Merchants
Verify EMI authorisation before onboarding. Always confirm that a payment service provider offering an e-money account is listed on the relevant national regulator's public register (FCA, BaFin, ACPR, etc.). Unlicensed providers cannot legally safeguard your funds.
Understand sweep schedules. E-money balances held in a business payment account are not automatically swept to your bank. Configure automatic sweeps or monitor balances actively to avoid liquidity gaps, particularly around high-volume periods.
Treat e-money accounts as operational, not savings, accounts. Since e-money cannot earn interest, parking significant reserves in an EMI account has an opportunity cost. Use bank accounts for treasury and e-money accounts for operational payment flows.
Check redemption terms in your contract. Regulation guarantees redemption rights, but some EMIs apply fees after contract expiry or for amounts below a minimum threshold. Read the terms before committing high volumes.
For Developers
Use the EMI's safeguarding structure to your advantage. If you are building a regulated product on top of an EMI's API, understand which entity holds the e-money licence — yours or the EMI's — and who bears the safeguarding obligation. Incorrect assumptions create regulatory exposure.
Implement idempotency on all payment calls. E-money ledger operations can fail mid-flight due to network issues. Without idempotency keys, retries risk double-crediting or double-debiting balances, which are notoriously difficult to reconcile.
Log all balance transitions with timestamps. Regulators require EMIs to maintain detailed transaction records. If you are building a platform on top of an EMI's infrastructure, ensure your own logs match the EMI's ledger state at all times for audit readiness.
Respect redemption API endpoints. Building a product that prevents or delays redemption — even unintentionally through UX friction — can constitute a regulatory breach. Redemption must be technically straightforward and clearly surfaced in your product flows.
Common Mistakes
Even experienced teams make avoidable errors when working with e-money products. These five mistakes appear repeatedly in compliance reviews and post-incident analyses.
Confusing safeguarding with deposit insurance. E-money safeguarding protects customer funds through segregation, not through a government-backed guarantee scheme. Communicating to customers that their funds are "insured" in the same sense as a bank deposit is misleading and potentially unlawful.
Issuing e-money without a licence. Accepting funds and crediting an internal balance — even for a loyalty programme or marketplace wallet — can constitute e-money issuance under EMD2 if it meets the regulatory definition. Many startups unknowingly breach this rule. Always obtain a legal opinion before launching a stored-balance product.
Ignoring AML obligations for e-money accounts. EMIs must apply transaction monitoring, customer due diligence, and suspicious activity reporting just as banks do. Merchants building on EMI APIs that handle user funds inherit downstream AML obligations depending on their agreement structure.
Assuming instant settlement equals instant finality. Closed-loop e-money transactions settle immediately on the issuer's ledger, but that does not mean the transaction is irrevocable. Chargebacks, disputes, and fraud reversals can claw back funds. Build reconciliation logic that treats all settlements as provisional until a defined confirmation window has passed.
Failing to reconcile e-money balances daily. Discrepancies between the EMI's ledger and your own records compound quickly at scale. A daily automated reconciliation that flags variances above a set threshold is the minimum acceptable operational standard.
E-Money and Tagada
Tagada's payment orchestration layer connects merchants to multiple open banking providers, acquirers, and EMIs through a single API. For merchants running payment flows that touch e-money accounts — whether their own business wallet or their customers' stored-value balances — orchestration matters because EMI routing decisions affect settlement speed, FX costs, and fallback behaviour.
When routing through Tagada, you can configure priority rules that prefer EMI-based rails for low-value, high-frequency domestic payments where instant settlement is critical, while falling back to card or bank transfer for cross-border transactions. This reduces settlement latency without requiring separate EMI integrations for each market.
Tagada does not itself hold an e-money licence and does not safeguard funds. All e-money issuance and safeguarding is performed by the licensed EMI partners in Tagada's network. Merchants retain full visibility of which licensed entity is handling their funds at each step through Tagada's transaction metadata.