Crypto Payments Have a Conversion Problem Before They Have an Adoption Problem

A customer can tap a crypto card in Chicago while the merchant receives dollars and never knows a digital asset was involved. That looks like adoption. Operationally, it is a chain of conversions that must work quickly, at a predictable cost, through both calm markets and ugly ones.

That distinction matters one year after a flash crash reportedly erased $19 billion from leveraged crypto positions. CoinDesk reports that liquidity in bitcoin and ether has since rebuilt, while many altcoins remain more vulnerable. For traders, that is a market-structure story. For payment companies, card issuers, remittance providers, and businesses holding crypto receipts, it is a warning about what happens between “pay” and “settled.”

The industry often treats payment adoption as a question of how many merchants, wallets, or cards can access crypto. Access is only the front end. The harder question is whether the infrastructure can reliably convert the asset a customer holds into the asset a merchant, recipient, or bank actually wants.

In the United States, that usually means dollars.

A crypto payment is usually several transactions wearing a trench coat

When someone spends a volatile token through a card, the merchant generally does not want exposure to its price after the sale. The infrastructure therefore has to value the token, sell or hedge it, produce the required dollars, and complete settlement through conventional payment and banking systems.

Those steps can be nearly invisible to the customer. They are not economically trivial.

A payment provider has to manage exchange liquidity, spreads, execution timing, fraud controls, network fees, banking access, and reconciliation. If the customer’s asset trades in a thin market, a nominal balance in an app may not translate into the same amount of spending power once it is converted.

That is where the reported divide between bitcoin, ether, and less-liquid assets becomes relevant. Deep liquidity does not make an asset stable, but it can make conversion more dependable. Thin liquidity can create wider spreads and greater slippage precisely when markets become stressed.

A card interface can hide that complexity. It cannot repeal it.

This also explains why supporting a long list of tokens is not automatically a better payments product. More assets can attract users, but each additional conversion route introduces another market that must remain liquid enough to support real transactions. A token that trades adequately during ordinary conditions may become expensive or difficult to unload during a sudden selloff.

For a payment operator, the meaningful feature is not the length of the asset menu. It is whether the conversion path still works when everyone tries to use the same exit.

Stablecoins simplify the price problem, not the whole payment chain

Stablecoins can remove one obvious source of friction because the payment asset and the merchant’s accounting unit may both be dollars. A business does not need to continually translate a volatile token price into the amount shown on an invoice.

That is useful, especially for recurring payments, supplier transfers, and remittances where the recipient cares about preserving a dollar amount rather than gaining crypto exposure.

But “dollar-denominated” and “equivalent to cash in a bank account” are not interchangeable descriptions.

A stablecoin payment still depends on several layers: the issuer’s redemption process, the blockchain used for transfer, the wallet or custodian holding the asset, and the service responsible for converting it into bank money when needed. Liquidity can also differ across chains and trading venues, even when the token bears the same name.

A recipient may be paid instantly on-chain yet still face a delay moving those funds into a US bank account. Conversely, a payment company may provide customers with an immediate dollar balance while managing the actual conversion later. The user experience says “instant.” The treasury desk sees timing and counterparty exposure.

Stablecoins therefore address unit-of-account volatility better than they address every form of settlement risk. They can make the pipe straighter. They do not eliminate the joints.

Crypto cards move complexity away from the checkout counter

Crypto cards offer one of the clearest examples of how domestic payment infrastructure is changing without requiring merchants to adopt new technology.

The merchant can continue accepting the same card network and receiving its normal settlement currency. The crypto-specific work happens elsewhere, usually between the customer’s account, the card program, liquidity providers, and the institution handling conversion.

That model has a practical advantage: merchants do not need to train staff on wallets, manage private keys, or alter their point-of-sale systems. It also means crypto payment growth can occur without merchants holding crypto or even realizing that a customer funded a purchase with it.

Still, shifting complexity away from the checkout counter does not make it disappear. It concentrates the operational risk inside the providers running the card program.

Those providers need clear answers to basic questions. Which assets can be converted in stressed markets? How is the exchange rate established? When is the customer’s asset sold? Who absorbs slippage between authorization and settlement? What happens when a trading venue, blockchain, or banking partner is unavailable?

These are not edge cases. They determine whether a crypto card behaves like a dependable payment instrument or like a trading account attached to a piece of plastic.

For users, the relevant fee is also broader than the amount labeled “transaction fee.” The real cost can include the trading spread, conversion charge, network fee, card fee, and any tax consequences associated with disposing of an asset. A smooth interface can make those components difficult to see.

Remittances expose a different dollar-liquidity bottleneck

Cross-border stablecoin transfers are often described as a way to move digital dollars without waiting for correspondent banks. That framing captures the transfer itself but can miss the endpoints.

A US sender may have to move money from a bank account into a stablecoin. The recipient then needs a wallet, a usable blockchain connection, and some way to spend the token or convert it into local money. The blockchain leg can be fast while either endpoint remains slow or expensive.

For US-facing remittance providers, domestic dollar liquidity is therefore part of the product. They need reliable access to stablecoins on the way in, bank dollars on the way out, or both. They also need enough inventory to serve customers when demand moves sharply in one direction.

A remittance rail is not finished merely because a token reaches another wallet. It is finished when the recipient can use the value for its intended purpose at a tolerable cost.

That may mean retaining a dollar stablecoin, withdrawing local currency, paying a bill, or spending through a connected card. Each option relies on different infrastructure. Quoting aggregate blockchain transaction volume says little about whether those final steps are available.

What US businesses should ask before accepting crypto

A small business considering crypto payments does not need to become a market maker. It does need to understand who is doing that job on its behalf.

The first question is what the business ultimately receives. Direct receipt of a volatile asset creates a different balance-sheet exposure from automatic conversion into dollars. Receiving stablecoins reduces price volatility relative to other crypto assets but adds questions about custody, redemption, and access to banking rails.

The second question is when settlement becomes final from the business’s perspective. Blockchain confirmation, processor approval, and arrival in a bank account can occur at different times. A provider should be able to explain which event controls refunds, accounting, and access to funds.

Finally, businesses should examine what happens during disruption. A system that works in a quiet market may depend on one exchange, one stablecoin, one blockchain, or one banking partner. Redundancy is not exciting, but payments rarely improve when excitement is the design objective.

The grounded takeaway

The recovery of bitcoin and ether liquidity suggests that the largest crypto markets have repaired some of the damage exposed by the flash crash. The continuing risk in altcoins shows that this recovery is not evenly distributed.

For payments, the lesson is straightforward: a polished checkout experience is only as reliable as the conversion and settlement machinery behind it. Stablecoins can reduce the mismatch between crypto balances and dollar obligations, while cards can connect those balances to familiar merchant networks. Neither removes the need for liquid markets, functioning banks, dependable redemption, and clear operational responsibility.

Crypto payment adoption should be judged by whether money arrives where it is supposed to arrive, in the form the recipient can use, under conditions that are not unusually favorable. Everything else is interface design.