Stablecoin payments for cross-border supplier invoices

Executive Summary

• For this Brazil–France supplier invoice, the recommended agreement keeps USD bank money as the payment asset. The buyer is discharged when the supplier receives the amount due as available USD funds in its designated account, net of charges. Token delivery to the buyer’s provider or the off-ramp does not meet that agreed condition. (Code civil, arts. 1342, 1342-2, 1342-4 and 1342-7.)
• Express token acceptance changes the result. If the supplier agrees that receipt of a specified quantity of eligible USDC satisfies the invoice, discharge occurs when all agreed delivery conditions are met. Later de-pegging or redemption failure then falls on the supplier under that allocation, subject to preserved buyer warranties and mandatory law. (Code civil, arts. 1103, 1193 and 1342-4.)
• A supplier-nominated wallet requires an express statement of its owner, controller and recipient’s authority. An authorised collection agent can receive effective payment of the agreed asset. A wallet used only to collect tokens for conversion does not establish that fiat debt has been paid. (Code civil, arts. 1342-2 and 1340.)
• Use a Brazilian provider entitled to perform the actual virtual-asset and foreign-exchange (FX) activities, with an appropriately authorised account provider for local funds. A Brazilian virtual-asset service company, or SPSAV, must keep the proposed transfer within its applicable USD 100,000 limit. A foreign bank’s EU authorisation does not remove that Brazilian limit. (Lei 14.478/2022, arts. 2 and 5; Resolução BCB 277/2022, arts. 29 IV and 76-A; Resolução BCB 520/2025, arts. 19–22 and 28.)
• USDC has an EU issuer and holder-redemption arrangement, but the token is not an immediately available USD bank balance. A European Economic Area (EEA) corporate holder’s redemption through Circle France requires the prescribed onboarding and controls. Secondary-market conversion involves a separate dealer price and settlement obligation. (Regulation (EU) 2023/1114, arts. 48–49; Circle, MiCA Redemption Policy, 15 September 2026, §§ 1–3, 5 and 8.)
• A permission under the Markets in Crypto-Assets Regulation, or MiCA, alone does not cover every payment activity. The off-ramp needs the relevant crypto service scope and the payment authority required for its fiat or e-money payment services. Supplier acceptance grants neither permission. (Regulation (EU) 2023/1114, arts. 59–60 and 70(4); Directive (EU) 2015/2366, arts. 1, 4 and 37.)
• A firm platform payout promise gives the buyer contractual recourse, but does not itself release the invoice debt. The supplier must expressly accept any substitution of debtor. Otherwise, platform insolvency before the agreed receipt leaves the buyer responsible for payment. (Code civil, arts. 1330 and 1336–1340.)

The documented route for a USD 75,000 invoice

The proposed sale contract makes USD 75,000 payable to the French supplier’s designated USD account at a bank in France. The buyer funds the transaction from a BRL account in its own name. A Brazilian virtual-asset service provider sells native USDC to the buyer for BRL, records the buyer’s ownership and transfers those tokens under a disclosed mandate.

The proposed off-ramp is Banking Circle S.A., a Luxembourg bank. Its official records identify crypto-for-funds exchange, crypto-for-crypto exchange and client transfer services, with France in its cross-border service list. Its published stablecoin settlement product includes USDC and serves financial institutions. The designed transaction therefore requires an accepted institutional relationship with the Brazilian provider and express bank acceptance of the underlying buyer, supplier beneficiary and disclosed agency structure. (CSSF, Banking Circle S.A., register B00000408; ESMA, MiCA crypto-asset service-provider register, Banking Circle S.A. entry; Banking Circle, stablecoin settlement announcement, 27 April 2026.)

Banking Circle would buy the buyer’s USDC as principal under a separate accepted exchange quote and pay the agreed USD proceeds to the supplier. The documents must identify the buyer as the seller of the tokens, the Brazilian provider as its agent and the bank as purchaser. They must specify when token ownership passes and when the bank owes the fiat price. This structure uses the bank’s exchange service; any separate custody service needs its own analysis and permission. (Regulation (EU) 2023/1114, arts. 3(1)(19), 60, 75 and 77.)

The supplier remains outside token ownership in this route. The bank becomes the token holder after its purchase and may use its liquidity or redeem tokens separately. Its purchase price obligation must state whether issuer redemption is a condition of payout. The preferred contract commits the bank to the agreed net USD payment once its purchase conditions are satisfied, without making the supplier’s receipt depend on a later discretionary sale or redemption.

