Crypto Acceptance, Euro Settlement
Accept crypto and stablecoin payments at the till, settle the merchant in euro with zero crypto exposure - the terminal fleet never changes.
The full blueprint adds all 9 risks with their controls and owners, the DORA third-party pack and the delivery plan in 4 phases.
Web document · ~13 pages · 17 min read · one link opens all 22 blueprints
- Maturity
- Proven
- Regime
- PSD2 + MiCA
- Proven stack (4 of 5)
- Lyzi · Triple-A · Checkout.com · Coinbase Payments
- Last verified
- August 2026
Reviewed by Ivor Jugo, Offer Owner at Protofire
size of the largest live crypto-acceptance merchant network (Checkout.com x Coinbase Payments), live 2 Jun 2026.
Settled in USD, not euro - the only independently press-corroborated euro-settled reference is Printemps' 20-store network, live since Nov 2024.
01. The opportunity
A merchant that wants to accept crypto-asset payments does not need a crypto licence, a wallet, or exposure to price movement. The acquirer or payment service provider handling the transaction converts the payment to euro and settles it to the merchant's existing bank account exactly as a card transaction would, and the point-of-sale terminal does not change. What changes sits on the acquirer's side of the till: how the payment is authorised, converted and reconciled across three systems that were not built to talk to each other - the terminal, the crypto rail and the euro settlement account.
The pattern reached retail scale in France from November 2024, when Printemps became the first European department-store chain to accept crypto-asset payments, live across 20 French stores. By mid-2026 the same architecture was live at enterprise scale: Checkout.com added stablecoin acceptance for its 1,000-plus merchant network with Coinbase Payments on 2 June 2026, and Fireblocks launched dedicated acceptance infrastructure for payment service providers the same day. For an acquirer or PSP it adds a payment method to merchants it already serves, and gives those merchants a way to take digital-asset payments without holding any crypto themselves.
02. The regulatory position
03. Who's already done this
20 French stores via Binance Pay, converted to euro by Lyzi - the only reference here corroborated by independent press rather than vendor material alone.
Stablecoin acceptance via Triple-A; the 15% revenue / 50% AOV figures are Triple-A's own published case study, not independently audited.
Stablecoin (USDC/USDT) acceptance settled in USD, not euro - evidence for the pattern generally, not the euro-settlement variant.
04. Does this fit you?
- Yes if the goal is adding crypto acceptance to merchants already served, with no change to their terminal fleet or licensing position.
- Not if the merchant or acquirer actually wants to hold the crypto balance rather than convert to euro immediately.
05. The stack, layer by layer
Most of these layers can be rented from a named vendor, and usually should be. The part that matters is the one layer you have to own yourself.
The merchant's terminal fleet and settlement account
The existing terminal fleet and POS software, the bank settlement account, and the customer relationship or acquiring contract already in place. None of this changes when crypto acceptance is added.
The acquiring rail
On-chain/rail payment authorisation, crypto-to-euro conversion at the acquirer's own risk, and PSD2-plus-MiCA licensed settlement - explicitly not terminal hardware, a POS software change, or merchant-side custody.
The reconciliation layer
Acquirer-side reconciliation between the terminal system, the crypto rail and euro settlement; screening on incoming crypto-assets; dispute and chargeback handling adapted to an irreversible on-chain leg; conversion-rate and settlement-latency monitoring.
06. Why this stack
- The merchant needs no crypto licence at all - the acquirer carries the regulatory burden and the conversion risk.
- Terminal-native integration means no hardware refresh: existing Ingenico, Verifone and similar terminals keep working unchanged.
Risks, controls and owners
From the full blueprint · 3 of 9 shown, one with its control- Conversion-rate risk between authorisation and settlementControl: in the full blueprintOwner: The acquirer
- Acquirer holds an unlicensed fiat floatControl: Confirm the acquirer's actual PI-plus-CASP authorisation, or a partner-bank structure, before contractingOwner: The institution's counsel/compliance function
- Terminal/POS integration defectControl: in the full blueprintOwner: The acquirer, then the merchant's own IT on acceptance testing
The other 6 risks, and every control, are in the full blueprint.
Get all 9 with controls ↓Get the full BP-6
Web document · ~13 pages · 17 min read
This page is the short version. The full BP-6 adds all 9 risks with their controls and owners, the DORA third-party pack and the delivery plan in 4 phases. We email you a personal link, and it opens all 22 blueprints in the library.
We email your personal link and, now and then, a blueprint update. Privacy policy
Reviewed by Ivor Jugo, Offer Owner at Protofire · last verified August 2026
What the full blueprint adds, by reader
- Counsel
- The regulatory position across 3 regimes, article by article
- Risk & compliance
- All 9 risks, each with its control and the party that owns it
- Third-party risk
- The DORA pack: critical-or-important classification, the Art. 28(4) pre-contract assessment, Art. 30(3) contract clauses and Art. 29 concentration. Any commission we may earn on a named vendor is disclosed
- Technical lead
- Which of the 6 building blocks are essential and which are optional, and why
- Delivery
- The delivery plan in 4 phases, with the decision that gates each, then monitoring and incident response once live
- Board
- For the board paper: what each function gets, and where this pattern does not work
FAQ
Does a merchant or acquirer need a crypto licence to accept crypto at the till?
In the Merchant Acceptance With Euro Settlement pattern, the merchant needs no crypto-asset licence and holds no crypto exposure, because it is settled in euro and the terminal fleet never changes. The acquirer holding the merchant's fiat float needs a PSD2 Payment Institution authorisation in addition to a MiCA CASP authorisation for the crypto leg. This dual-licence requirement is not optional, since the EBA no-action-letter forbearance for EMT-linked payment services closed on 1 March 2026.
Who already runs euro-settled crypto acceptance in stores?
Printemps, the French department-store retailer, has accepted crypto across 20 French stores since November 2024 via Binance Pay, with conversion to euro by Lyzi, and it is the only reference here corroborated by independent press rather than vendor material. Farfetch accepts stablecoins via Triple-A. The largest live network, Checkout.com with Coinbase Payments, covers more than 1,000 enterprise merchants since 2 June 2026, but it settles in US dollars rather than euro, so it evidences the pattern generally rather than the euro-settlement variant.
What does the acquirer build versus rent in this pattern?
The merchant keeps its existing terminal fleet, POS software, bank settlement account and acquiring contract, none of which changes. The acquiring rail is rented from providers such as Lyzi, Triple-A, Checkout.com, Coinbase Payments or Fireblocks Flow, covering on-chain payment authorisation, crypto-to-euro conversion at the acquirer's own risk, and PSD2-plus-MiCA licensed settlement. What the acquirer builds is the reconciliation layer between terminal, rail and euro settlement, screening on incoming crypto-assets, dispute and chargeback handling adapted to an irreversible on-chain leg, and conversion-rate and settlement-latency monitoring.
Already evaluating this for your institution?
When you are ready, we scope a business case on your own numbers: the costed build, the controls, the SLA and the ROI your board needs to approve it. Or talk it through first.
Run this pattern in production, or tried to and stopped? .