All guides
GuideStablecoinsPaymentsEU

Stablecoin gateway refunds after fiat settlement

Who refunds a consumer after a stablecoin payment is settled to the merchant in euros, in which form, and what happens when a provider fails.

15 min read

The merchant remains responsible for a valid consumer refund after a gateway converts the customer's stablecoins into euros. The merchant's settlement currency does not automatically determine the customer's refund currency. The contracts must identify who accepted payment, what the customer paid and whether the customer expressly agrees to a different refund method. The merchant needs funds and a working repayment route even when its provider fails. (Bürgerliches Gesetzbuch, §§ 355(3), 357 and 362.)

A UK-based gateway serves a German merchant selling ordinary goods online to consumers in Germany. Customers pay a euro-denominated e-money token. A German crypto-asset service provider accepts and converts the tokens, while an authorised payment provider settles euros to the merchant. The financial roles can sit within one entity only where its permissions cover each service.

For this route, appoint the receiving provider expressly to collect the agreed payment for the merchant. Keep the UK gateway's software role separate from the financial contracts. The decisions below also identify what changes when the customer independently converts tokens before paying the seller, or a UK merchant directs its sales to Germany.

  • The seller handles the goods refund. A collecting provider's later failure to remit does not revive the customer's price debt where authorised receipt discharged it. (BGB, §§ 355(3), 357, 362(2) and 364(1).)
  • A qualifying withdrawal normally requires repayment within 14 days after notice, subject to the goods-return conditions. Refund in the original payment means unless the customer expressly agrees otherwise without incurring refund costs. (BGB, §§ 355(3) and 357(1)–(4).)
  • Check crypto and payment permissions separately. MiCA authorisation alone does not cover every e-money-token transfer or fiat payment service. A pending application does not authorise a new checkout launch. (Regulation (EU) 2023/1114, Articles 59 and 70(4); EBA/OP/2026/01, paragraphs 8–15.)
  • Keep the merchant's refund, the provider's execution liability and the token holder's issuer-redemption claim separate. Each has its own debtor and conditions. (BGB, §§ 357, 675u and 675y; Regulation (EU) 2023/1114, Article 49.)
  • Require an operational fallback and evidence of asset ownership. Safeguarding protects defined customer assets; it does not guarantee an immediate merchant refund. (Regulation (EU) 2023/1114, Article 75; Zahlungsdiensteaufsichtsgesetz, § 17; Kryptomärkteaufsichtsgesetz, § 45.)

Identify the seller and the provider at every payment stage

The seller's identity must agree across the checkout, order confirmation, invoice and refund notice. Identify separately the token issuer, receiving custodian, converter, payment provider and settlement bank. A group brand cannot establish which company owes payment. German distance-selling disclosures require the trader's identity, payment arrangements and complaint information. (Einführungsgesetz zum Bürgerlichen Gesetzbuche, Article 246a § 1.)

Record four different events: receipt of the customer's tokens, discharge of the sale price, completion of conversion and final euro settlement. Blockchain confirmation alone does not establish all four. For the selected collection model, the merchant mandate must specify the token, network, amount and acceptance event that discharge the customer. Authorised third-party receipt can satisfy the customer's obligation before bank settlement. (BGB, §§ 185, 362 and 364.)

A UK seller directing the relevant sales to consumers habitually resident in Germany must also preserve their mandatory German consumer protection. Choosing English law cannot remove that protection. Mere website accessibility is insufficient: the contract must fall within activities directed to Germany. (Regulation (EC) No 593/2008, Article 6(1)–(2).)

The German provider must have MiCA permission for its actual custody, exchange or transfer services, or qualify under the relevant financial-entity notification route. The payment provider must separately cover the payment activities performed. An e-money token is deemed electronic money under MiCA, and transfers for clients can engage payment-services law. Pure exchange and payment execution require separate classification. (Regulation (EU) 2023/1114, Articles 48(2), 59–60 and 70(4); EBA/Op/2025/08, paragraph 23.)

The UK operator must also examine its own activities. The technical-services exclusion requires absence of possession of funds and excludes payment initiation and account information services. UK anti-money-laundering rules also cover arranging crypto exchanges. Having no wallet keys therefore does not establish that the gateway is outside regulation. Obtain the required status or change the relevant function before starting it. (Payment Services Regulations 2017, regulation 138 and Schedule 1, Part 2, paragraph 2(j); Money Laundering Regulations 2017, regulations 14A and 56.)