This arrangement needs separate, consistent documents: the goods contract and payment addendum; the buyer’s Brazilian account, acquisition and transfer agreements; and the bank’s accepted exchange and third-party payout instructions. A group brand or dashboard label cannot replace the legal entity and capacity at each stage. The buyer’s contract with a provider cannot alter the supplier’s agreed payment rights without the supplier’s assent. (Code civil, arts. 1193, 1199 and 1340.)

French law fixes the agreed performance and place of payment

The parties should choose French substantive law for the sale and payment addendum, expressly exclude the United Nations Convention on Contracts for the International Sale of Goods and select the competent courts of Paris. For an international sale of tangible goods within its scope, the Hague Convention of 15 June 1955 governs the choice of law before a French court and is preserved by Article 25 of Rome I. Brazil and France are CISG contracting states; choosing French law alone does not express an exclusion. An express exclusion uses the Convention’s party-autonomy rule. (CISG, arts. 1(1)(a) and 6; Hague Convention of 15 June 1955, arts. 1–2 and 5–7; Regulation (EC) No 593/2008, arts. 3, 12 and 25; Regulation (EU) No 1215/2012, art. 25.)

French payment law starts with performance of the obligation owed. A creditor can accept a different performance, even where its value differs, but the debtor cannot impose that substitution. A USD invoice therefore does not authorise payment in any dollar-referenced token. The parties must agree whether USD funds remain due or whether defined token delivery is accepted in satisfaction. (Code civil, arts. 1342 and 1342-4.)

French law permits foreign-currency payment in France for an obligation arising from an international transaction. The Brazil–France goods sale meets that description. This rule supports the USD invoice; it does not classify USDC as sovereign currency. The addendum should fix the contractual place of payment at the supplier’s stated address in France and identify the receiving account or wallet separately. A blockchain address does not supply a territorial place of performance. (Code civil, arts. 1343-3, 1343-4 and 1342-6.)

The law and forum clause governs the contracting parties’ invoice relationship. It does not confer regulatory permissions, bind a non-signatory issuer or off-ramp, or decide every custody, property and insolvency question. Mandatory rules remain relevant where the actors operate. The supplier should sign its own recipient designation because external agency authority falls outside Rome I’s contract-law rules. (Regulation (EC) No 593/2008, arts. 1(2)(g), 9 and 12; Code civil, art. 1199.)

Ledger finality and legal discharge require different evidence

A ledger records a token transfer under the network’s rules. Legal discharge asks whether the buyer performed the obligation owed to the correct recipient. The amount, asset, chain, wallet authority, contractual confirmation condition and any required account credit all matter. A transaction hash can help prove payment, but cannot establish these elements by itself. The buyer claiming release bears the burden of proving extinguishment. (Code civil, arts. 1342-2, 1342-8 and 1353.)

For the recommended fiat route, the legal trigger is the supplier’s receipt of available USD funds allocated to the invoice. Funding the Brazilian platform, receiving a successful transaction status, passing ownership to the bank and receiving a payout reference are intermediate events. The contract should distinguish a bank’s receipt of an instruction from its credit to the supplier, and distinguish a displayed pending credit from funds available to the supplier.

The payment schedule should also define how partial credits reduce the balance. The supplier need not accept a short payment as full satisfaction, and payment costs ordinarily fall on the debtor. A USD 74,900 credit against a USD 75,000 principal balance leaves USD 100 unpaid under the proposed allocation. If interest is due, the parties must address the statutory default that partial monetary payments apply to interest first. (Code civil, arts. 1342-4, 1342-7, 1342-10 and 1343-1.)

Neither party should describe the agreed receipt as immune from every legal challenge. A sanctions measure, court order, insolvency avoidance rule or bank correction raises a separate question. The clause establishes invoice performance between buyer and supplier; it does not override those rules.

Direct stablecoin receipt transfers risk at an agreed event

In variant A, the supplier signs an addendum accepting 75,000 native USDC on Ethereum as complete performance of the USD 75,000 invoice. This is a deliberate fixed-quantity bargain. The parties could instead calculate the token quantity using an executable USD price, but that would create a different allocation. The dollar reference alone does not choose between them. (Code civil, arts. 1103, 1193 and 1342-4.)

