Electronic Money Token Issuance

Skip key takeaways

Key takeaways: electronic money token issuance 5

Updated August 4, 2026

Which parts of an e-money token's path MiCA actually specifies, where it specifies nothing at all and why the backing model is a parameter rather than a fixed property.

• Whether an e-money token is backed by safeguarded funds or by a reserve of assets is a conditional that turns on significance or on supervisory direction, so the backing model is a parameter and not a fixed property By default funds received sit under the safeguarding regime, but a significant token moves onto the reserve of assets regime instead, and a supervisor can move even a non significant token onto that same regime without any threshold being crossed. Whether the default safeguarding rule reaches a credit institution issuer at all is left open, since the provision it depends on is addressed to electronic money institutions.
• The mint trigger is receipt of funds while the safeguarding clock runs from issuance, so a conformant issuer holds live tokens against funds that are not yet required to be placed A token is minted at par value only once funds are received, which rules out striking supply against a mere promise of funds. Receipt of funds and issuance of the token are measured by two different clocks, and neither clock is treated as tighter than the other.
• Article 54(a)'s 30 percent measures funds received and binds the issuer, and Article 36(4)(d)'s 30 percent measures the amount referenced per official currency and binds the EBA's discretion The two rules share a numeral but nothing else, since one applies directly to the issuer's own funds received while the other sets a floor on a technical standard the regulator has discretion to write. Confusing the two denominators would misstate what either provision actually requires an issuer to hold.
• Redemption ships with a fee switch, a per-working-day cap and a suspension that a competent authority can throw without the issuer's agreement, even though the steady state is free and unlimited In the steady state redemption is available at any time, at par and free of charge, but that state is defeasible three separate ways: through the issuer's own recovery plan, through a supervisor compelling that plan's measures and through a supervisor suspending redemption directly. Exactly how long settlement is allowed to take once a request is accepted is left as an open question rather than a stated number.
• MiCA never uses the words burn, destroy or extinguish, so the supply-reduction step is built from the reserve matching rule and declared in the issuer's own stabilisation policy What the regulation does specify is reserve side accounting: issuance and redemption must always be matched by a corresponding change in the reserve, and the reserve's value must at least equal the claims of token holders in circulation. What happens to a token once it is redeemed is not stated, only what must happen to the reserve when redemption occurs.

Copy takeaways

If you are building an e-money token issuance path, we can help you design a system that switches between the backing regimes instead of one that has to be rebuilt when significance status changes.

See our MiCA compliance services

Electronic money token issuance reads as a token problem and builds as a balance sheet problem, because the euro at the center of it changes legal character several times without ever changing amount. You have decided to issue, you hold or are buying the license, and what remains is the path a single euro takes from a customer's bank transfer to a published audit result. Regulation (EU) 2023/1114 states that path as accounting outcomes and almost never as a mechanism, which is why a summary of it reads clean and a build against it does not. Sections below follow one euro through the gate, the regime fork, the mint, placement, circulation, the redemption request, the supply side and attestation, naming the two stations where the text prescribes no mechanism at all.

In short: An electronic money token is issued at par value and on the receipt of funds, so there is no minting against a promise of funds. Whether the backing sits in safeguarded funds or in a reserve of assets is a conditional turning on significance or on supervisory direction, not a fixed property of the instrument. Article 54 requires at least 30 percent of the funds received to sit always in separate accounts in credit institutions, and that measure is not the other 30 percent circulating summaries quote. Redemption is free, at par and available at any time in the steady state, and that steady state is defeasible by the issuer's own recovery plan, by supervisory compulsion to execute it and by direct supervisory suspension. The words burn, destroy and extinguish do not appear in the Official Journal English text of the Regulation, so the supply reduction step is built from the reserve accounting rules and from the issuer's own declared procedure.

Before the euro arrives: two licences and 40 working days

