Stablecoin Payment Agreements for Businesses

By Hank FasthoffSeptember 17, 2026

A supplier agrees to accept 100,000 tokens against a $100,000 invoice. Before the supplier converts them to dollars, their market price falls to $0.97, leaving a sale value of $97,000 before fees. Whether the buyer owes another $3,000 depends on the agreed payment obligation and allocation of that risk.

A stablecoin is a digital token designed to maintain a value relative to a reference asset, such as the U.S. dollar. For a business paying suppliers or collecting commercial invoices, that design leaves several contractual decisions unresolved. The parties should establish which asset they will accept, when payment is complete, and what happens if the expected conversion or transfer cannot occur.

The Currency of the Obligation

For sales of goods governed by Texas law, Business and Commerce Code § 2.304 permits the price to be payable in money or otherwise. The parties can therefore specify the agreed payment medium. A contract allowing stablecoin payment should also identify whether the debt is measured in dollars or a fixed quantity of tokens.

A dollar invoice can permit a specified number of tokens to satisfy the debt, or it can require a token quantity calculated by reference to an agreed dollar value. Those arrangements allocate price risk differently. You should specify the valuation source, calculation time, and treatment of fees if the amount due depends on conversion.

In the supplier example, an agreement accepting 100,000 specified tokens as full payment upon qualifying receipt would allocate a subsequent market decline to the supplier, subject to any agreed exceptions. An agreement requiring the supplier to receive $100,000 after conversion would allocate that risk differently. The invoice, payment instructions, and governing agreement should describe the same obligation.

The Accepted Token and Network

A token name alone can leave the permitted payment method uncertain. The payment instructions should identify the issuer, network, and token identifier used on that network, together with the receiving address and any required routing information. The people administering the payment system can supply those details for inclusion in the agreement or an authorized payment schedule.

A token issued directly on a network can differ from a representation created through a bridge, a system used to transfer value between networks. Circle’s Third-Party Bridged USDC Terms describe locking native USDC in a bridge contract on Ethereum and minting corresponding tokens on another network. Circle disclaims dollar and reserve backing for those bridged tokens and does not issue or directly redeem them. Conversion back to native USDC depends on the supported network and bridge.

That distinction affects what the recipient acquires and the steps needed to obtain dollars. You should state whether bridged or wrapped versions are acceptable and who may approve a substitute token or network. Any approval procedure should address existing invoices and transfers already underway.

When the Invoice Is Paid

A payment can pass through several stages before the recipient has usable funds. The sender submits a transaction, the network records it, a provider credits an account, and the provider may then convert the asset or arrange a bank payout. The agreement should identify the event that discharges the payer’s obligation.

For direct transfers, the parties can specify the required network confirmation, correct destination, and amount received. For payments through a processor, they also need to establish the legal effect of the processor’s receipt. You should address whether the payer has completed payment at that point and which party bears the risk of the processor’s subsequent delay or failure.

Stripe’s stablecoin payment documentation describes customers paying in supported stablecoins, subject to a $10,000 limit per transaction, while completed payments settle in the merchant’s Stripe balance in local currency. The product therefore illustrates processor settlement for smaller payments. A credit to that balance and a payout to the merchant’s bank account are separate events, so you should compare the merchant agreement and customer terms when defining payment completion.

The contract also needs a procedure for short payments, duplicate payments, and transfers received after a quotation expires. An expired quotation can require a new calculation, while a duplicate payment can create a return obligation. Defined procedures allow the parties to reconcile those events against the invoice.

Redemption and Changes in Value

Redemption means exchanging a token with its issuer under the applicable redemption terms. Selling the token through an exchange or another intermediary involves a different counterparty and price. A business expecting to convert receipts into dollars should identify which method it can use before promising a settlement date.

Circle’s USDC terms for holders outside the European Economic Area condition direct redemption on an eligible Circle Mint account in good standing. Its commitment to redeem at $1 per USDC is subject to the applicable terms and fees, and Circle does not guarantee prices on other platforms.

Tether’s USDT, identified as USD₮ in its Token Terms of Sale and Service, also requires a verified customer relationship for direct redemption. Its terms restrict U.S. persons from holding or using Tether tokens, with an exception for Eligible Contract Participants accepted by Tether. That term identifies a category defined under federal commodities law. A U.S. business should confirm its eligibility under the applicable terms before agreeing to use USDT.

Tether’s fee schedule sets a $100,000 minimum for direct acquisition or redemption and a redemption fee of the greater of $1,000 or 0.1%. For an eligible customer redeeming 100,000 USDT at $1 each under that schedule, the redemption fee would be $1,000, leaving $99,000 before any other charges. A payment clause requiring receipt of $100,000 after conversion would therefore need to account for the redemption fee even if the token maintained its intended value.

