Stablecoins Need a Better Business Case for Payments

A business considering stablecoin payments should start with a question its finance team can answer: which payment problem would this solve better than the current arrangement?

Payments Dive’s October 14, 2026 report highlighted a striking finding: among 148 surveyed businesses, one reported using stablecoins and seven more planned to do so. Payments Dive

The Cleveland Fed published the underlying research on September 28, 2026, using a September 18–25, 2025 regional survey—not a current national measure.

That timing limits what the findings can tell us about adoption today. For banks and payment companies, their more useful application is as a starting point for testing the commercial proposition.

Demand needs evidence

In a multiple-answer question put to 102 respondents, 50 selected customer demand as an adoption factor, 49 wanted more time to observe developments, and 42 wanted evidence of lower costs or greater efficiency.

Those answers describe decision factors, not a verdict on every stablecoin product.

Our reading is that a provider should begin with a customer problem, rather than an assumption that offering another payment method will generate demand. Education can explain how a product works; it cannot substitute for a credible reason to change.

Consider a firm whose existing supplier payments are inexpensive and predictable. A proposal to replace them should demonstrate a benefit large enough to justify integration, staff training and revised controls. The right outcome might be a limited pilot—or a decision that the existing arrangement remains adequate.

Cross-border needs a corridor-level test

Industry consultants quoted by Payments Dive identify cross-border payments as a promising application. That is a proposition to evaluate, not a guarantee of savings. Payments Dive

As background, the Committee on Payments and Market Infrastructures’ October 2023 analysis cautioned that the drawbacks of stablecoin arrangements could outweigh potential cross-border benefits. That older assessment supplies context, not evidence of today’s adoption. Bank for International Settlements

We would evaluate a proposed service against a specific existing route, using the same currencies, transaction sizes and recipient requirements.

The comparison should include conversion charges, foreign-exchange spreads, funding requirements, local payout costs and the effort involved in resolving exceptions. Measure when the recipient can use the required currency, not just when a token reaches a wallet.

For example, a faster blockchain transfer would not solve a supplier’s deadline problem if conversion or local payout remained unavailable when needed. Conversely, a route that delivers usable funds sooner could have value even where its transfer fee is not the lowest.

Both outcomes should be tested rather than assumed.

Regulatory progress is a separate question

The GENIUS Act became law on July 18, 2025, establishing a US framework for payment stablecoins. Its enactment and effective-date provisions are separate.

That legislative milestone is not, by itself, evidence of commercial demand.

A project team should distinguish three assessments: whether its proposed activities are legally permissible, whether the service can operate reliably, and whether customers have a reason to use it. Passing one assessment does not answer the other two.

For a licensing review, begin with an activity map: issuance, custody, conversion, transfer and fiat payout. Ask qualified advisers to assess the relevant entities and jurisdictions against that actual design, rather than treating “stablecoin payments” as a complete regulatory description.

The banking questions belong in the pilot

For correspondent banking strategy, map every point where funds enter or leave bank accounts. Identify the banking relationships, liquidity arrangements and fallback routes needed at either end before assuming that a digital transfer removes those dependencies.

The pilot should also assign responsibility for screening, reconciliation, rejected transactions and customer support. Ask what happens when a provider is unavailable, a recipient cannot receive the asset, or a payment needs to be returned.

A useful design comparison is direct corporate holding versus a provider-managed service that converts into the recipient’s preferred currency. Evaluate both against the customer’s operational requirements; do not assume that willingness to receive a payment implies willingness to manage a new treasury asset.

Start with a defined customer group and a recurring payment flow. Record the existing route’s total cost, time to usable funds and exception rate, then compare the proposed service under normal and disrupted conditions.

The adoption signal worth watching is repeat use supported by a measurable improvement in those outcomes. A successful token transfer alone is not enough to establish the business case.