Nothing moves until two documents exist. Article 48(1) forbids any person to offer an electronic money token to the public or seek its admission to trading in the Union unless that person is the issuer and both "is authorised as a credit institution or as an electronic money institution" and has notified a crypto asset white paper to the competent authority and published it under Article 51. A recital names both routes by their instruments and confirms the electronic money directive applies "unless specified otherwise in this Regulation"; it is cited without a number, because none was visible in the retrieved text. Article 48(2) then decides what kind of engineering problem follows: "E-money tokens shall be deemed to be electronic money." That deeming makes the walk below an e-money problem first and a token problem second, and it is where this article stops, since what an e-money token is under MiCA is treated separately.

At least 40 working days before the intended offer or admission to trading, the issuer notifies its competent authority of that intention, and where Article 48(4) or (5) applies it draws up a white paper and notifies it under Article 51; both locators were assigned from position in our source rather than from a visible article label and stay flagged. Distribution inherits obligations too. With the issuer's written consent another person may offer the token and is then bound by Articles 50 and 53, so Article 53(2)'s requirement that marketing communications carry "a clear and unambiguous statement that the holders of the e-money token have a right of redemption against the issuer at any time and at par value" travels with the distributor, as does Article 53(6)'s ban on dissemination before the white paper is published.

Licensing lead time in our own record is 7 months, across 4 banking platform builds between 2012 and 2026. That is delivery data rather than a statement of law, and it puts the notice period in proportion: 40 working days is the shortest clock in a sequence measured in quarters, a publication gate and not a licensing timeline.

Where the euro lands is a conditional, not a rule

The default is safeguarding, and Article 54 says so in its own heading

Article 54 is the Title IV provision addressing the money, headed "Investment of funds received in exchange for e-money tokens", whose chapeau reads "Funds received by issuers of e-money tokens in exchange for e-money tokens and safeguarded in accordance with Article 7(1) of Directive 2009/110/EC shall comply with the following". The named mechanism is safeguarding under the electronic money directive, and the phrase "reserve of assets" does not occur in it. That phrase belongs elsewhere: Article 36(1) reads "Issuers of asset-referenced tokens shall constitute and at all times maintain a reserve of assets", it sits in Chapter 3 of Title III, that chapter is headed "Reserve of assets" and the title above it is headed "ASSET-REFERENCED TOKENS".

The substitution, and who can trigger it

So far so clean, and both clean statements are false. Article 58(1)(a) subjects electronic money institutions issuing significant tokens to "the requirements referred to in Articles 36, 37, 38 and Article 45, (1) to (4) of this Regulation, instead of Article 7 of Directive 2009/110/EC", with the comma reproduced as the Official Journal prints it. The operative words are "instead of", so significance substitutes one regime for another rather than adding to it. Article 58(2) then lets a home competent authority require an electronic money institution issuing tokens that are not significant to comply with any requirement referred to in paragraph 1, to address liquidity risks, operational risks or risks arising from non compliance with reserve management requirements. A non significant issuer can therefore be moved onto the reserve regime with no threshold crossed. Neither absolute survives that pair; only the conditional does, which makes the backing model a live architectural fork rather than a footnote.

Why the confusion has a mechanical cause

The merge is not careless reading alone. Article 54(b) cross refers into Article 38(1) for its investment quality standard, and Article 38 carries the heading "Investment of the reserve of assets" over a paragraph 1 addressed to issuers of asset referenced tokens. Follow the reference and you land inside the reserve chapter while still reading an electronic money token rule.

One addressee question the text does not answer

Article 58 is addressed to electronic money institutions. Its heading is license neutral, "Specific additional obligations for issuers of e-money tokens", while paragraph 1 opens "Electronic money institutions issuing significant e-money tokens shall be subject to:" and paragraph 2 addresses the same institutions issuing tokens that are not significant. Paragraph 3 addresses tokens denominated in a currency that is not an official currency of a Member State, not issuers, and the article ends there. MiCA plainly contemplates credit institution issuers, at Article 48(1)(a) and at Article 57(1), and Annex VI is headed for issuers of significant e-money tokens without limiting license type. What Article 58 does to a credit institution issuing a significant token is not stated in its text, and this article stops there. The same license type problem leaves open whether Article 54 reaches a credit institution issuer, since Article 54 conditions on funds safeguarded under a directive provision addressed to electronic money institutions.

