B2B stablecoin payments

Stablecoin payments in business. The real issue is proof and reconciliation.

How to receive USDC or EURC with a clean process for the invoice, the proof, the reference value and the accounting.

Updated on 2 March 2026·By Julien·See all guides

TLDR

The issue is not only getting paid in stablecoins. The issue is making the flow usable on the finance side.
The real risk in business is operational, not technical.
A clean pilot limits variables. One stablecoin. One network. One method for proof and reconciliation.
The key point is proof. One invoice. One payment. One link. One reference value. One standard file.
Custody makes the pilot simpler. Non-custody requires security discipline.
MiCA provides the EU-wide framework. Provider status, accounting treatment, tax rules and record-keeping still need to be checked locally in each country. [1] [14]

Starting decisions

Decision	Recommended pilot choice	Why
Stablecoin	USDC or EURC only	Short list, issuer risk can be documented [9]
Network	One single network supported by the provider	Fewer mistakes, simpler proof
Safekeeping	Custody at the start	Team rights, exports, logs, continuity
Conversion	Immediate above a threshold	Lower exposure to depeg and issuer risk
Thresholds	Dual approval above €10,000	Reduces human risk on material amounts

This guide is not for you if

You only do simple domestic payments in the euro area, with no payment friction.
You do not have the ability to produce clean proof and archive it.
Your business requires reversible payments.
You refuse both custody and the setup of a minimum internal control.

Why companies are getting into it
What stablecoin means for a finance team
The 5 decisions before the first payment
The clean process in 9 steps
The proof to keep
Risks and controls
Custody vs non-custody
Conversion and treasury
EU framework
7-day pilot plan
Frequently asked questions
From the guide to implementation
Conclusion
Appendix A. Full checklist
Appendix B. Proof file model
Appendix C. Glossary
Sources

An international client wants to pay a €50,000 invoice. They propose USDC or EURC. They can pay today. Your finance team blocks it. They do not know what to treat as proof. They do not know how to validate an address. They do not know which documents to produce for accounting.

You have two options. Refuse and lose revenue. Or accept and improvise on the finance and accounting side.

This guide is here to build a third option. A framed pilot. A simple rail. Minimum controls. A repeatable proof package and clean reconciliation.

Unless stated otherwise, this guide follows an EU-first approach. Accounting, tax, record-keeping and reporting rules should then be validated locally with your accountant or counsel in the country where your business operates.

What you need to obtain at the end

A simple method to link one invoice, one payment, one hash and one reference value.
A standard proof file, reusable and archivable.
A clear rule on the stablecoin, the network, the conversion and the thresholds.
A workflow that your finance team or firm can accept.

If you want to go straight to implementation, see the SettleOps offers or book a 15-minute call.

Why companies are getting into it

Reducing international friction

On some corridors, cross-border payments remain costly and hard to read. The topic is tracked at international level because the goals for cost, speed and transparency are not being reached everywhere. [11] [12]

A stablecoin can reduce friction when the client is already on that rail. You do not replace the bank. You add a settlement method.

Settlement timing

A transaction becomes visible quickly, time-stamped and publicly verifiable. That is useful when the client wants immediate proof. It is also useful to record receipt without waiting for a bank statement.

Access to crypto-native clients

Some clients have treasury natively on-chain. SaaS, gaming, web services, crypto actors. For them, paying in stablecoins is sometimes the standard mode. Refusing can slow the sale.

Alternative when banking rails are slow or expensive

Cut-off times, controls, correspondent banks, unexpected fees. A stablecoin is not a universal solution. But it can become a useful plan B.

Cases where it does not make sense

Simple domestic payments in the euro area already covered by instant transfer
Organisation too small to produce clean proof
Activity that requires reversible payments
No international need, therefore no real gain

What the word stablecoin means for a finance team

Receive, hold, convert

Receiving means an asset lands on an address controlled by the company, or by a provider acting for it. Holding means you keep that asset in treasury, even for a few days. Converting means you sell that asset for bank euros or bank dollars.

Many failures come from confusion. The team says “payment” while mixing receipt, conversion and holding.

Market risk and operational risk

The market risk is meant to stay low, but it is not zero. USDC briefly depegged in March 2023 during the banking stress around SVB. [10]

The main business risk is often operational. Wrong address. Wrong network. Fraud through address change. Loss of wallet access. Incomplete proof file.

Issuer and reserves

A stablecoin means an issuer, a framework and reserves. Circle publishes transparency elements and indicates that Deloitte has been its independent auditor since the 2022 financial year. [9]

Simple finance objective. Document the issuer choice. Update that file on a fixed basis, for example every quarter.

