The grace period is over. On 1 July 2026, MiCA's transitional period ended, and only authorised crypto-asset service providers may now offer crypto-asset services in the EU. Firms still operating under old national registrations had to wind down or move clients to an authorised provider or a self-hosted wallet.
Few made the jump. Only around 210 of the more than 1,200 entities with pre-MiCA national registrations converted to full CASP authorisation, roughly 17%.
For teams planning crypto wallet app development for European users, the rules are no longer a future concern. They decide the architecture. Who holds the keys, how transfers are logged and how a wallet proves ownership to an exchange all trace back to two regulations: MiCA and the EU Transfer of Funds Regulation, better known as the Travel Rule.
Does MiCA Regulate Crypto Wallets?
MiCA regulates crypto-asset service providers, not individual users or the software they run. A custodial wallet, where the provider holds or controls user keys, counts as a custody service and needs CASP authorisation. A self-custody wallet, where only the user controls the keys, generally falls outside MiCA.
The grey areas sit between those two poles. An MPC wallet where the provider holds one key share, or a recovery service that can restore access without the user, may give the provider enough control to count as custody. That classification depends on the key design, so it has to be settled before development starts. A business building a crypto wallet should get a legal view on its key model before writing any code.
What Does the Travel Rule Require From Crypto Wallets?
The Travel Rule requires CASPs to send identifying information about the sender and recipient with every crypto transfer between providers, regardless of value. For transfers to or from self-hosted wallets, the obligations change.
A CASP must collect and hold originator and beneficiary information for transfers involving self-hosted addresses. Above €1,000, it must assess whether its own customer owns or controls that address.
How Wallet Ownership Gets Verified
The European Banking Authority's guidance allows a CASP to confirm ownership by having the customer sign a specific message with the key for that address. Other common methods include a small test deposit, known as a Satoshi test, and the AOPP signature protocol.
This matters for self-custody wallets as well. An exchange user withdrawing to a personal wallet may be asked to prove ownership. A wallet that supports message signing and standard ownership proofs makes that step painless. A wallet that doesn't forces users into slower checks or failed withdrawals.
How Do MiCA and the Travel Rule Change Wallet Architecture?
Compliance requirements now shape five parts of a wallet build. Each one is cheaper to design in than to retrofit.
Map Every Transfer Flow
Compliance teams should classify each flow where customer assets move as internal, CASP-to-CASP or CASP-to-self-hosted. Each type carries different data and verification duties. A wallet product that can't tell these apart at the transaction level can't apply the right rules.
Identify the Counterparty
Before sending, a custodial wallet needs to know whether the destination belongs to another CASP or a self-hosted wallet. That requires integration with a Travel Rule messaging network and an address attribution service.
Screen at Withdrawal
Onboarding checks aren't enough. Sanctions and risk screening should run at the moment of transfer, against the destination address and, where possible, its transaction history.
Keep Auditable Records
Travel Rule data, ownership proofs and screening results must be stored and retrievable for supervisors. The data model should link each record to the specific transaction it covers.
Configure by Jurisdiction
Thresholds differ outside the EU. The UK applies its own regime, and Switzerland generally requires ownership checks without a threshold. Rules should live in configuration, so the wallet can change behaviour per market without a code release.
What Compliance Changes Are Coming Next for Crypto Wallets?
The current rules aren't final. Three developments deserve a place on any wallet roadmap.
The Travel Rule regulation required the European Commission to report on risks linked to self-hosted wallets by mid-2026. Its findings could tighten obligations around self-custody transfers.
The Commission also opened a targeted consultation on reviewing MiCA, with replies due by 31 August 2026. Changes to custody definitions would directly affect how hybrid and MPC wallets are classified.
The EU Anti-Money Laundering Regulation applies from July 2027. It bans CASPs from offering anonymous accounts and from handling privacy-focused coins, which will narrow the assets a regulated wallet can support.
A wallet built with configurable compliance rules will absorb these changes with far less disruption than one with rules hard-coded into transfer logic.
Where Do Automation and Agentic AI Fit in Wallet Compliance?
In 2026, AI agents increasingly initiate transfers for businesses and users, and the Travel Rule applies to them in full. An agent sending funds from a custodial wallet still triggers data collection, screening and, above €1,000 to a self-hosted address, ownership checks.
Wallet teams should design agent permissions with compliance built in. That means restricting agents to pre-verified destination addresses, capping transfer sizes and logging each action against the human or business that authorised it.
Automation also reduces the manual load on compliance teams. AI-assisted screening can triage alerts, group related transactions and draft case notes for review. Final decisions on blocked or flagged transfers should stay with trained staff.
What Should Teams Ask a Crypto Wallet Development Company?
A wallet development company working on EU products should treat compliance as part of the architecture. These questions help separate experienced teams from feature-list vendors.
Questions to ask before hiring:
How will the key design affect whether the wallet counts as a custody service under MiCA?
Which Travel Rule networks and address attribution services can the wallet integrate with?
Does the wallet support message signing and standard ownership proofs for self-hosted addresses?
How are compliance thresholds configured per jurisdiction?
How are AI agent transfers permissioned and logged for audit?
Teams comparing wallet development services or a wallet consulting service can use this list to test proposals, and the cryptocurrency wallet development company page shows how custody models, compliance integrations and security reviews are typically scoped into a wallet build.
Frequently Asked Questions
Do self-custody wallets need a MiCA licence?
Self-custody wallet software generally doesn't need a MiCA licence, because the provider never controls user assets. Wallets where the provider holds keys or key shares may count as a custody service and require CASP authorisation.
What is the Travel Rule threshold for self-hosted wallets in the EU?
CASPs must collect sender and recipient information for all transfers involving self-hosted wallets. Above €1,000, they must also verify that their customer owns or controls the self-hosted address.
How can a user prove they own a self-hosted wallet?
The most common methods are signing a specific message with the wallet's private key, sending a small test deposit, or using the AOPP protocol. Wallets that support message signing make this step faster.
Did the MiCA transitional period end?
Yes. The transitional period ended across the EU on 1 July 2026. Providers without CASP authorisation can no longer serve EU clients.
Does the Travel Rule apply to transfers made by AI agents?
Yes. The Travel Rule applies to the transfer, regardless of whether a person or software initiated it. Custodial wallets must collect the same data and run the same checks for agent-initiated transfers.
Conclusion
MiCA and the Travel Rule have moved from preparation to enforcement, and crypto wallets built for European users now carry compliance in their architecture. Key design determines regulatory status, transfer flows determine reporting duties, and configurable rules determine how well a wallet copes with the 2027 changes ahead. For teams planning a compliant wallet build, Codezeros works on crypto wallet app development where custody models and Travel Rule integrations are scoped from the first design session. Contact us today to review your wallet's compliance architecture.