The token is minted on receipt, and the funds are not placed yet

Article 49(3) is the mint gate, and it carries two operative conditions in one line: "Issuers of e-money tokens shall issue e-money tokens at par value and on the receipt of funds." The price is par, the trigger is receipt, and there is no pre minting against a promise of funds, which rules out striking supply ahead of a settlement window. Article 49(2) gives the holder a claim against the issuer, and Article 49(1) makes this article the whole rule for the subject: "By way of derogation from Article 11 of Directive 2009/110/EC, in respect of the issuance and redeemability of e-money tokens only the requirements set out in this Article shall apply". Teams arriving from a payments product will recognize the resulting ledger shape from neobank stablecoin rails.

The interval between mint and placement

Directive 2009/110/EC requires at Article 7(1) that "In any event, such funds shall be safeguarded by no later than five business days, as defined in point 27 of Article 4 of that Directive, after the issuance of electronic money", quoted as printed with its cross reference to the repealed Directive 2007/64/EC intact. The destination article printed in that chain measures something else, requiring funds not yet delivered or transferred "by the end of the business day following the day when the funds have been received" to be deposited in a separate account in a credit institution or invested in secure, liquid low risk assets. Those are different intervals between different events, and neither is called tighter than the other here. The live destination is Article 10(1) of Directive (EU) 2015/2366 as amended by Regulation (EU) 2024/886 with effect from 8 April 2024, and that inbound clock is worked through in e-money safeguarding reconciliation. So the mint path carries a real window rather than a presentation choice: the token exists from receipt, and the funds have an outer limit measured from issuance. On significance the window changes instrument rather than disappearing, because Article 37(3) requires that "The reserve assets shall be held in custody by no later than five working days after the date of issuance".

Placement: 30 percent of funds received, always, in credit institutions

Under the default regime the composition rule is two points doing different work. Article 54(a) requires that "at least 30 % of the funds received is always deposited in separate accounts in credit institutions". The base is the funds received and the timing qualifier is "always", which is neither an average nor a period end test, so a control measuring the ratio nightly and reporting a monthly mean has not measured what the provision states. Article 54(b) sends the remainder into "secure, low-risk assets that qualify as highly liquid financial instruments with minimal market risk, credit risk and concentration risk, in accordance with Article 38(1) of this Regulation, and are denominated in the same official currency as the one referenced by the e-money token". That closing clause is a hard treasury constraint: a euro referenced token cannot be funded with dollar instruments.

The other 30 percent, and it is not this one

A second 30 percent circulates in commentary and belongs to a different regime. Article 36(4), second subparagraph, point (d) requires a technical standard to specify "the minimum amounts in each official currency referenced to be held as deposits in credit institutions, which cannot be lower than 30 % of the amount referenced in each official currency". Base: the amount referenced per official currency. Addressee: the European Banking Authority's discretion in drafting that standard, not the issuer directly. Article 45(7)(b) lifts the same referenced amount base to a floor of 60 percent for significant tokens. Same numeral, different denominators, different regimes, different addressees.

What that standard sets is not stated here, because the adopted delegated act was not read for this article. Article 36(4) describes only its own subject matter: percentages of the reserve by daily and weekly maturities, including reverse repurchase agreements terminable on one working day notice and on five working day notice, cash withdrawable on the same notice periods, other maturities and overall liquidity management techniques.

On significance the euro changes regime, not just paperwork

What arrives with the substitution

Article 36 brings two distinct segregations. The reserve is legally segregated from the issuer's estate and from the reserve of other tokens so that creditors "have no recourse to the reserve of assets, in particular in the event of insolvency", and it is operationally segregated as well. Paragraph 1(b) requires the reserve to be managed so that "the liquidity risks associated to the permanent rights of redemption of the holders are addressed". Paragraph 5 forbids a commingled treasury across products: an issuer offering two or more tokens operates segregated pools per token, each managed separately, and where different issuers offer the same token they operate only one reserve for it. Article 37 adds custody, requiring reserve assets to be unencumbered and not pledged as a financial collateral arrangement, held so the issuer has "prompt access to the reserve assets to meet any requests for redemption", with custodian concentration and asset concentration avoided as two separate rules.