The token schedule should identify USDC’s issuer arrangement, Ethereum as the permitted network and the exact native token contract. It should exclude wrapped, bridged and similarly named tokens unless separately approved. The supplier’s wallet must be authenticated through an authorised signatory and an independently verified communication channel. A signed challenge or controlled test transfer may evidence technical control; it does not alone establish company authority or legal ownership.

For this direct variant, the supplier controls the signing authority for its own wallet. If a custodian holds the keys instead, the addendum must identify the custodian and require the corresponding credit to the supplier’s account. Wallet control means the power to authorise transfers or instruct the custodian, including the agreed recovery and approval arrangements. Issuer freeze powers can still restrict movement from a wallet whose keys the supplier controls. (Circle, USDC White Paper, amended 15 September 2026, D.1; Regulation (EU) 2023/1114, art. 75.)

The proposed acceptance event requires the full net token quantity, the approved token and chain, the authenticated address, and the stipulated confirmation evidence. The parties can require the transaction’s block to be reported as finalised by two independent Ethereum node services. They should require no active issuer block or legal hold preventing use at that event. Any technical waiting period belongs in the payment schedule; it is not a statutory rule of invoice discharge.

Once those conditions are satisfied, the supplier has accepted token performance. Under the proposed allocation, subsequent de-pegging, issuer failure, redemption delay and the supplier’s conversion choice fall on the supplier. A retained warranty about the buyer’s title, lawful source or compliance can preserve recourse for a later problem caused by the buyer. A later freeze does not automatically revive a debt already discharged through conforming performance. (Code civil, arts. 1103, 1342 and 1342-4.)

Direct receipt also requires French payment and anti-money-laundering (AML) compliance. The Monetary and Financial Code expressly regulates debt payment with e-money tokens. The professional-debtor e-money payment ceiling is EUR 3,000 unless an exception applies. Article L.112-6 III(e) removes the token-payment restriction where both debtor and creditor undergo the specified identity verification or equivalent checks. This USD 75,000 direct receipt must document that exception. (Code monétaire et financier, arts. L.112-6 I and III(e), and D.112-3.)

The supplier also falls within the French goods-merchant AML rule when it accepts this e-money payment above EUR 10,000. MiCA deems an e-money token electronic money. The supplier must therefore meet the applicable customer, beneficial-owner, risk-assessment and reporting duties. Satisfying the payment-cap exception or using a custodian does not automatically discharge those separate obligations. (Regulation (EU) 2023/1114, art. 48(2); Code monétaire et financier, arts. L.561-2, 11°, D.561-10-1, L.561-4-1–L.561-8 and L.561-15.)

An intermediary’s fiat promise leaves the invoice outstanding

In variant B, the buyer sends USDC to an intermediary that promises to pay USD to the supplier. If the supplier agreed to receive fiat, the buyer has funded its payment arrangement but has not yet delivered the agreed performance. A provider failure, delayed conversion or insolvency before supplier credit leaves the invoice unpaid to that extent. The buyer must pursue its separate contractual claim against the intermediary. (Code civil, arts. 1199, 1342 and 1342-2.)

The strongest exception concerns collection authority. French law recognises payment to the creditor’s designated recipient. If the supplier expressly appoints the intermediary to receive eligible tokens as invoice payment, conforming receipt by that agent can discharge the buyer before conversion. The supplier then bears the agent’s subsequent conversion or remittance risk to the extent agreed. The documents must state whether the recipient accepts payment for the supplier or merely processes the buyer’s funding. (Code civil, art. 1342-2.)

An intermediary’s promise also differs from substituting it as debtor. Novation is not presumed. An accepted delegation can give the supplier another debtor while preserving the original buyer’s obligation. An express release can instead substitute the new obligation. The original buyer nevertheless remains liable if it expressly guarantees the new debtor’s future solvency or that debtor is already in debt-settlement proceedings at delegation. A simple instruction naming another payer or recipient does not itself effect novation or delegation. (Code civil, arts. 1330, 1336–1338 and 1340.)

If the platform sells a fixed BRL-to-USD payment product as the buyer’s counterparty, its contract should allocate the conversion price, fees and payout deadline. That can move economic risk to the platform, but the supplier still retains its claim against the buyer unless it expressly agrees otherwise. A supplier accepting a release in exchange for the platform’s obligation takes platform credit risk. The platform’s payment, FX and virtual-asset permissions follow its actual activities.

