Stablecoin Payouts From a Merchant Perspective in 2026

The pitch for stablecoin payouts is well rehearsed by now. Instant settlement, low transaction cost, no banking-hours friction, no SWIFT charges, no intermediary banks dropping payments into investigation queues. For a merchant paying out to contractors, affiliates, sellers, or international suppliers, the pitch is genuinely compelling, and the volume of payouts moving through stablecoin rails has grown to a level that makes the rails part of mainstream operational infrastructure rather than an experimental edge.

But the operational reality of running a stablecoin payout function is more nuanced than the pitch suggests. The gains are real and meaningful, but they come with a set of operational disciplines that traditional payout rails do not require, and the failure modes are different from the failure modes that operators of traditional rails are trained to anticipate. This piece documents what running stablecoin payouts looks like from the merchant side after several years of operational maturity.

The first decision is which stablecoin to use, and the choice is more consequential than most operators initially appreciate. The major stablecoins differ along several dimensions: the issuer and the issuer's regulatory standing, the reserves backing the token and the transparency of those reserves, the chains on which the token is available and the implications for transaction cost and speed, and the redemption mechanism and its reliability in stressed conditions.

USDC, issued by Circle, has emerged as the default choice for U.S.-regulated operators because of the issuer's regulatory standing and the transparency of the reserves. USDT, issued by Tether, retains larger market share globally because of broader chain support and broader counterparty acceptance, particularly in markets where Circle's banking relationships are less established. DAI, issued by MakerDAO through a decentralized mechanism, occupies a smaller share but is the choice of operators who prioritize the absence of a centralized issuer. Other stablecoins exist with various tradeoffs. The choice depends on the operator's specific circumstances, but it should be a deliberate choice rather than a default.

For each stablecoin choice, the operator must then choose which chain to transact on. Ethereum mainnet is the most established but the most expensive, with transaction costs that can range from a few dollars to several tens of dollars depending on network congestion. Polygon, Arbitrum, Base, and other layer-two networks offer dramatically lower transaction costs but require the recipient to be set up to receive on the selected chain, which is not universally the case.