Four behavioural obligations arrive with Article 45(1) to (4), and paragraph 2 has the sharpest product consequence: the token must be capable of being held in custody by different unaffiliated crypto asset service providers "on a fair, reasonable and non-discriminatory basis", which forecloses a single custodian architecture at design time. Beside it sit a remuneration policy that does not create incentives to relax risk standards, a liquidity management policy delivering a resilient liquidity profile including under stress, and regular liquidity stress testing. Paragraph 4 closes with a cross reference worth quoting exactly as printed: "Depending on the outcome of such tests, EBA may decide to strengthen the liquidity requirements referred to in paragraph 7, first subparagraph, point (b), of this Article and in Article 36(6)." Article 36(6) contains no liquidity requirement; it is the matching provision. The reference reads as a numbering slip and is left as printed rather than repaired.

Own funds move too

Capital moves on the same trigger. Article 58(1)(b) applies Article 35(2), (3) and (5) and Article 45(5) instead of Article 5 of Directive 2009/110/EC. Own funds sit, under Article 35(1), at the highest of EUR 350 000, 2 percent of the average amount of the reserve of assets, or a quarter of the preceding year's fixed overheads, and Article 45(5) lifts that middle percentage to 3 percent on significance while the other two limbs stand. Article 35(2) points the quality of those funds at the Common Equity Tier 1 items and instruments of Articles 26 to 30 of Regulation (EU) No 575/2013.

How a token becomes significant

Article 43(1) supplies the criteria: more than 10 million holders, a value, market capitalisation or reserve size above EUR 5 000 000 000, average daily transactions "higher than 2,5 million transactions and EUR 500 000 000 respectively" as the primary text conjunctively prints it, and designation of the issuer as a gatekeeper under Regulation (EU) 2022/1925. An issuer may also volunteer, showing through a detailed programme of operations that it is likely to meet at least three of them, under a provision whose article number our source assigned from an internal cross reference and which stays flagged as such.

In circulation the euro earns nothing, and nothing is defined widely

The prohibition is stated plainly at Article 50(1), overriding the directive it displaces: "Notwithstanding Article 12 of Directive 2009/110/EC, issuers of e-money tokens shall not grant interest in relation to e-money tokens." Paragraph 2 extends it down the distribution chain, so a crypto asset service provider may not grant interest when providing services related to the token and an exchange cannot pay yield on a balance.

Paragraph 3 is what actually shapes a product roadmap. Any remuneration or benefit related to the length of time a holder holds the token counts as interest, and the definition continues: "That includes net compensation or discounts, with an effect equivalent to that of interest received by the holder of the e-money token, directly from the issuer or from third parties, and directly associated to the e-money token or from the remuneration or pricing of other products." Read the last clause slowly. It reaches a fee rebate on a different product, a loyalty credit funded by a partner and a cross subsidised reward keyed to holding time, whoever pays it, so a rewards design that never says yield can still land inside the definition. Recital 68 goes wider, extending the rationale to "interest not related to the length of time that such holders hold those e-money tokens", but the time keyed operative text controls and the recital is noted rather than relied on.

The redemption right is unconditional, the redemption path is not

What the right actually says

On request, Article 49(4) requires the issuer to redeem "at any time and at par value, by paying in funds, other than electronic money, the monetary value of the e-money token held to the holder". The middle clause is the one that surprises integrators: settling by handing over more electronic money does not discharge the obligation, so paying out in another stablecoin is not redemption, which is worth testing against the settlement assumptions in stablecoin payment gateway integration. Article 49(5) puts the conditions for redemption prominently in the white paper, at Article 51(1), first subparagraph, point (d), and what that point requires is not described here, because it was never retrieved.