The 5 decisions before the first payment

1. Which stablecoin

Start with a short list. Maximum two assets.

EURC if you invoice in euros and your clients are mainly in Europe
USDC if your flows are global or denominated in dollars

Pilot rule. Anything not on the list is refused.

2. On which blockchain

The number one criterion is not the cost down to the cent. It is reducing human risk.

Network supported by your provider and your exports
Simple proof tools, stable explorers
Adoption among your clients
Predictable fees

One single network for the pilot.

3. Who holds the keys

Two models. Custody through a provider, or non-custody with the keys held internally. Also decide governance. Who initiates. Who validates. Who observes.

4. Conversion policy

Decide before the first invoice. Immediate conversion, periodic conversion or capped partial holding.

5. Thresholds and refusal rules

Set simple limits. Maximum amount per invoice in the pilot, excluded countries and counterparties, suspension rule if there is an anomaly, rule on origin and consistency of the payer.

Useful default pilot values. Dual approval above €10,000. Maximum holding period 7 days. Holding cap 5% of available treasury. Immediate conversion above €25,000.

The clean process in 9 steps

Step 1. Scoping

One page is enough. Use case, countries, estimated monthly volume, invoicing currency, authorised asset and network, conversion policy, thresholds and refusal rules.

Step 2. Rail choice

Company wallet or provider. Strong authentication, named access, least-privilege principle, action logs and emergency access procedure.

Step 3. Invoicing

The invoice stays in the currency of your accounting, usually EUR. Add the accepted stablecoin, the accepted network, the receiving address, the invoice reference and a note on irreversibility and the required network.

One address per invoice. Useful for reconciliation. Simple when the custody provider generates addresses automatically. In non-custody, avoid this during the pilot.

Step 4. Internal validation

Anti-fraud control against address change. One person prepares the address. Another checks it against the internal source of truth. The validation is archived. Any address change is treated as an incident.

Step 5. Receipt

Define a confirmations rule. Some platforms explain this principle as a security measure before crediting a deposit. [5] On Polygon, some actors wait for 128 blocks before allowing certain actions. [6] The important thing is to have a written and stable rule.

Step 6. Proof

At the moment when you consider the invoice paid, capture the transaction hash, the timestamp, the source address, the destination address, the amount, the network and a time-stamped screenshot of the explorer or an export from the provider.

Step 7. Optional conversion

If there is conversion, document who triggers it, where, when, why and which proof is produced. Add an automatic trigger if the exposure goes above the defined threshold.

Step 8. Accounting reconciliation

Goal. One invoice. One payment. One link. Mapping from invoice to hash, wallet or provider export, conversion documents and a rate source if needed.

The ECB publishes euro reference rates for information purposes only, so your firm should define the valuation method and supporting evidence actually used in your jurisdiction. Accounting treatment must be validated locally based on the country where the entity operates. [4]

Step 9. Archiving and audit trail

One standard file per invoice. Always the same structure. Record-retention periods depend on local law, so define a documented retention rule for each operating country. For France, accounting records and supporting documents are generally kept for ten years. [3] [8] See Appendix B for the folder model.

Full 20-point checklist. See Appendix A.

Proof to keep

Invoice and settlement terms
Proof of the receiving address communicated
Proof that the receiving address was checked
Hash and time-stamped capture
Wallet or provider export
Conversion proof if there is conversion
Source of the rate used if needed
Internal validation log
Incident notes if there is an anomaly

Model folder tree per invoice. See Appendix B.

Risks and controls. The minimum viable version

Address mistakes

Control. Dual internal validation. Test on a small amount for a new payer.

Wrong network

Control. One single network in the pilot. Explicit mention on the invoice. Refusal of any variation.

Phishing and the crypto version of false bank details

Control. Secondary channel required to confirm any change. No change without dual validation.

Depeg

USDC dropped below one dollar during the SVB crisis before coming back. [10] Control. Clear conversion policy. Exposure cap. Written exit plan.

Issuer risk

Control. Internal issuer file. Archived attestations. Quarterly review. [9]

Sanctions and origin of funds

Control. Proportionate vigilance. Screening if volumes justify it. Clear refusal policy.

Custody vs non-custody

Custody

Advantages. Simpler setup. Team rights management. Exports and logs. Limits. Dependency. Fees. Possible freezes if alerts appear.

Non-custody

Advantages. Direct control. Flexibility. Limits. Higher human risk. Business continuity must be organised internally.

Pragmatic recommendation. Start with custody if you do not already have an internal security discipline. Move to a more autonomous model once the pilot is under control.

Conversion and treasury

