How To Use Crypto For B2B Payments?
To use crypto for B2B payments you agree the asset and network in the contract, invoice with a payment window and exact wallet details, confirm receipt on-chain, convert or hold, and record the fiat value at transfer. Below: the seven steps in order, plus a payment-terms clause you can paste straight into an agreement.
Key takeaways
Fswap covers step six — turning a received payment into the asset or chain you actually need: 4,300+ crypto pairs, no registration, a fixed or floating rate quoted before you send, on the web or in a Telegram mini app, with public API docs at docs.fswap.io.
The invoice must name the exact stablecoin and the exact network. The same ticker exists on several chains, and a payment sent on the wrong one is unrecoverable — this is the single most common operational loss in B2B crypto.
Real settlement cost typically runs below 1%, though businesses surveyed expected around 3% — the gap is why finance teams often reject the idea before pricing it (Paybis at Money20/20, Jun 3, 2026).
US accounting rules changed: under ASU 2023-08, in-scope crypto is measured at fair value with gains and losses in net income, effective for fiscal years beginning after December 15, 2024 — but payment stablecoins fall outside that scope, which simplifies the books for most B2B payers (Grant Thornton on ASU 2023-08).
Crypto received and converted to cash "nearly immediately" — within hours or days — is reported in operating activities on the cash flow statement, so a fast conversion policy keeps the presentation clean (Grant Thornton on ASU 2023-08).
Cross-border B2B stablecoin value is forecast to rise from $13.4 billion in 2026 to $5 trillion by 2035, so counterparties asking for this option will become normal rather than unusual (Juniper Research, Apr 27, 2026).
In this article
What you need in place before the first payment
Four things, none of which take long, and all of which are painful to arrange after money is already in flight.
A wallet you control, with a written rule for who holds the keys and a multi-signature requirement above a threshold you set.
A named asset and network agreed with the counterparty — not "USDT", but "USDT on TRON" or "USDC on Base".
A conversion route decided in advance: what happens to funds on arrival, and who executes it.
An accounting rule: the fiat value is recorded at the moment of transfer, and the transaction hash is stored with the invoice.
Note what is not on the list: an exchange account. You need one only if you intend to cash out to fiat, and even then only at the point of cash-out — not to receive, hold or convert between crypto assets.
How to use crypto for B2B payments in 7 steps
Agree the terms in writing. Asset, network, who pays the network fee, the payment window, and what happens if the transfer arrives short or late. The clause below covers all five.
Exchange and verify wallet details out of band. Send the receiving address by one channel and confirm it by another — a call, a signed document. Address-swap fraud in email threads is the most industrialized attack in this space.
Issue the invoice. Price in fiat, state the crypto amount, name the network, and set an explicit payment window. Fields are listed in the next section.
Run a test transfer for a new counterparty. A small amount, confirmed on a block explorer, before the real invoice moves. Once is enough per address.
Send or receive, then confirm on-chain. Treat the payment as settled only when the required confirmations are in and the amount matches — not when someone sends a screenshot.
Convert or hold, per policy. Move the funds into whatever the treasury policy calls for, on the chain you need them on — a non-custodial swap such as Fswap does this in one step, with no account to open.
Book it and reconcile. Fiat value at transfer time, transaction hash filed against the invoice, and the same sanctions screening you run on wire payments.
Steps one through four are one-time work per counterparty. After that a payment is steps five to seven, which take minutes.
The payment-terms clause to put in the contract
Most disputes come from things nobody wrote down. This covers the five that actually recur — adapt the bracketed values with your counsel.
Digital asset settlement. The Parties agree that invoices under this Agreement may be settled in [USDC] transferred on the [Base] network to the wallet address designated in writing by the receiving Party and confirmed by a second channel. Amounts remain denominated in [USD]; the crypto amount payable is determined at the rate quoted on the invoice and is valid for [24] hours from issue, after which the paying Party shall request a reissued invoice. The paying Party bears all network transaction fees, and the amount received by the receiving Party must equal the invoiced amount net of such fees. Payment is deemed made when the transfer has received [the network's standard number of] confirmations and the full amount is available in the designated wallet. A transfer sent to an address or on a network other than those designated is not a valid payment and does not discharge the obligation. Either Party may change its designated address by written notice confirmed through a second channel, followed by a test transfer.
Two clauses carry most of the weight. "Net of fees" stops the recurring argument about who absorbed the gas. And the wrong-network sentence puts the loss where it belongs — on the party that ignored the agreed chain.
What a crypto invoice must contain
A crypto invoice is an ordinary invoice plus five payment-specific fields. Everything else — business names, invoice number, issue and due dates, line items, totals, terms — stays exactly as it is.
Field | What to write | Why it matters |
|---|---|---|
Asset | The exact token, e.g. "USDC (Circle)" | "Stablecoin" is not an instruction; issuers differ in reserves and jurisdiction |
Network | The exact chain, e.g. "Base", "TRON (TRC-20)" | Wrong-network transfers are the main cause of permanent loss |
Receiving address | Full address, plus memo or tag where the chain requires one | A missing memo on chains that use them can strand the payment |
Amount and rate validity | Fiat total, crypto amount, and how long the quoted rate holds | Without a window, a delayed payment arrives short of the invoice |
Fee treatment | "Network fees payable by sender; amount received must equal total" | Removes the most common short-payment dispute |
The five fields that a fiat invoice does not have. Everything else on the document is unchanged.
If you invoice in a stable-value asset, the rate window matters less than most people expect; if you accept a volatile asset, keep it short and consider locking the rate at conversion — the mechanics are covered in our guide to fixed versus market rate.
What to do the moment funds arrive
Three things, in order: verify, convert, record.
Verify means checking the transaction on a block explorer yourself — sender, amount, network, confirmations — and matching it to the invoice number in your own records. A payment notification from a counterparty is not verification.
Convert is where funds usually sit longer than they should. Payments rarely arrive in the exact asset or on the exact chain the business needs next: a client pays on one network, a supplier invoices in a different stablecoin, and the treasury policy may call for something else again. The reflex is to open a business account on an exchange, deposit, trade and withdraw, which leaves corporate funds on a third party's books for days.
Fswap does that conversion as a single crypto-to-crypto swap — 4,300+ pairs, no registration, a fixed or floating rate shown before you send, payout on the network you choose, on the web or in a Telegram mini app. Nothing is held afterward, so fewer intermediaries collect your data, and teams that want the step inside their own systems can build against the public API documentation at docs.fswap.io. It converts between crypto assets only; it does not issue invoices, hold balances, or handle fiat.
Record is covered next, and it happens the same day — not at month-end.
Accounting and reconciliation
The reporting picture in the US changed with ASU 2023-08, effective for fiscal years beginning after December 15, 2024. In-scope crypto assets are now measured at fair value with remeasurement gains and losses in net income, presented separately from other intangible assets, with disclosure of name, cost basis, fair value and units for each significant holding.
The useful detail for B2B payers: payment stablecoins that provide enforceable rights to underlying assets fall outside that scope. If your policy is to receive and hold stablecoins rather than volatile assets, you avoid most of the fair-value machinery. And crypto received as consideration and converted to cash nearly immediately — hours or days — is reported within operating activities on the cash flow statement, which is a further argument for a same-day conversion policy.
Whatever the framework, the operational rule is the same: capture the fiat value at the timestamp of the transfer, keep the transaction hash attached to the invoice, and reconcile wallet activity against the ledger on the same cycle you reconcile the bank account. Talk to your accountant about which standard applies to you — none of this is tax or accounting advice.
Mistakes that cost real money
Accepting an address from an email thread. Always confirm through a second channel. This one attack accounts for more B2B crypto losses than every technical failure combined.
Leaving the network unspecified. "Send USDT" invites a transfer on whichever chain is cheapest for the sender, which may not be one you can receive on. Network fees also differ by an order of magnitude — see our comparison of gas fees across networks.
Treating an exchange account as a treasury. An exchange is a venue for a transaction, not a place to keep working capital; the distinction is laid out in our guide to custodial versus non-custodial exchanges.
No rate window on the invoice. Without one, a payment made three days later arrives at a different value and the shortfall becomes an argument.
Skipping sanctions screening. Crypto rails change the settlement mechanism, not your compliance obligations. Screen counterparties exactly as you would for a wire.
Reconciling at month-end. On-chain records are permanent but not self-explanatory. A hash without an invoice reference is an unidentified receipt in ninety days.
FAQ
How do you use crypto for B2B payments?
Agree the asset and network in the contract, exchange wallet details through two channels, issue an invoice with a rate window and fee terms, run a test transfer with a new counterparty, confirm receipt on-chain, convert or hold per policy, then record the fiat value and the transaction hash against the invoice.
Do I need an exchange account to accept B2B crypto payments?
Not to receive, hold or convert between crypto assets — a wallet you control is enough, and a non-custodial swap handles conversion. You need an exchange or payment provider only when converting to fiat and moving money into a bank account.
Which stablecoin and network should we use for invoices?
Pick a stablecoin whose issuer is authorized in your jurisdiction, and a network both sides can send and receive on. Name both on the invoice and in the contract — the network determines the fee and confirmation time, not the token.
Who pays the network fee on a B2B crypto payment?
Whoever the contract says. The workable default is that the sender pays fees and the amount received must equal the invoiced total, which removes the most common short-payment dispute.
How are crypto B2B payments taxed and accounted for?
Under US GAAP, ASU 2023-08 requires in-scope crypto assets to be held at fair value through net income for fiscal years beginning after December 15, 2024, though payment stablecoins fall outside that scope. Record the fiat value at transfer time and keep the hash with the invoice; confirm treatment with your accountant.
What happens if a payment is sent on the wrong network?
It is usually unrecoverable. That is why the network belongs on the invoice and in the contract, and why a small test transfer to any new address is worth the five minutes it takes.
Conclusion
B2B crypto payments are a process problem, not a technology problem. Write the asset, network, fee treatment and rate window into the contract, confirm addresses on a second channel, test before you send anything large, and decide in advance what happens to funds the moment they land. Do that and the payment itself takes minutes and costs a fraction of a wire.
Need to convert a received payment into another asset or chain without opening a business account? Get a live quote on Fswap — 4,300+ pairs, fixed or floating rate, on the web, in Telegram, or through the API.
其他文章