The operational pattern that has emerged for most merchant payouts is to use a layer-two network as the default for payouts above a defined size threshold (the threshold at which the recipient's setup cost is justified by the transaction cost saving), and to use a centralized exchange's internal transfer mechanism for payouts below the threshold (which costs nothing but requires the recipient to have an account on the same exchange). The hybrid pattern preserves the cost advantage for large payouts while accepting the operational simplification for small ones.

The largest operational friction in stablecoin payouts is the onboarding of the recipient. Traditional payout rails benefit from the universality of bank account ownership; almost every payee already has the infrastructure needed to receive a traditional payout. Stablecoin payouts require the payee to have a wallet on the relevant chain, to understand the address format, to be able to verify that they have correctly recorded the address for receipt, and to be able to convert the stablecoin to local currency if that is what they ultimately need.

The onboarding friction is solvable but requires investment. The merchants who run stablecoin payout programs successfully invest in documentation that walks the payee through wallet setup, provide white-glove support for the first payout to each new payee, and offer a fallback to traditional rails for payees who cannot or will not complete the stablecoin onboarding. The merchants who do not make this investment frequently produce a payout program that works for some payees and fails for others, with the failures often clustered in exactly the demographics where stablecoin payouts would have been most valuable.

The single largest source of catastrophic loss in stablecoin payouts is sending to the wrong address. A misaddressed transaction is, in almost all cases, irrecoverable. The discipline that prevents this is to verify each address at multiple points: at the moment of recipient setup (through a small test transaction that the recipient confirms receipt of), at the moment of payment scheduling (through a confirmation step that displays the address and the recipient name side by side), and at the moment of payment execution (through a second confirmation that the operator must explicitly approve).

The friction of these confirmations is meaningful but small in absolute terms. The cost of skipping them is dramatically larger: a single misaddressed transaction can wipe out the operational savings from many months of stablecoin payouts. The discipline is non-negotiable for any operator running stablecoin payouts at a volume that justifies the rails at all.

Stablecoin payouts are subject to a regulatory layer that is more developed than most operators initially appreciate. The Travel Rule requires the originating institution to share identifying information about the originator and the beneficiary with the receiving institution for transactions above defined thresholds. The thresholds vary by jurisdiction but are typically 1,000 USD-equivalent in the U.S. and 1,000 EUR-equivalent in the EU.

For a merchant running payouts through a regulated VASP (virtual asset service provider) that handles the Travel Rule compliance on the merchant's behalf, the operational burden is modest. For a merchant running payouts through a self-custodied wallet, the obligations may attach directly to the merchant under the relevant jurisdiction's interpretation of the rules. The discipline is to understand the regulatory posture of the chosen rails in advance, to engage with the VASP's compliance documentation, and to seek legal advice before scaling payouts to a volume that triggers reporting obligations the merchant has not prepared for.

The tax and accounting treatment of stablecoin payouts is more complex than the treatment of traditional payouts, even when the stablecoin remains pegged to the dollar at all relevant times. The tax authority's position in most jurisdictions is that stablecoins are property rather than currency, and a payout in stablecoin is a disposition of property that may produce a taxable event for the merchant even if the underlying value is essentially the same as a dollar payout would have been.

The accounting treatment is similarly more involved. The merchant must record the cost basis of the stablecoin held in inventory, the disposition value at the moment of each payout, and any gain or loss between the two. The accounting systems that handle this well are not the off-the-shelf small-business accounting tools but rather specialized crypto accounting platforms or custom integrations. The operator who plans for this accounting work in advance avoids the year-end surprise of being unable to file accurate returns. The operator who does not plan often discovers the requirement at the worst possible moment.

Stablecoins are stable, until they are not. The depeg events of the last several years have been relatively rare and relatively short-lived, but they have happened, and an operator with significant stablecoin balances on the balance sheet at the moment of a depeg event experiences real economic loss. The discipline that mitigates this is to minimize the duration for which stablecoin balances are held — convert to fiat or to longer-term treasury instruments as soon as the operational need for the stablecoin balance has passed.

The discipline applies to both the merchant's own balances and the timing of payouts. A payout that is scheduled for the end of the week, with the funds held in stablecoin in the interim, exposes the merchant to depeg risk for that period. A payout that is executed promptly upon scheduling, with the stablecoin acquired immediately before the payout rather than held in inventory, eliminates the exposure. The operational pattern of minimizing the inventory duration is the pattern that produces durable stability.

Even the most reliable stablecoin payout rail experiences occasional disruption — chain congestion that produces delayed transactions, an exchange maintenance window that blocks deposits or withdrawals, a regulatory action that temporarily affects a specific rail. The operator running payouts at scale should maintain a documented failover process: the alternative rail to use, the procedure for switching to it, and the communication template for notifying recipients of a delay or a rail change.

The multi-rail discipline is the same discipline that mature operators apply to their inbound payment rails. The benefit is the same: operational continuity through the inevitable disruptions of any individual rail. The cost is modest — the operational overhead of maintaining the secondary relationship and the documentation of the failover procedure. The operator who has the failover ready avoids the operational crisis when the primary rail is disrupted. The operator who has not prepared experiences the crisis at the worst possible time.

The pattern that is emerging in mature operators is steady-state hybrid: traditional rails for the largest payouts (where the per-transaction cost of the traditional rail is amortized over the transaction size), stablecoin rails for the mid-range payouts (where the cost savings are most meaningful and the operational discipline is most justified), and exchange internal transfers for the smallest payouts (where the operational simplification is the dominant consideration). Each rail serves a specific segment of the payout volume, and the operator who configures the routing logic correctly captures the benefits of each rail without paying the costs of the others.

The discipline of treating payouts as a portfolio rather than as a single channel is the discipline that distinguishes mature operators from operators who are still treating stablecoins as either the entire solution or as an experimental sideline. Stablecoins are neither. They are one rail among several, with specific strengths and specific costs, and the operator who has done the work to understand exactly when to use them is the operator who captures the operational gains the pitch promised while avoiding the failure modes that the pitch did not mention.