Brazil’s eFX international-payment regime imposes a further limit on that alternative. Since 1 October 2026, settlement between an eFX provider and its immediate foreign counterparty must use the permitted fiat channels; virtual assets are prohibited for that settlement. Goods or services bought through a digital payment solution outside an integrated e-commerce platform also face a USD 10,000 equivalent limit. An eFX product therefore cannot supply the stablecoin-funded substitute for this USD 75,000 invoice. The distinct buyer-owned-token transfer must satisfy its own virtual-asset FX rules in substance. (Resolução BCB 277/2022, arts. 49 I(b), 50 I, 56-B § 2 and 76-A–76-B, as amended by Resolução BCB 561/2026.)

A nominated wallet does not settle freeze and conversion losses

Variant C starts with a wallet nominated by the supplier. The signed instructions must establish whether it is the supplier’s own wallet, an authorised collection agent’s wallet or an off-ramp address used pending fiat payout. Nomination alone does not specify the payment asset or discharge event. Subsequent ratification or a demonstrated benefit can also affect an unauthorised-recipient dispute, so a blanket rule that every misdirected transfer can never count would be too broad. (Code civil, arts. 1342-2, 1342-3 and 1340.)

If the agreed direct-token conditions require usable tokens, a freeze before those conditions are met prevents the designed acceptance event. If the supplier has already received conforming tokens in satisfaction, a later issuer freeze or failed voluntary conversion generally falls within its accepted risk. Preserved buyer warranties and the cause of the restriction can change that result. Under a fiat-only clause, the buyer remains exposed until the agreed fiat receipt regardless of the nominated wallet’s balance.

A transfer on the wrong chain fails an express chain condition even where the address characters match. A different token contract or unsupported wrapper also fails the agreed eligibility test. The buyer should bear its own routing error and instruct a lawful cure. Authentic but erroneous supplier instructions require a different inquiry into compliance, creditor cooperation and available remedies. Neither a test payment nor a saved address eliminates the need to authenticate changes. (Code civil, arts. 1104, 1217, 1342-2 and 1353.)

A de-peg before the bank purchase changes the number of tokens or BRL funding needed for the net USD target. A de-peg after a firm principal purchase falls under the bank’s purchase terms; the buyer nevertheless remains liable to the supplier until fiat receipt. In a completed fixed-quantity direct payment, subsequent de-pegging rests with the supplier under the agreed allocation. The same market event therefore has different effects at different contractual stages.

Weekend movement requires an executable quote and a clear expiry rule. The buyer should bear BRL/USD and token/USD repricing until a provider expressly assumes that exposure. A chain transfer made outside banking hours does not establish that USD payout will occur then. For a USD payment where both the payer’s and payee’s payment service providers, or the sole provider, are located in the EU, the revised Payment Services Directive, or PSD2, excludes Articles 81–86 for the parts of the transaction carried out in the EU, so the USD deadline and fee gross-up need express agreement. (Directive (EU) 2015/2366, art. 2(3).)

USDC redemption belongs to the holder at the relevant stage

The selected token is native USDC under Circle’s published dual-issuer arrangement. Circle Internet Financial Europe SAS is a French electronic-money institution, identified in REGAFI by CIB 17788. The French Financial Markets Authority (AMF) record describes an Article 60 MiCA notification for custody, administration and transfer of its own e-money tokens. That limited route should not be treated as a general licence for every crypto service. (REGAFI, Circle Internet Financial Europe SAS, entity 737158; AMF, notification N2026–005, 23 April 2026; Regulation (EU) 2023/1114, art. 60(4).)

On 14 October 2026, the European Banking Authority classified USDC as a significant e-money token. That classification engages MiCA’s additional issuer requirements. The EBA announced that responsibility for specified reserve, liquidity, own-funds, recovery and redemption-plan matters will transfer from France’s prudential supervisor, ACPR, on 12 November 2026, while ACPR retains other supervision. The holder’s redemption claim continues under Article 49. (Regulation (EU) 2023/1114, arts. 49, 56, 58 and 117; EBA, USDC significance announcement, 14 October 2026.)

MiCA gives an e-money token holder a claim against the issuer and requires redemption at par into funds other than electronic money. The issuer must disclose redemption conditions and may not charge a redemption fee, subject to the Regulation’s recovery provisions. This is a holder’s legal claim. It is separate from a dealer’s secondary-market sale price, spread and settlement promise. (Regulation (EU) 2023/1114, art. 49(2), (4)–(6).)