Regulatory payment agency needs the required registration and principal responsibility. A merchant's collection mandate does not supply that status. Nor does MiCA contain a general exemption allowing an unlicensed gateway to provide crypto services as another CASP's agent. (Payment Services Regulations 2017, regulation 34; FCA, PERG 15.4, Q28; Regulation (EU) 2023/1114, Article 59.)

Current permissions matter. MiCA's maximum national grandfathering period ended on 1 July 2026. The EBA's February 2026 opinion advises national authorities to allow narrowly conditioned supervisory continuation for certain pending payment-authorisation applicants, with restrictions on marketing and new clients. It supplies no basis for new merchant onboarding in this route. The UK's enacted cryptoasset regime has full commencement on 25 October 2027; existing requirements still govern the present activity. (Regulation (EU) 2023/1114, Article 143(3); EBA/OP/2026/01, paragraphs 9–14; SI 2026/102, regulation 1.)

Select a MiCA-compliant token and check its issuer and white paper. ESMA's 8 October 2026 opinion expects CASPs to cease services involving non-compliant stablecoins, subject to limited supervised wind-down. A familiar ticker or euro peg is insufficient. These are supervisory expectations, distinct from the underlying statutory conditions. (Regulation (EU) 2023/1114, Article 48; ESMA75-113276571-1742, paragraphs 7 and 12–27.)

Before integration, the merchant and gateway should collect the exact entities' permission records, contracts and transaction responsibilities. Licentium's payment processor selection guide provides the wider provider assessment process.

Establish the customer's entitlement before calculating the refund

For an eligible distance sale, the consumer generally has 14 days to withdraw. For ordinary goods, the period normally starts on delivery, with different rules for split deliveries and missing withdrawal information. Check the statutory exceptions, including personalised and perishable goods. Paying stablecoins does not turn an ordinary fixed-price goods purchase into an excluded financial-market transaction. (BGB, §§ 312g, 355 and 356.)

The merchant must return the received performance without undue delay and within 14 days after receiving the withdrawal. It may withhold repayment until the goods return or the consumer supplies dispatch evidence, whichever happens first. That withholding right does not apply where the merchant offered collection. A provider investigation does not restart the clock. (BGB, §§ 355(3) and 357(1), (4).)

Include the refundable standard outbound delivery charge. The extra cost of a consumer-selected premium delivery option need not be returned. Direct return costs and compensation for excessive handling depend on the statutory information and other conditions. They are different from a gateway's processing fee. (BGB, §§ 357(2), (5) and 357a(1).)

Defective goods require their own decision. Repair or replacement may precede rescission; serious defects, failed cure, refusal and other statutory conditions can change that sequence. On qualifying rescission, the seller bears return costs and dispatch evidence has the statutory effect specified for repayment. Apply these rules rather than imposing the withdrawal timetable on every defect claim. (BGB, §§ 437, 439, 475(6)–(7), 475d and 476.)

Customer service should retain the order, delivery date, withdrawal or defect notice, applicable terms and return evidence. A voluntary return outside statutory rights follows the agreed policy, subject to mandatory law. A duplicate transfer or payment made without a legal basis requires a separate restitution analysis. (BGB, §§ 361, 476 and 812.)

Determine the refund means and amount from the customer's payment

For statutory withdrawal, the default is the same payment means used for the original transaction. Another method requires express agreement and must not cause the consumer refund costs. The merchant's net euro proceeds do not replace that rule. (BGB, § 357(3).)

In the direct-token collection model, preserve the token identity, network and accepted units. The provider's later conversion is an arrangement on the merchant's side. Do not treat it as the customer's consent to a bank refund or a deduction for conversion losses.

For euro-priced goods paid with a euro token, offer a separately recorded choice to receive the refundable gross euro price and delivery component by bank transfer. Identify the amount and cover the costs caused by that alternative. Taking that agreement when the refund arises is the recommended evidence practice; the statute does not prescribe that timing. A preselected checkout statement is poor evidence of an express choice. (BGB, § 357(3); Commission Notice 2021/C 525/01, section 5.5.3.)

