The Markets in Crypto-Assets Regulation entered full force on 30 December 2024. Article 60 lists the activities that require Crypto-Asset Service Provider (CASP) authorisation in the EU. The two that matter for agent-commerce settlement are exchange of crypto-assets for funds (the USDC-to-EUR swap) and custody and administration of crypto-assets on behalf of clients (holding USDC for a customer, even briefly).
Anyone executing those activities on behalf of EU clients needs to be authorised, full stop. That said, the regulation does not require the customer-facing API vendor to be the licensed entity — it requires that somebody in the settlement chain is licensed for each regulated activity. This is the basis for the technical-service-provider model.
Model 1: CASP-licensed vendor. The vendor itself holds the Article 60 authorisation, custodies customer USDC, executes the swap on its own book, and pays EUR from its own balance sheet. Examples: Bitstamp, Kraken EU, larger exchanges. Pros: single counterparty, single audit trail. Cons: 12-24 months and EUR 150k+ to obtain authorisation; ongoing capital, governance and reporting burden.
Model 2: Technical service provider (TSP) behind licensed partners. The vendor never custodies customer funds. The customer-facing API orchestrates the flow but the actual swap and EUR payout are executed atomically by a licensed European payment partner on the partner's book. AsterPay is one example; many agent-commerce-native rails follow this pattern. Pros: ship in months not years, regulated perimeter is the partner's responsibility. Cons: need a robust partner contract, and the TSP must publicly disclose the model so customers know which entity holds the licence (partner names are typically disclosed to onboarded customers under partnership-only disclosure terms rather than on a public marketing page).
Both models are MiCA-aligned. Both are routinely used by European fintechs in production today. The choice between them is a build-vs-buy question, not a legal question.
AsterPay does not hold a CASP licence in its own name and is not pursuing a CASP application. This is a deliberate commercial choice: the partner-routed model lets AsterPay ship a faster, cheaper, multi-currency rail than any single-CASP setup could, while keeping every actual money-movement event on a regulated entity's books.
No. MiCA-compliant implies the speaker holds the licence and meets every obligation in their own name. MiCA-aligned is the honest phrase for a technical service provider routing through licensed partners. If a vendor calls itself "MiCA-compliant" without naming the entity that holds the licence, walk away — either they hold one and should be naming it, or they don't and the claim is misleading. AsterPay says "MiCA-aligned via licensed European payment and crypto-asset partners" precisely because that is the accurate description.
Most agent commerce today is settled in stablecoins because the on-chain transfer is fast and the agent doesn't have a bank account. But the merchant on the other end almost always wants EUR, USD or GBP — not USDC. The settlement layer is the bridge. Picking a MiCA-aligned bridge means your agent commerce stack survives the next round of EU enforcement actions, your finance team gets clean fiat-denominated journal entries, and your VAT calculations are not subject to FX drift between receipt and conversion.
The TSP-behind-licensed-partners model is what makes agent commerce shippable in the EU today. Without it, every agent-commerce vendor would need to either spend two years getting its own CASP licence or move out of the EU. Neither is good for European builders, and neither is required by MiCA.