The carve out and what fills it

Article 49(6) is quoted everywhere and usually quoted short: "Without prejudice to Article 46, the redemption of e-money tokens shall not be subject to a fee." The opening clause is load bearing, and Article 55 is what gives it content: "Title III, Chapter 6 shall apply mutatis mutandis to issuers of e-money tokens." That sentence names a chapter rather than selected articles, so its reach is Articles 46 and 47 entire. Its addressee is issuers of electronic money tokens without qualification, so it turns on neither significance nor license type. And it is unconditional, so the recovery plan obligation lands on every issuer from the start.

Inside that chapter, Article 46(1) has three subparagraphs and the first two are obligations in their own right, covering restoration of compliance with the reserve requirements and preservation of the issuer's services, timely recovery of operations and fulfilment of obligations "in the case of events that pose a significant risk of disrupting operations". The third subparagraph reaches the redemption path. The plan "shall include appropriate conditions and procedures to ensure the timely implementation of recovery actions as well as a wide range of recovery options, including: (a) liquidity fees on redemptions; (b) limits on the amount of the asset-referenced token that can be redeemed on any working day; (c) suspension of redemptions." The Regulation supplies its own citation form for that list at Annex VI point 38, as the third subparagraph, points (a), (b) and (c), of that paragraph. Note the word "including": the three are a floor rather than a menu.

Three routes to a halted redemption

The first route is the issuer executing its own plan. The second is Article 46(3), which gives the competent authority power to require the issuer to implement one or more of the arrangements or measures set out in the recovery plan, or to update the plan and implement the updated measures within a specific timeframe, where the issuer fails to comply with the reserve requirements or, "due to a rapidly deteriorating financial condition, is likely in the near future to not comply" with them. That trigger is forward looking, so the switch can be thrown before anything has broken. The third bypasses the plan altogether: under Article 46(4) the authority may temporarily suspend redemption directly, in the same circumstances, where justified having regard to the interests of holders and financial stability.

This engineering consequence is ours rather than the Regulation's, and it follows directly. The redemption path ships with a fee switch, a per working day cap and a kill switch even though the steady state is free and unlimited, and the kill switch has to be operable on external instruction rather than only on an internal decision. Our own delivery record supplies the failure mode: the most frequent catch in our Production Readiness Reviews, applied before roughly 19 launches and migrations, is an operational gap rather than a code defect, and the canonical example is a backup with no proven restore. A suspension switch nobody has exercised is that same defect class, with the added problem that the person exercising it may not work for you. What the plan itself looks like is not described here, because Article 46(6) delegates its format and contents to guidelines that were not read.

The latency question, unresolved

Settlement latency is where the text runs out. Four candidate provisions were checked against the complete Regulation and all four are qualitative: Article 37(1)(c) on prompt access to the reserve assets, Article 36(1)(b) on the liquidity risks of permanent redemption rights, Article 45(3) on a resilient liquidity profile and Article 47(2) on holders being "paid in a timely manner" under the redemption plan. On its face Article 49(4)'s "at any time" governs the availability of the right rather than the latency of settlement, and the number is pushed into the issuer's own declared conditions. That is a reading rather than a finding, and it is not a claim that no numeric deadline exists anywhere. One could sit in Directive 2009/110/EC as nationally transposed, in Directive (EU) 2015/2366 or in a supervisory guideline, none of which were read for this article.

Burn is an accounting consequence, and the word is not in the text

Start with the lexical result and with the terms that make it checkable. The complete Official Journal English text of Regulation (EU) 2023/1114, all 167 PDF pages covering printed pages L 150/40 to L 150/205, was searched case insensitively for "burn", "burnt", "burned", "destro" catching destroy, destroyed and destruction, "extinguish", "cancel", "taken out of circulation", "withdrawn from circulation", "no longer in", "outstanding e-money", "amount of e-money tokens", "reduction in", "supply of", "in circulation", "units of the" and "decrease in the reserve". Eleven returned nothing bearing on token destruction; every hit on "cancel" concerns a cancelled offer, an insurance notice period, order cancellation or insider dealing, and every hit on "supply of" concerns algorithmic crypto assets in a recital or the market manipulation definitions. That is a statement about a search of the complete text. It is not a finding that MiCA imposes no supply reduction obligation.