Three possible policies. Immediate conversion, periodic conversion, capped partial holding.

Define a clear rule before the first payment. Exposure cap, maximum holding period and exit trigger if parity diverges or if a major public event occurs.

EU framework. Key points

MiCA applies in two phases. Rules for asset-referenced tokens and e-money tokens have applied since 30 June 2024, and the broader regime has applied since 30 December 2024. [1] [14]

For an EU business, the practical point is simple. Work with providers whose regulatory status is clear, documented and current. ESMA maintains the interim MiCA register, which should be part of your provider due diligence. [2] [14]

If your flow involves e-money tokens used in a way that overlaps with payment services, also check the provider's position on the MiCA and PSD2 interplay. EBA has published guidance on this point. [13]

MiCA does not replace local accounting, tax, record-keeping or invoicing rules. Those remain country-specific. If your business operates across borders, keep an eye on the EU's broader VAT and e-invoicing timeline as well. [7]

France-specific note. If your entity is based in France, also review the AMF, ACPR and ANC guidance in addition to the EU framework. [15] [16] [17]

7-day pilot plan

Day 1. Scoping. Asset, network, provider, conversion, thresholds.
Day 2. Access setup. Roles, strong authentication, logging.
Day 3. Invoice template. Notes, one network, address, irreversibility rule.
Day 4. Validation workflow. Anti-address-change. Dual approval threshold.
Day 5. Tests. Correct payment. Partial payment. Wrong network. Address change.
Day 6. Proof and exports. Standard file. Test reconciliation. Test conversion out to euros.
Day 7. Review with accounting, then launch on a pilot client.

Frequently asked questions

Is it legal

Yes if the parties agree. The key issue remains the process, the proof and the choice of compliant providers.

Is it taxable

Revenue remains taxable as usual. The tax treatment of holding and any gains or losses depends on the company regime. Validate it.

What if the stablecoin depegs

That is a real risk. It is managed through a conversion policy, an exposure cap and an exit plan. [10]

What if we use the wrong address

Often irreversible. Dual control. Small-value test. One single network.

How do we prove the payment

Hash, time-stamped capture, provider export and a clear mapping back to the invoice.

Do network fees reduce the amount received

Usually not. Network fees are paid by the payer in the native token. The risk is more often the wrong amount being sent.

Do we need KYC

You need to know your clients according to your risk policy. Strict obligations mainly sit with providers.

How many confirmations should we wait for

It depends on the network and the amount. What matters is having a stable written rule that is actually applied. [5]

Can an EU business get paid in stablecoin

Yes, if the client can send it and your chosen rail supports it. The practical treatment then depends on your local accounting, tax and compliance framework, which should be validated in the country where the entity operates.

Who should have access to the wallet

Not everyone. Named access. Separated roles. Dual approval above a threshold.

Does MiCA change anything for us

Yes. MiCA changes provider authorisation, disclosure, supervision and market access across the EU. For businesses, the key impact is choosing providers with clear regulatory status and updating internal procedures accordingly. [1] [2] [14]

How long should we archive records in Europe

Retention periods depend on local law. Define a documented retention rule country by country. Retention requirements vary by EU country — typically between 7 and 10 years. [France] Accounting records and supporting documents are generally kept for ten years. [3] [8]

From the guide to implementation

Reading a guide is not enough. At some point, you need to freeze a first workflow, choose the right thresholds, prepare the proof and decide what your firm must receive.

SettleOps supports exactly that step through two simple formats.

Simple Pilot. For a first well-framed flow, often an agency, a studio or a small service business.
Structured Pilot. For several flows, several stakeholders or a more advanced finance need.

See the offers · 15-minute call

Conclusion

Stablecoin reduces friction when the client is already on that rail.
The pilot must limit variables.
The number one risk is human error.
Address validation is an anti-fraud control.
Proof must be standardised.
Conversion is decided before the first payment.
Custody or non-custody depends on your operational maturity.

Recommendation by profile

SME without a dedicated finance team. Custody. Fast conversion. Low thresholds. Limited pilot.
SME with structured accounting. Custody or non-custody depending on skills. Dual approval. Monthly review.
Company with treasury and controls. Hybrid model possible. Capped partial holding. Monitoring. Incident procedures.

Disclaimer. This guide is operational. It does not constitute tax, legal or financial advice. Validate it according to your country, your activity and your firm.

Before launching

If you have a first USDC or EURC payment to receive and you want to avoid improvisation, a 15-minute call is enough to validate your case and choose the right setup.

Appendix A. Operational checklist

20 points to validate before launching. See the 9-step process for the context of each one.