Circle’s published policy directs EEA holders to Circle France and non-EEA holders to Circle LLC’s arrangements. It addresses fungible supported USDC circulating between the issuers’ regions. A French corporate supplier holding accepted USDC has the EEA holder route even without an existing full Circle Mint account. Corporate non-customers must establish a redemption-only account and complete the prescribed checks. The retail processing timetable should not be imported into this corporate transaction. (Circle, MiCA Redemption Policy, 15 September 2026, §§ 1.4, 2.1, 3 and 4; USDC White Paper, D.1.)

Under the recommended bank-purchase route, the supplier never becomes the token holder. The buyer owns the tokens before the agreed sale; the bank owns them afterwards and holds the EEA redemption claim. A provider possessing the keys as custodian does not necessarily own its customer’s tokens. The custody and account terms must establish the customer’s rights and who can exercise redemption operationally.

Redemption can be delayed by lawful restrictions and operational requirements. Circle’s September policy also describes stress measures where reserves cannot be rebalanced between its US and EEA issuers, including deferred redemption and eligibility restrictions. Those contractual statements do not determine whether every particular restriction complies with MiCA. An applicable stress event should stop a new invoice transfer until the issuer and receiving bank establish lawful eligibility and an executable payout. (Circle, MiCA Redemption Policy, §§ 5 and 8; Regulation (EU) 2023/1114, arts. 49 and 55.)

Issuer failure concerns the redemption claim and access to backing assets. Service-provider failure concerns custody, execution or an unpaid exchange price. MiCA requires protection of customer ownership and custody segregation, but those protections do not insure the issuer’s solvency or guarantee immediate access. After an outright sale to an off-ramp, the seller may hold a contractual fiat-price claim rather than a proprietary claim to customer tokens. The agreement must identify that exposure. (Regulation (EU) 2023/1114, arts. 70(1), 75(7)–(8) and 77; Circle, USDC White Paper, D.5 and D.9–D.12.)

Brazilian permissions follow the BRL and token activities

Brazilian virtual-asset regulation covers third-party exchange, transfer and custody services. The Central Bank of Brazil (BCB) regulates the relevant providers, while the securities regulator retains competence over securities. Calling an instrument a stablecoin does not decide a securities question; adding investment or collective-return rights would require a separate classification. The defined transaction uses USDC for payment and adds no investment product. (Lei 14.478/2022, arts. 1–2, 5 and 7–8; Decreto 11.563/2023, arts. 1–3; Lei 6.385/1976, art. 2 IX.)

For fiat collection, the buyer should use an individual payment or deposit account in its own name at an entitled institution. A platform cannot create deposit-taking or payment-account authority merely by obtaining virtual-asset permission. The account agreement must identify the institution holding BRL and the basis on which the platform can instruct it. Statutory separation of payment-account funds should not be extended to every platform balance or token holding. (Lei 12.865/2013, arts. 6, 9 and 12; Resolução BCB 520/2025, art. 28.)

For token acquisition and transfer, use a fully authorised SPSAV with the required intermediation and custody category and FX permission. An eligible bank needs FX permission and the required crypto notification and certification completed. An ordinary bank licence alone does not establish those crypto conditions. A timely incumbent application can permit continued activity under transition rules, but an applicant is not necessarily fully authorised or already subject to every requirement of the completed regime. (Resolução BCB 277/2022, art. 29 I, IV and § 5; Resolução BCB 519/2025, arts. 2–3 and 26; Resolução BCB 520/2025, arts. 7, 9–10, 19–22 and 88.)

Brazil now brings international virtual-asset payments and fiat-referenced token acquisition into its FX rules. An SPSAV’s relevant international payment with a counterparty lacking BCB FX authorisation is capped at USD 100,000 equivalent. The USD 75,000 invoice leaves room for execution needs, but the entire proposed transfer must stay within the applicable limit. Artificial splitting is not an acceptable substitute for the correct permission. (Resolução BCB 277/2022, arts. 22, 29 IV and 76-A.)