A payment agreement can address a departure from the intended dollar value through a defined suspension or substitution procedure. The trigger could use an agreed price source, a specified deviation, and a minimum duration. The parties should also identify who provides notice and whether the procedure affects unpaid invoices, payments in progress, or completed payments.

A substitute payment method should have a defined deadline and cost allocation. You should specify whether the original due date applies and who bears conversion losses when the parties switch to bank payment.

Frozen Tokens and Restricted Accounts

Issuer restrictions and provider restrictions can affect different parts of a payment. For native USDC, Circle’s terms reserve authority to block transfers under its blocklisting policy and describe freezes required by legal orders. Tether’s terms, § 2, reserve authority to freeze tokens or suspend services when required by law, when Tether considers it prudent, or following specified violations.

The available controls also depend on the token version and custody arrangement. For the bridged tokens covered by its separate terms, Circle states that it lacks control over the software governing those tokens and cannot freeze stolen tokens through that software. Those terms also reserve restrictions on assets in Circle’s custody. Authority to restrict assets does not promise recovery after theft.

The agreement should allocate responsibilities for a restriction, including notice, information requests, and cooperation with the provider. It should also address responsibility for losses caused by inaccurate information or a party’s breach, and whether either party must make a substitute payment while the original funds are inaccessible. A substitute payment provision needs a reconciliation procedure if the original funds are subsequently released.

Sanctions restrictions constrain those procedures. The Office of Foreign Assets Control states that sanctions obligations apply equally to digital and traditional currency transactions. An alternative wallet, token, or payment provider cannot authorize a prohibited transaction, and any contractual fallback must preserve applicable blocking and other legal requirements.

Incorrect Instructions and Unauthorized Transfers

A payment dispute can begin with an altered invoice or an unauthorized change to a receiving address. The contract can specify which representatives may issue instructions and how the payer must authenticate a change. You should establish a verification procedure that uses previously confirmed contact information and records the authorization.

Responsibility also depends on which party supplied the incorrect information and whether the payer followed the agreed procedure. A clause assigning every transfer error to the sender may conflict with the recipient’s control over payment instructions. The agreement should address cooperation in recovery, allocation of recovery costs, and whether an attempted recovery affects the payment deadline.

The transaction identifier, network, token, amount, and receiving address should be recorded with the invoice and applicable instructions. Those records connect the transfer to the obligation the parties intended to satisfy. Access to provider records should continue through the period in which a payment or refund can be disputed.

Refunds and Commercial Remedies

A refund provision should identify the circumstances requiring repayment and the amount or value to be returned. Returning the original token quantity can produce a different result from returning the invoice’s dollar value. The agreement should establish the calculation method, permitted deductions, and payment date, subject to applicable law.

Provider procedures can limit how a refund is delivered. Stripe’s documentation, for example, states that stablecoin payment refunds return as stablecoins to the customer’s original wallet. A business using that service should account for the procedure when drafting its refund terms and address what happens if the customer reports losing access to that wallet.

The underlying commercial agreement also governs disputes over defective goods, incomplete services, or termination. You should distinguish when the payment obligation is discharged from whether either party has performed the rest of the contract. A completed token transfer does not resolve a claim that the seller failed to deliver what it promised.

The Provider Agreement and Regulatory Scope

The provider agreement identifies which entity receives funds, performs conversion, and owes settlement. Its suspension rights, payout conditions, liability limits, and termination provisions affect whether the business can perform the commitments in its customer or supplier contracts. A promise of payment by a particular date needs comparison with any provider discretion to delay the necessary conversion or withdrawal.

Collecting or transmitting funds for other businesses introduces a separate regulatory question. FinCEN’s guidance on convertible virtual currency, § 4.6, addresses processors that receive virtual currency from customers and transmit value to merchants as money transmitters. A proposed service performing those functions requires a separate assessment of applicable registration, licensing, and compliance obligations before launch.

President Trump signed the GENIUS Act into law on July 18, 2025, establishing a framework for payment stablecoin issuance, including reserve and redemption requirements. Section 20 sets the Act’s effective date as the earlier of 18 months after enactment or 120 days after the primary federal payment stablecoin regulators issue final implementing regulations. Particular provisions also contain transition periods, so a contract review should identify the requirements applicable to the issuer, provider, and transaction at the relevant time.

For an ongoing commercial relationship, you should address changes in law or provider support that prevent use of the agreed payment method. The agreement can specify notice, an authorized substitute, and the treatment of outstanding obligations if no permitted substitute is available. Those provisions belong alongside the ordinary payment terms because a regulatory change can affect performance during the contract.

Before the first invoice is issued, the parties should be able to identify exactly what constitutes payment and who bears each defined risk before and after that event. The agreement should also specify what happens to the debt when tokens arrive late, lose value, become restricted, or must be returned. Those decisions determine whether the chosen payment method fits the commercial bargain.