What the Regulation does carry is reserve side accounting. Article 36(6) requires issuers to ensure "that the issuance and redemption of asset-referenced tokens is always matched by a corresponding increase or decrease in the reserve of assets". The reserve's aggregate value must, under Article 36(7), be "at least equal to the aggregate value of the claims against the issuer from the holders of the asset-referenced token in circulation", which keeps circulating supply distinct from issued supply without ever saying how a token leaves circulation. Article 36(8)(d) requires the stabilisation policy to "describe the procedure by which the asset-referenced tokens are issued and redeemed, and the procedure by which such issuance and redemption will result in a corresponding increase and decrease in the reserve of assets", and point (g) requires a list of who is entitled to redeem against the reserve. Those ask for a description of the issuer's own procedure. MiCA's text does not prescribe the mechanism, and Annex VI points 13 and 14 make the matching rule and the coverage rule enforceable in exactly those reserve side terms.

A reach limit finishes the station honestly. All three provisions above are asset referenced token provisions and arrive at an electronic money token issuer only through Article 58(1)(a) on significance or Article 58(2) by supervisory direction. For a non significant token with no direction in place, this article can cite nothing at all on the supply side, and the mechanism you build is declared in your own stabilisation policy rather than derived from a rule.

Attestation: six months, six weeks, two weeks

The walk ends at a published number. Article 36(9) requires issuers to "mandate an independent audit of the reserve of assets every six months, assessing compliance with the rules of this Chapter", fixing three things at once: the frequency is six monthly, the subject matter is the reserve rather than the financial statements, and the standard is compliance with Title III Chapter 3. Article 36(10) supplies the clock. Results go to the competent authority without delay and "at the latest within six weeks of the reference date of the valuation", then the result is published "within two weeks of the date of notification". Four grounds let the authority instruct a delay, two of them being the issuer having been required to implement recovery measures under Article 46(3) or a redemption plan under Article 47, which wires the attestation pipeline into the machinery of the previous section. An issuer in recovery can be told to withhold the result.

The mechanism correction

Both provisions reach issuers of significant electronic money tokens through Article 58(1), whose second subparagraph reads: "By way of derogation from Article 36(9), the independent audit shall, in respect of issuers of significant e-money tokens, be mandated every six months as of the date of the decision to classify the e-money tokens as significant pursuant to Article 56 or 57, as applicable." A secondary account attributes the six monthly cadence itself to that derogation. Right on effect, wrong on mechanism. Article 36(9) already says every six months on its own terms, and the derogation moves only the start date, from the asset referenced token trigger events of authorisation or white paper approval to the significance decision, because those trigger events do not exist for this issuer.

What the reserve audit does not discharge

Two audits run, not one. Article 34(12) separately requires the issuer to be regularly audited by independent auditors, at an unspecified cadence, with results communicated to the management body and made available to the competent authority, and the "Without prejudice to Article 34(12)" opening Article 36(9) is what keeps them apart. A drafting artefact sits nearby and is noted rather than resolved: Annex VI point 16 anchors the same six monthly audit to the date of the offer to the public or admission to trading, where Article 58(1) anchors it to the significance decision. The operative date is Article 58(1)'s, Annex VI is a list of infringements, and this article does not choose between them.

On publication the fence is narrow. Article 30 is not among the articles Article 58(1)(a) imports, and the audit result is published for a significant token through Article 36(10), which is imported, with Annex VI point 17 enforcing it and naming the European Banking Authority as recipient. Whether the fuller Article 30(2) duty, the full and unredacted audit report plus a plain language summary, reaches an electronic money token issuer by some other route is unestablished, and nothing here should be read as putting that issuer outside Article 30.

Building an issuance path against a conditional