The proposed ownership sequence matters. Article 76-A prohibits the Brazilian provider’s token purchase or sale from being paid or received in foreign currency. Its definition treats the provider as buyer or seller for those transactions. The structure therefore uses a BRL sale to the buyer, followed by transfer of buyer-owned tokens and the bank’s separate purchase from that disclosed buyer. It must not conceal the Brazilian provider selling its own inventory for USD. (Resolução BCB 277/2022, art. 76-A § 1 I and § 2.)

The same article restricts moving funds in third parties’ interests, with a specified exception involving a BCB-authorised FX institution acting for clients. The buyer must be the identified principal paying its own invoice. An omnibus platform arrangement cannot hide an additional unlicensed intermediary or disregard this restriction. If the bank will accept only a different principal structure, the parties need a bank-led Brazilian arrangement satisfying the rule or an ordinary authorised FX payment. (Resolução BCB 277/2022, art. 76-A § 3.)

Before transfer, the Brazilian provider must document the client’s terms, payment purpose and recipient relationship, and perform the required diligence on the foreign provider. Transfers involving self-hosted wallets require owner and source/destination checks. Brazil’s phased travel-data implementation does not excuse withholding information already required by the EU receiving institution. (Resolução BCB 277/2022, arts. 76-A §§ 4–5, 76-B § 2 and 76-C; Resolução BCB 520/2025, arts. 43–44 and 89.)

For transfers to or from self-hosted wallets of at least USD 10,000 equivalent, Brazil also requires the specified report to its financial intelligence authority. Operations contracted from 1 October through 31 December 2026 are reported on the first business day of January 2027. This affects the direct-wallet variants at the defined amount; suspicious-transaction reporting is a separate duty. A hosted institutional wallet is not self-hosted merely because it sits abroad. (Circular BCB 3.978/2020, art. 49 V and § 2, as amended by Resolução BCB 591/2026.)

EU permissions cover exchange, transfer and fiat payout separately

Professional crypto services generally require a crypto-asset service provider (CASP) authorisation or an eligible financial institution’s Article 60 entitlement. Exchange, custody and transfer are distinct categories. By October 2026, the maximum MiCA grandfathering period has ended; an old national virtual-asset provider registration alone does not establish permission to provide professional EU crypto services. (Regulation (EU) 2023/1114, arts. 59–60, 63 and 143(3).)

Banking Circle’s bank status and recorded exchange and transfer services make it a relevant candidate for the proposed route. The contracting documents must match those activities. Buying USDC as principal differs from holding it for the buyer pending a discretionary sale. If the latter service is added, its custody authority and protections must be addressed expressly. (CSSF, Banking Circle S.A., register B00000408; ESMA, MiCA service-provider register, Banking Circle S.A. entry; Regulation (EU) 2023/1114, arts. 75 and 77.)

MiCA requires related payment services to be provided by a properly authorised payment provider, whether the crypto provider itself or another institution. E-money tokens (EMTs) are electronic money under MiCA, and electronic money falls within PSD2’s definition of funds. A token transfer service can therefore raise payment-law requirements as well as crypto rules. Banking status provides the selected off-ramp with a payment-provider basis; a CASP-only intermediary needs the appropriate separate payment arrangement. (Regulation (EU) 2023/1114, arts. 48(2) and 70(4); Directive (EU) 2015/2366, arts. 1(1)(a), 4(25) and 37; Luxembourg Law of 10 November 2009, arts. 1–4.)

The EBA’s nonbinding opinion of 12 February 2026 addresses qualifying EMT payment services after the general transition ended on 2 March 2026. Its limited continuation arrangements concern pending authorisation applications and restrict new business. This proposed transaction should use a payment provider whose permission covers the actual service. (EBA, Opinion EBA/OP/2026/01, 12 February 2026, paras. 8–15.)

The classification still depends on the service actually supplied. In Betaal Garant Nederland, the Court of Justice held that a guarantee intermediary using its linked foundation’s bank account did not itself provide the relevant credit-transfer service merely because the foundation instructed its bank. The banks executed transfers ancillary to the guarantee arrangement. That holding requires care with labels, but does not exempt a treasury business whose core service is transmitting customer funds. Money remittance and the precise account and mandate arrangements require separate assessment. (Betaal Garant Nederland CV v De Nederlandsche Bank NV, C-51/25, EU:C:2026:590, paras. 11–15, 30, 35–41, 46 and 52–53; Directive (EU) 2015/2366, Annex I, points 3(c) and 6.)