Use case defined and limited
Allowed assets listed, maximum two
One single network in the pilot
Provider chosen and tested. Exports and logs validated
Named access. Strong authentication enabled
Separated roles. Initiate and validate
Dual approval threshold defined
Written address-change procedure
Invoice template validated and frozen
Confirmation rule defined and written
Delivery-after-receipt rule defined
Proof-on-receipt procedure defined
File naming convention defined
Conversion policy decided
Exposure cap and holding period defined
Rate source documented if needed
Country and counterparty refusal policy defined
Proportionate screening defined
Conversion-out to euros tested
Compliant archiving. Duration defined

Appendix B. Proof file model

One structure per invoice. Always the same one. Adapt the names to your internal naming convention.

Clients/
  CLIENT_NAME/
    2026-03/
      INV_2026-0312/
        01_Invoice.pdf
        02_Receiving_address_and_validation.pdf
        03_Address_control_proof.pdf
        04_TxHash_timestamped_capture.pdf
        05_Wallet_or_provider_export.csv
        06_Conversion_slip.pdf
        07_Rate_source.pdf
        08_Internal_validation_log.pdf
        99_Incident_notes.txt

Appendix C. Glossary

Only the terms used in this guide.

Stablecoin. Crypto-asset designed to track the value of a reference currency, here the euro or the dollar.
USDC. Stablecoin pegged to the US dollar, issued by Circle.
EURC. Stablecoin pegged to the euro, issued by Circle.
Wallet. Tool that controls a blockchain address and signs operations.
Custody. Safekeeping operated by a third-party provider that holds the keys on behalf of the company.
Non-custody. Safekeeping operated directly by the company, which holds its own keys.
Transaction hash. Public unique identifier of a blockchain transaction.
Confirmations. Number of blocks added after a transaction. Used as a practical finality rule before a payment is treated as definitive.
Network fees. Cost paid by the payer for inclusion of the transaction in a block. Usually without impact on the amount received.
Depeg. Temporary or lasting break in the parity of a stablecoin against its reference currency.
MiCA. European regulation on markets in crypto-assets. Frames the issuance of stablecoins and crypto-asset service providers in the EU.
EMT. Electronic money token. MiCA regulatory category that includes USDC and EURC.
PSAN. Former French national regime for digital asset service providers. This is France-specific and should not be treated as the default framework for the EU.

Sources

Core EU and international sources

[1] European crypto-assets regulation MiCA. EUR-Lex summary of Regulation (EU) 2023/1114. Consulted in March 2026. eur-lex.europa.eu
[2] Interim MiCA Register and Databases and Registers. ESMA. Consulted in March 2026. esma.europa.eu
[4] Euro foreign exchange reference rates. European Central Bank. Consulted in March 2026. ecb.europa.eu
[5] Cryptocurrency deposit processing times. Kraken Support. Consulted in March 2026. support.kraken.com
[6] Polygon Confirmations. IDEX Docs. Consulted in March 2026. docs-v3.idex.io
[7] VAT in the Digital Age package. European Commission. Adopted on 11 March 2025 and rolled out progressively until January 2035. taxation-customs.ec.europa.eu
[9] Transparency and Stability. Circle. Consulted in March 2026. circle.com
[10] Circle reveals exposure to Silicon Valley Bank as USDC breaks peg. Reuters. 11 March 2023. reuters.com
[11] Moving on up. Results of the 2024 cross-border payments monitoring survey. CPMI BIS. 18 December 2025. bis.org
[12] G20 Roadmap for Enhancing Cross-border Payments. FSB. 9 October 2025. fsb.org
[13] Asset-referenced and e-money tokens under MiCA, including the Opinion on the interplay between PSD2 and MiCA in relation to CASPs that transact e-money tokens. EBA. Consulted in March 2026. eba.europa.eu
[14] Markets in Crypto-Assets Regulation MiCA. ESMA. Consulted in March 2026. esma.europa.eu

France-specific note

[3] Article L123-22 of the French Commercial Code. Légifrance. Consulted in March 2026. legifrance.gouv.fr
[8] Record retention periods for businesses. Entreprendre Service Public. Consulted in March 2026. entreprendre.service-public.gouv.fr
[15] AMF reminder that the transitional period for PSANs ends on 1 July 2026. AMF. 5 February 2026. amf-france.org
[16] ACPR expectations for the authorisation as a payment institution of providers offering services falling simultaneously under payment services and crypto-asset services. ACPR. 19 February 2026. acpr.banque-france.fr
[17] ANC regulations no. 2026-01 and no. 2026-02 of 9 January 2026. ANC. Published on 18 February 2026. anc.gouv.fr