Everything from here is our engineering view, with every regulatory statement behind it cited above. The first design decision is neither the chain nor the custody stack. It is to treat the backing model as a parameter, because a platform that hard codes the safeguarding path has to be rebuilt if its token is classified significant or if a supervisor directs it onto the same regime. Type inbound receipts by legal basis at ingestion so each population carries its own clock, its own alarm and its own evidence, since a blended ageing report hides the day one population genuinely needs the longer window. Build the fee switch, the per working day cap and the suspension path while nobody is asking for them, then exercise the suspension path on a schedule the way you would exercise a restore. And write the mint and redeem procedure down in detail, because a description of that procedure is what the stabilisation policy asks for.

One figure from our own delivery record sets the budget expectation, and it is ours rather than a market number. Across 8 real world asset and tokenization platforms delivered between 2020 and 2026, 52 percent of effort went to compliance rather than to token and contract code, and legal wrapper plus transfer agent logic outweighed token code by roughly 2 to 1. On an issuance build the mint and burn code is the small half. The regime fork, the receipt typing and the attestation pipeline sit in the large half, which is MiCA compliance software development work rather than smart contract work, delivered the same way as the rest of our FinTech development services.

How Pharos Production helps

Pharos Production builds the issuance path as a parameterised system rather than a single regime: a backing model switchable between safeguarded funds and a reserve of assets without a rewrite, receipt typing by legal basis with a clock per type, a redemption path carrying its fee switch, its per working day cap and an externally operable suspension, supply accounting that ties every mint and redeem to a reserve movement, and an attestation pipeline built to the six weeks and two weeks clock. We write the mint and redeem procedure as a deliverable, because that document is what the stabilisation policy asks for and what survives contact with a supervisor. Where the work is the wider compliance surface rather than the issuance path alone, it is MiCA compliance software development.

Sources: Regulation (EU) 2023/1114 (MiCA), CELEX 32023R1114, complete Official Journal English text, OJ L 150 of 9.6.2023, printed pages L 150/40 to L 150/205: Articles 30 and 34(12) at L 150/89 and L 150/92, Articles 35 to 38 at L 150/92 to L 150/96, Article 45 at L 150/104, Articles 46 and 47 at L 150/105 and L 150/106, Articles 53, 54 and 55 at L 150/111, Article 58 at L 150/114, Annexes V and VI at L 150/198 and L 150/202 to L 150/205. Articles 48, 49, 50, 43 and 57 from the same Regulation via the EUR-Lex ELI text, with the locators for Article 48(6), Article 48(7) and Article 57(1) assigned from position or from an internal cross reference and flagged as such, and one recital cited without a number because none was visible. Directive 2009/110/EC, CELEX 32009L0110, Articles 5 and 7(1), quoted as printed, so Article 7(1)'s cross reference to the repealed Directive 2007/64/EC stands unmodernised. Directive 2007/64/EC, CELEX 32007L0064, Article 9(1), quoted as the reference actually printed in the operative chain, whose live destination is Article 10(1) of Directive (EU) 2015/2366 as amended by Regulation (EU) 2024/886 with effect from 8 April 2024. The lexical search reported at the supply side station covers the complete MiCA text only. Article 45(4)'s cross reference to Article 36(6) is quoted as printed and not repaired. The station framing, the switch vocabulary, the parameterisation advice and our licensing lead time, Production Readiness Review and delivery effort figures are ours, and they are delivery record rather than market data. This is engineering guidance, not legal advice.

FAQ

Last updated: August 4, 2026 · Reviewed by: Dmytro Nasyrov (Founder and CTO)

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Popular

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 7

• ★ Featured question. Does a MiCA e-money token have a reserve of assets?

  Copy link Copies a direct link to this answer to your clipboard.

  It depends, and both absolute answers are wrong. By default the funds received sit under the safeguarding regime: Article 54 addresses funds received in exchange for e-money tokens and routes them through Article 7(1) of Directive 2009/110/EC.

  But Article 58(1)(a) puts electronic money institutions issuing significant e-money tokens onto Articles 36, 37, 38 and Article 45(1) to (4) instead of Article 7 of that Directive, and Article 58(2) lets a home competent authority impose the same on a non-significant issuer.

