Stablecoin payments in Europe: does MiCA authorisation cover PSD2?
MiCA authorisation does not automatically cover every stablecoin payment service. The EBA's 2026 opinion explains the PSD2 overlap and why banking files need an activity-by-activity permissions map.
On 12 February 2026, the European Banking Authority published an opinion on the end of the transition under its no-action letter concerning the interplay between MiCA and PSD2. The transition ended on 2 March 2026. This October briefing revisits that supervisory guidance for European crypto businesses arranging banking or stablecoin settlement; it is not a new October rule.
The core issue is that some services involving electronic money tokens, or EMTs, can also qualify as payment services. MiCA authorisation therefore should not be presented as blanket permission for every payment activity. The relevant question is what the firm actually does with the token, for whom, and under which legal permissions.
Do all stablecoin businesses need a PSD2 licence?
That is not what the opinion says. Its focus is crypto-asset service providers carrying out EMT services that qualify as payment services. Simply using the word stablecoin does not determine the regulatory outcome, and not every token or crypto service has the same classification. A qualified adviser should map the particular activity and confirm the competent authority's treatment.
What did the EBA say about continued operations?
The EBA advised national authorities on conditional continuation for relevant firms awaiting PSD2 authorisation after the transition. Firms that did not meet the conditions were advised to discontinue the affected services. This is supervisory advice, not a blanket extension for every crypto firm, and a pending application should not be described as an approved payment licence. The conditions and national implementation need to be checked for the specific case.
What will a banking partner need to understand?
Prepare a simple flow-of-funds diagram showing the customer, token issuer, crypto provider, conversion counterparty and fiat settlement account. Explain who holds funds, who initiates transfers and whether you act for customers or only manage your company's own treasury. Attach the permissions and relevant agreements supporting each regulated step; do not substitute a licence badge for a description of the actual flow.
Also document source-of-funds checks, customer screening, expected countries and volumes, and how transactions can be reconciled between on-chain records and fiat settlements. These are practical file-preparation points, not new requirements invented by the opinion. A bank may still decline an activity outside its risk appetite even when a permission exists.
Planning stablecoin settlement without a permissions gap
Before launching or changing a payment model, establish which authorised counterparties will perform the regulated activities and which accounts support fiat settlement. Xavion Capital can help assess crypto-business banking fit and coordinate provider introductions around a documented model. Legal classification and authorisation conclusions remain matters for qualified advisers and the relevant supervisory authority.
For an EU-facing crypto business, a clear permissions map is more useful to a banking partner than a broad claim of MiCA compliance. Resolve the payment-service overlap before asking a provider to support the settlement flow.