If the customer retains the token route, make the terms commit to returning the originally accepted token units, adjusted for any lawful partial refund. This is a proposed contractual allocation of quantity and price risk. The commitment must preserve any greater mandatory repayment entitlement. (BGB, § 361(2).) It should not be presented as a universal statutory valuation formula for every stablecoin arrangement. The merchant must arrange the units and transfer costs needed to honour that commitment.

A different result can follow where the customer independently sells tokens to a converter and pays the merchant euros. The merchant then refunds the euro payment through the applicable original means. Check whether the conversion was genuinely independent: a merchant-arranged related service can also unwind when the goods contract is withdrawn. Separate terms pages alone do not establish independence. (BGB, §§ 357(3) and 360.)

An EMT holder's redemption right is another obligation. MiCA requires the issuer to redeem at par into funds other than electronic money, subject to its recovery provisions. It does not make the issuer responsible for the merchant's goods refund. Nor does it guarantee that a converter's market sale executes at par. (Regulation (EU) 2023/1114, Article 49(2), (4)–(6).)

For a dollar token against a euro invoice, record the sale denomination, accepted token quantity and any agreed refund rate separately. Neither the original rate nor the current market rate is automatically the answer merely because the merchant settled euros. The proposed euro-refund agreement should identify the euro amount without passing a new exchange charge to the customer. Original independent acquisition costs require their own contractual analysis. (BGB, § 357(3); Commission Notice 2021/C 525/01, section 5.5.3.)

Allocate failed settlement and provider loss through three refund flows

Normal cancellation after euro settlement

The customer validly withdraws, the merchant has received final euro settlement, and return evidence satisfies the withholding conditions. The customer expressly chooses the documented euro refund.

  1. Customer service confirms the entitlement, refundable gross price and delivery component. It records the withdrawal date and dispatch evidence.
  2. The merchant instructs its payment provider from available funds. The consumer receives the agreed amount without a deduction for the gateway's fee.
  3. Finance links the bank confirmation to the original order and closes the refund only when repayment is established. A queued instruction alone is insufficient evidence.

The original token conversion can remain completed. The merchant owes the agreed repayment within the applicable withdrawal deadline; a depleted provider balance requires a top-up or another lawful payment route. (BGB, §§ 357 and 362.)

Conversion or settlement fails during the refund

The merchant has received euros, but the customer retains the token refund. The merchant funds a fresh conversion and transfer; the converter fails before the customer receives the refund.

The merchant remains responsible for completing its refund obligation. Operations must establish whether the failed step was an exchange, a custody transfer or an in-scope payment order. A firm exchange price and its finality conditions engage MiCA's exchange rules. An unauthorised or incorrectly executed payment engages separate payment remedies. The statutory outcome depends on the service, user and territorial conditions; the merchant's business payment contract may validly vary specified default protections. (Regulation (EU) 2023/1114, Article 77; BGB, §§ 675e, 675u and 675y.)

The merchant should fund an alternative permitted provider or obtain express agreement to a euro refund. It should pursue the failed provider under the relevant service contract and statutory rights. Do not make the customer's repayment conditional on that recovery.

If the failure instead occurred during the original inward conversion, identify whose recipient accepted the tokens. Receipt by the merchant's authorised collecting provider may already have discharged the customer. Failure of a converter independently engaged by the customer before payment reached the merchant can leave the goods price unpaid. The merchant must not demand a second payment without resolving that distinction. (BGB, §§ 185, 362 and 364.)

The provider becomes insolvent after settlement

The merchant has received the sale proceeds, a refund is due, and the provider holding the merchant's refund balance enters insolvency. The merchant should use funds outside that provider and a functioning lawful route. Its customer cannot be required to wait for the merchant's recovery from the estate. (BGB, §§ 357 and 361.)