• What does MiCA's 30 percent rule actually measure?

  Copy link Copies a direct link to this answer to your clipboard.

  Two different rules share the numeral. Article 54(a) requires at least 30 percent of the funds received to be always deposited in separate accounts in credit institutions, and it binds the issuer directly.

  Article 36(4)(d) sets a floor of 30 percent of the amount referenced in each official currency on what an EBA technical standard may require, inside the reserve-of-assets regime, rising to 60 percent for significant tokens under Article 45(7)(b).

• When is an e-money token minted?

  Copy link Copies a direct link to this answer to your clipboard.

  At par value and on the receipt of funds, under Article 49(3). Both conditions are operative: the price is par and the trigger is receipt, so there is no minting against a promise of funds.

• Can an issuer refuse or delay redemption?

  Copy link Copies a direct link to this answer to your clipboard.

  In the steady state, no: Article 49(4) makes redemption available on request, at any time, at par, paid in funds other than electronic money, and Article 49(6) makes it fee-free. That steady state is defeasible three ways.

  Article 55 applies Title III Chapter 6 to every e-money token issuer, Article 46(1) third subparagraph makes liquidity fees, per-working-day limits and suspension of redemptions mandatory recovery-plan contents, Article 46(3) lets a competent authority compel the plan's measures on a forward-looking trigger and Article 46(4) gives that authority a separate power to suspend redemption directly.

• Can an issuer settle a redemption in another stablecoin?

  Copy link Copies a direct link to this answer to your clipboard.

  No. Article 49(4) requires the issuer to redeem "by paying in funds, other than electronic money", so handing over more electronic money does not discharge the obligation.

• Does MiCA require redeemed e-money tokens to be burned?

  Copy link Copies a direct link to this answer to your clipboard.

  MiCA's text does not prescribe a mechanism. The words burn, destroy and extinguish do not appear in the Official Journal English text of Regulation (EU) 2023/1114, on a case-insensitive search of the complete 167-page text against a named list of sixteen terms.

  What the Regulation does carry is reserve-side accounting: Article 36(6) requires issuance and redemption to be always matched by a corresponding increase or decrease in the reserve, Article 36(7) requires the reserve to cover claims from holders of tokens in circulation, and Article 36(8)(d) requires the stabilisation policy to describe the issue and redeem procedure. Those reach an e-money token issuer only on significance or by supervisory direction.

• How often is the reserve audited, and when is the result published?

  Copy link Copies a direct link to this answer to your clipboard.

  Article 36(9) requires an independent audit of the reserve of assets every six months. Article 36(10) requires notification to the competent authority within six weeks of the reference date of the valuation and publication within two weeks of that notification.

  For a significant e-money token, Article 58(1) second subparagraph runs the six months from the classification decision under Article 56 or 57 rather than from the asset-referenced token trigger dates. The derogation moves the start date; the six-monthly cadence comes from Article 36(9) itself.

I work with startup founders who need a dedicated software development team but don’t want to gamble on hiring, random outsourcing, or opaque delivery.
Most founders face the same problem sooner or later.
Early technical and team decisions lock the product into tech debt, slow delivery, missed milestones and constant re-hiring. By the time this becomes visible, fixing it is already expensive.

As a CTO and software architect, I help founders design, build and run dedicated development teams that work as a true extension of the startup. Not as a black-box vendor.

My focus is on complex products where mistakes are costly:

• Web3 and blockchain platforms
• FinTech and regulated products
• High-load startup systems
• MVP → scale transitions

We don’t do body-shopping.
We don’t sell generic outsourcing.

Instead, we help founders:

• build the right team structure from day one
• keep technical ownership and transparency
• scale delivery without losing control
• avoid vendor lock-in and hidden risks

Teams are aligned with the product roadmap, business goals and long-term architecture. Not just short-term velocity.