In short
The GENIUS Act and MiCA both require full reserve backing for payment stablecoins and e-money tokens, but differ on permitted reserve assets, custody arrangements, reporting cadence and supervisory reporting. A dual jurisdiction issuer should run one reconciliation and evidence layer, with regime specific eligibility and reporting applied on top.
Where the two regimes agree
Both frameworks start from the same premise. A token presented as redeemable at par for a fiat currency must be backed by reserves at least equal to the outstanding liability, held separately from the issuer's own assets and available to meet redemption.
Both restrict reserves to conservative, liquid instruments rather than allowing the issuer to invest for yield at its discretion. Both require regular disclosure of reserve composition. Both impose redemption obligations at par.
Both also treat the reserve as client property in substance, meaning that segregation and insolvency remoteness are central rather than incidental.
The consequence is that the underlying operational control, continuous reconciliation of outstanding supply against segregated reserve holdings, is identical in both jurisdictions.
Where they diverge, and why it matters operationally
The divergences are in the detail that determines daily operation. Permitted reserve asset categories differ, so an instrument eligible in one regime may be ineligible or subject to a concentration limit in the other.
Custody and placement requirements differ, with MiCA placing specific expectations on where reserve assets sit and how they are safeguarded for e-money tokens, and the US framework specifying its own permitted arrangements.
Reporting cadence and content differ, as do the parties to whom reporting is made and the form of external examination or audit required.
The practical result is that an issuer serving both markets cannot simply apply the stricter rule everywhere, because strictness is not a single dimension. A reserve mix optimised for one regime can breach a concentration or eligibility rule in the other.
One reconciliation layer, two regulatory overlays
The design that works is a single continuous reconciliation of supply against reserves, with regime specific eligibility, concentration and reporting logic applied as overlays on the same underlying position.
Running two separate compliance stacks produces two versions of the truth, and the reconciliation between them becomes an additional control with its own failure modes. It also doubles the evidential burden without improving the evidence.
Safeheld reconciles issuance, on-chain supply, treasury positions and reserve custody balances once, and evaluates the resulting position against each regime's eligibility and reporting requirements separately.
That produces one operational record, two compliant reporting outputs and a single audit trail that both supervisors can test.
Segmenting supply and reserves by regime
Where an issuer operates distinct legal entities for each jurisdiction, supply and reserves must be attributed correctly to each. A token minted by the EU entity is not backed by reserves held by the US entity, notwithstanding that the two are economically related.
This attribution is easy to state and difficult to maintain, because tokens circulate freely once issued and holders do not respect entity boundaries. Bridging and secondary market movement can create positions where economic exposure and legal issuance are not aligned.
Reconciliation must therefore track issuance by entity, redemption by entity and reserve holdings by entity, and prove coverage separately at each level rather than in aggregate.
Aggregate coverage across a group is not a defence to a shortfall in one regulated entity, and a supervisor will test the entity, not the group.
Producing two reporting sets from one record
Reporting to a national competent authority under MiCA and to US supervisors and the public under the GENIUS Act differ in format, frequency, granularity and certification requirements.
Where both are generated from the same sealed reconciliation runs, discrepancies between them cannot arise silently, which removes a category of risk that dual jurisdiction issuers otherwise carry permanently.
It also simplifies the position when one supervisor asks about a figure published to the other, which happens more often than issuers expect.
Board and risk committee reporting draws from the same source, so internal governance describes the same position that external reporting describes.
Satisfying two examination regimes with one evidence set
Examination under the GENIUS Act by a registered public accounting firm and supervisory review under MiCA ask overlapping questions about the same underlying facts.
Sealing each reconciliation run under a SHA-256 Merkle root that can be verified independently allows the issuer to present the same primary evidence to both, with each party able to confirm integrity without relying on the issuer's assurance.
That reduces the marginal cost of the second regime substantially. Most of the cost of dual jurisdiction compliance is duplicated evidence production rather than duplicated regulation.
The remaining regime specific work then sits where it should, in eligibility assessment and reporting format, rather than in reconstructing the same facts twice.
Frequently asked questions
Can a dual jurisdiction issuer simply apply the stricter rule everywhere?
No, because strictness is not a single dimension. Permitted reserve asset categories, concentration limits and custody requirements differ in ways that are not nested. A reserve mix optimised for one regime can breach an eligibility or concentration rule in the other, so both rule sets must be evaluated against the same position independently.
Does group level reserve coverage satisfy an entity level shortfall?
No. Supervisors test the regulated entity. Tokens issued by an EU entity are not backed by reserves held by a US affiliate, so issuance, redemption and reserve holdings must be attributed by entity and coverage proved separately at each level rather than in aggregate across the group.
Why run one reconciliation layer instead of two compliance stacks?
Two stacks produce two versions of the truth and require a reconciliation between them, which is an additional control with its own failure modes. One continuous reconciliation with regime specific overlays produces a single operational record, two compliant reporting outputs and one audit trail that both supervisors can test.
What complicates supply attribution across jurisdictions?
Tokens circulate freely once issued and holders do not respect entity boundaries. Bridging and secondary market movement create positions where economic exposure and legal issuance diverge. Reconciliation must therefore track issuance and redemption by entity rather than inferring attribution from where a token currently sits.
Where does most of the cost of dual jurisdiction compliance sit?
In duplicated evidence production rather than duplicated regulation. When both regimes are served from the same sealed reconciliation runs, the marginal cost of the second regime falls to eligibility assessment and reporting format, which is where the genuine regulatory difference lies.