Supplier receipt of payment for its own goods does not by itself make the supplier an issuer, exchange or custodian serving clients. Its French payment and merchant AML obligations remain distinct. A Brazilian platform actively supplying services in the EU must also consider EU territorial requirements; a contractual recital about the client’s initiative cannot manufacture MiCA’s narrow reverse-solicitation conditions. (Regulation (EU) 2023/1114, arts. 3, 59 and 61.)

A third-country token needs a fresh EU assessment

The selected USDC arrangement includes an EU electronic-money institution as issuer and an EU whitepaper record. A token issued solely under a third-country regime does not obtain equivalent MiCA status because it references USD or is accepted by the supplier. EU public offers and admission to trading engage the EMT issuer requirements, subject to the Regulation’s specific exceptions. (Regulation (EU) 2023/1114, art. 48.)

The European Securities and Markets Authority’s (ESMA) opinion of 8 October 2026 also addresses crypto services involving non-compliant stablecoins. It distinguishes public-offer rules from the provider’s duty to act in clients’ best interests, and expects national authorities to require cessation across services, including custody and transfer. Its limited arrangements for disposing of pre-existing holdings do not support starting this new supplier-payment route. Client acknowledgments cannot cure the identified structural inconsistency. (ESMA, Opinion ESMA75-113276571-1742, 8 October 2026, paras. 7, 12–14, 19 and 21–27.)

That opinion is supervisory guidance, not a new legislative ban on private token ownership. Its distinction still prevents reliance on a broad claim that any foreign stablecoin can freely pass through an EU custodian or off-ramp. The proposed approved-token list should require the relevant issuer, whitepaper and service permissions and exclude a token that fails that assessment. (Regulation (EU) 2023/1114, arts. 48 and 66(1); ESMA, Opinion ESMA75-113276571-1742, paras. 23–27.)

AML, sanctions and transfer data can stop execution

The Brazilian provider, Luxembourg bank and French issuer must perform their applicable customer, beneficial-owner and transaction checks. The payment file should identify the goods, parties, invoice, source of funds and commercial purpose, and resolve material inconsistencies before funding. Suspicion can require reporting and restrictions on execution; a mandatory asset freeze cannot be displaced by the invoice deadline. (Lei 9.613/1998, arts. 9–11; Lei 13.810/2019, arts. 6 and 8–11; Luxembourg Law of 12 November 2004, arts. 2–5; Code monétaire et financier, arts. L.561-5–L.561-8, L.561-15–L.561-16 and L.562-4.)

The EU Transfer of Funds Regulation requires prescribed information for covered transfers through an EU provider. Its crypto-transfer definition requires a provider acting for an originator or beneficiary; specified transfers on providers’ own accounts are excluded. The bank’s principal purchase therefore requires assessment of the actual transfer mandates before funding. The payment file should identify the buyer as token originator, the bank as intended token recipient and the supplier as the later USD recipient. Those identities must remain clear in the bank’s accepted compliance instructions, including where its principal receipt falls outside the crypto-transfer definition. For a covered transfer, the required information must pass securely with the transfer; it need not appear on a public ledger. (Regulation (EU) 2023/1113, arts. 2(1), 2(4), 3(10), 3(15), 3(21)–(22), 14 and 16–17.)

An address linked to an equivalent third-country provider is not automatically self-hosted. For a covered transfer involving a self-hosted address, information duties apply across amounts; the EUR 1,000 threshold triggers an additional ownership or control assessment. Transfers between two providers are not automatically exempt where one acts for a customer. Missing or unreliable information can cause rejection, return, suspension or a request for further information. (Regulation (EU) 2023/1113, arts. 2(4), 3(20), 14(5), 16(2) and 17.)

Sanctions screening must cover the applicable legal regimes, actual counterparties and relevant wallets. USD correspondents and the token issuer can also impose contractual screening restrictions. The cure procedure should require prompt notice, lawful escalation and preservation of records. It must not instruct a new wallet or route to evade a freeze. A provider outage, de-peg or redemption delay does not automatically meet French law’s force-majeure test or prove that the invoice has been paid. (Code civil, arts. 1217–1218; Circle, USDC White Paper, D.1.)

The payment clause and stop conditions

The signed invoice addendum should contain the following commercial terms. These terms define the proposed allocation; the providers’ agreements must support the obligations they undertake.