For the selected German financial providers, separate three claims:

  • Crypto-assets genuinely held in custody engage MiCA segregation and German statutory client attribution, including specified omnibus holdings. German law qualifies that attribution where the client consented to dispositions for the institution's or another person's account. (Regulation (EU) 2023/1114, Article 75(7); KMAG, § 45.)
  • Qualifying payment or e-money funds engage the relevant safeguarding method. Establish the protected entitlement and actual account, asset or guarantee. A reserve labelled on a dashboard is insufficient. (ZAG, § 17.)
  • An unpaid conversion price or other ordinary contractual receivable may be an insolvency claim. Separate it from a right to recover property outside the estate and file the correct claim with supporting records. (Insolvenzordnung, §§ 38, 47 and 174.)

These protections do not guarantee the token's value or immediate access. A custodian's liability for attributable crypto-asset loss is subject to MiCA's conditions and value-at-loss cap. Issuer failure and an independent blockchain problem require different analysis. (Regulation (EU) 2023/1114, Article 75(8).)

If the German merchant itself becomes insolvent, a pre-opening consumer refund claim will ordinarily enter its insolvency proceedings unless a specific proprietary or priority basis applies. German custody rules must not be applied automatically to a UK provider's estate. In the software-only UK gateway model, its failure principally requires continuity of records, instructions and the merchant's access to its financial providers. (InsO, §§ 38, 47 and 87.)

Frozen tokens and duplicate recoveries

Record whether a freeze reflects an issuer block, a provider review or a legal prohibition. An operational block requires a lawful alternative refund plan; it does not itself create an agreed extension of the merchant's deadline. A legal prohibition on paying the recipient must be resolved before using any replacement route. (BGB, §§ 275, 286(4), 357 and 361.)

Use one order record for the merchant refund, provider reimbursement and any separate dispute credit. Check actual receipt before retrying a payment. The selected token payment has no card leg, so a card chargeback should not be promised. If a customer separately used a card to acquire tokens, assess that transaction under its own scheme rules.

A true duplicate recovery can support restitution, subject to the applicable defences. It does not authorise an unrestricted debit of the customer's wallet. Nor does a pending dispute automatically suspend a statutory refund. (BGB, §§ 362, 812, 814 and 818–819.)

Put the refund process into the checkout and contracts

The merchant should implement five connected documents and controls:

  1. Customer terms identifying the seller, payment means, refund rights, any token-quantity commitment, alternative-refund consent process and costs. Preserve mandatory withdrawal and defective-goods rights. (BGB, §§ 357, 361 and 476.)
  2. A merchant-provider schedule defining collection authority, the discharge event, conversion finality, gross-to-net reconciliation, refund funding and responsibility for failed instructions. (BGB, §§ 362 and 364; Regulation (EU) 2023/1114, Articles 77 and 82.)
  3. Custody and payment terms identifying the actual client, ownership records, safeguarding method, subcustodians and recovery procedure. Keep commercial indemnities separate from mandatory duties. (Regulation (EU) 2023/1114, Articles 70 and 75; ZAG, § 17.)
  4. An incident procedure assigning responsibility for low balances, frozen assets, duplicates, provider failure and an alternative payout. The merchant funds the customer obligation; contractual recourse allocates the resulting loss among businesses.
  5. A complaints process that distinguishes the seller, payment provider and CASP. German payment complaints ordinarily require a response within 15 working days, exceptionally 35 with an interim explanation where the delay is outside the provider's control. CASP complaints are free and normally decided within two months, with an exceptional-delay procedure. Neither timetable replaces the goods-refund deadline. (ZAG, § 62(3); Regulation (EU) 2023/1114, Article 71; Delegated Regulation (EU) 2025/294, Article 6.)

The checkout also needs Germany's electronic withdrawal function, effective from 19 June 2026. It must remain accessible during the withdrawal period, include a confirmation step and promptly provide a durable receipt with the declaration and timestamp. Disclose where the function can be found. A generic support form alone does not establish compliance. (BGB, § 356a; EGBGB, Article 246a § 1(2), point 1; Act of 3 February 2026, BGBl. 2026 I No. 28, Article 10(1).)

The merchant and gateway should approve the legal-entity map, permission evidence, refund terms and funding arrangements before accepting payments. Test each of the three flows against actual provider confirmations and customer receipt. If a provider cannot support the required refund method or the agreed fallback, change that route before launch.

Review gateway and merchant terms with Licentium to identify the refund debtor, review checkout and provider clauses, and specify the documents and product changes needed for the selected route.

guideStablecoinsPaymentsEU