1. Identify the buyer, supplier and every provider by legal entity, with the invoice number and the capacity of each recipient. State that USD 75,000 remains due until the supplier’s designated account receives the agreed available USD credit, net of charges. Record how accepted partial payments reduce the balance.
2. Fix France as the contractual place of payment, the due date, time zone, banking cutoffs and evidence of availability. Use French law, an express CISG exclusion and an agreed Paris forum for buyer–supplier disputes. Keep issuer and provider terms separately identified.
3. Approve the exact token, issuer arrangement, network and native contract. Authenticate wallet and bank instructions through verified company authority and a second channel. Require the same controls for changes, and identify the persons who hold keys or can instruct a custodian.
4. Record the BRL funding amount, executable exchange rates, rate direction, quotation time, expiry, rounding, slippage limit and gross-to-net calculation. Allocate network, dealer, redemption-operation, correspondent and payout costs. Set a top-up mechanism for any shortfall without assuming a secondary sale occurs at par.
5. Specify the technical confirmation condition, internal custody credit where relevant, ownership-transfer event and legal discharge event separately. State whether an intermediary receives for the buyer or is expressly authorised to accept payment for the supplier. An operational nomination should not imply debtor substitution.
6. Allocate wrong-token, wrong-chain, address-error, de-peg, pre- and post-receipt freeze, failed-conversion and insolvency losses. Preserve defined warranties about title and lawful source. A fixed provider payout promise must identify its payment deadline, exclusions and recourse.
7. Require immediate incident notice to the extent legally permitted and a defined cure period, followed by lawful fiat payment if the supplier remains unpaid. Record treatment of held tokens, returned funds and later recoveries so that the supplier does not recover the same debt twice. Keep an escalation and dispute process with responsible contacts and documentary evidence.

For the preferred route, do not fund until the Brazilian provider’s full permission supports both the crypto activity and FX leg. Any proposed transitional alternative needs a separate assessment of its actual permitted activities and safeguards. Stop if the gross transfer exceeds the applicable limit, the disclosed-principal structure fails the third-party funds restriction, or the arrangement is an eFX service attempting prohibited token settlement. (Resolução BCB 277/2022, arts. 29, 49–50 and 76-A; Resolução BCB 520/2025, art. 88.)

Stop if the bank has not accepted the buyer, corridor, token, chain and third-party USD beneficiary under enforceable terms. The provider’s public product description cannot fill those contractual conditions. An unresolved wallet mismatch, missing transfer data, sanctions restriction, active issuer stress restriction or expired executable quote is also a stop condition. (Regulation (EU) 2023/1114, arts. 59–60, 70(4) and 77; Regulation (EU) 2023/1113, art. 17.)

If a lawful, documented stablecoin route cannot deliver the required USD receipt by the deadline, use an authorised bank FX and fiat-transfer route. That fallback preserves the invoice’s payment asset and avoids forcing the supplier to assume an exposure it did not accept.

Reconciliation and an invoice denominated in euros

The supplier needs its invoice and signed addendum, authenticated payment instructions, the provider’s execution statement and its own bank credit advice. The file should reconcile BRL funding, token quantity, exchange proceeds, every fee and net invoice credit. A bank payment reference should connect the payment to the invoice; the supplier’s receipt confirms the final allocation. A blockchain hash belongs alongside that evidence, not in place of the agreed receipt. (Code civil, arts. 1342-8, 1342-10 and 1353.)

A supplier accepting tokens also needs wallet or custody evidence, the acceptance timestamp, token quantity and agreed valuation, and subsequent disposal or redemption records. The parties should obtain separate advice on recognition, token classification and valuation, FX gains and losses, VAT and customs, Brazilian taxes and transaction reporting, and each entity’s accounting standards. The payment design does not determine those treatments.

For a EUR invoice, the recommended clause instead requires the full net EUR amount in the supplier’s EUR account. Using a USD token adds a USD/EUR conversion that must be priced and allocated before receipt. A supplier expressly accepting USDC against a EUR invoice must agree either a fixed quantity or an EUR valuation rule and who bears later currency movement. A euro-referenced token would require its own issuer, redemption, network and provider assessment.

If the supplier insists on fiat, the signed clause should retain fiat as the discharge asset throughout. Token receipt by the platform or off-ramp remains part of the buyer’s execution chain, and the buyer’s obligation continues until the agreed fiat receipt or another expressly accepted method of extinguishment. (Code civil, arts. 1193, 1342 and 1342-4.)