There is no single public counter of every payment. A processor's merchant invoices, a 's transfer value and the amount of stablecoins outstanding measure different things. They cannot be combined into a global payment ranking without a common definition, period and coverage model.
Correction — 22 October 2026. The previous article presented an unsupported league table of payment assets, treated transfer activity as commerce, and attached precise fees and settlement times to heterogeneous routes. Those rankings and performance claims have been withdrawn. This revision explains how to compare evidence and a specific payment route.
Define the payment you want to measure
A customer buying groceries, an moving reserves and a trader transferring collateral can all create on-chain activity. Only a defined classification can distinguish their economic uses. Even a transfer between two different addresses need not represent two independent people or a purchase.
Start with a question such as “which assets paid this processor's completed merchant invoices during September?” That is narrower and more answerable than “which coin wins payments worldwide?” Specify treatment of failed invoices, refunds, internal transfers and mixed-asset settlement.
Count, value and users can produce different rankings
Consider a fictional processor with 100 payments in Asset A averaging $5 and 25 in Asset B averaging $100. Asset A has 80% of payment count but only $500 of $3,000 total value, or 16.67%. Asset B leads value with 83.33% while representing 20% of count. Both descriptions can be correct.
Neither establishes user share. A repeat customer can generate many invoices, while an aggregator can represent many customers through one account. Publish the denominator alongside the percentage. The offline model script reproduces this invented example; it is not a processor dataset.
Compare measurements with matching boundaries
| Metric | What it can show | What it cannot establish alone |
|---|---|---|
| Processor invoice count | Activity within that provider's defined sample | Worldwide merchant share |
| On-chain transfer value | Value moved under a stated counting method | Retail purchases or unique customers |
| Stablecoin supply | Outstanding units under an issuer/analytics definition | How often those units pay for goods |
| Wallet or address count | Recorded identifiers or software observations | A census of people or active buyers |
A fair cross-asset comparison also specifies networks, exchange-rate conversion, time zone and cutoffs. Comparing one chain's daily dollar transfers with another asset's monthly invoice count does not become valid by placing both in the same table.
Adjusted stablecoin activity is not automatically retail spending
Visa's explanation of on-chain stablecoin analytics explicitly distinguishes total transfer volume from adjusted activity and describes exchange, bot and repeated smart-contract activity. Adjustment can improve a metric without converting every remaining transfer into a customer purchase.
Coin Metrics' transfer-value methodology likewise describes heuristics and asset-specific coverage. Its adjusted measure is an analytical construction, not a receipt-level census of global commerce. Record methodology revisions when comparing periods; an apparent jump or fall can reflect changed labels or filters.
The old article's claim that one stablecoin network processes more actual payments than every alternative combined was not supported by evidence with that scope. It has not been replaced by a new unsourced winner.
Litecoin's usefulness depends on the complete route
For an actual LTC payment, authenticate the request, agree the amount and quote expiry, inspect the destination, submit the transaction and reconcile recipient credit. A processor may convert the receipt into ; a merchant may retain LTC. These create different price and counterparty exposure.
inclusion, invoice acceptance and a bank payout are separate stages. A 150-second block target is not a payment deadline. Our block-time analysis explains waiting tails, and the transaction-state guide separates the relevant observations.
Costs and restrictions must be checked for the selected asset
A stablecoin ticker without its network and token identifier is incomplete payment information. Native LTC and a wrapped LTC representation are also different assets. Check what the receiver actually accepts, any minimum, required , conversion spread and withdrawal conditions.
Do not compare a selected low fee with another route's entire customer bill. Conversely, low network cost does not erase acquisition or off-ramp costs. compatibility, access rules, provider queues and issuer controls can determine whether the route is usable even when a network is functioning.
Our GENIUS Act correction explains why regulation alone does not create universal tax exemptions, insurance or instant merchant credit. A legally supervised issuer and a successfully completed checkout are different claims.
What BitPay's data actually covers
The BitPay statistics page labels cryptocurrency merchant transaction counts and other measures for its own processing activity. Its category and period labels matter. A count share is not necessarily dollar-volume share, and neither is global share across competing processors and direct payments.
To cite a particular result, save a dated export or screenshot, record the observation window and preserve the exact measure. If no reproducible snapshot is available, link the changing source as a starting point without inventing a historical value. This editorial review did not extract a fresh market-share series or independently audit BitPay's classifications.
Lightning capacity and throughput need the same care
A public channel-capacity measure is a balance or capacity observation, not the number or value of payments completed over a period. Private activity and routing behaviour complicate interpretation. Similarly, a network's advertised transactions per second is not a measured merchant success rate.
For a payment route, verify the implementation, compatible endpoint, , fees and recovery process. Do not assume Bitcoin and deployments have interchangeable support. See the merchant Lightning checklist for that narrower operational question.
A reproducible comparison study
Choose a single period and define a completed payment. Identify every provider or data source included and the populations left out. Export raw observations where permitted, retain exclusions and publish the query or calculation. Separate count, value and distinct-customer measures.
Analyse currencies and networks separately before aggregation. Explain how conversion prices and refunds are handled and whether duplicate invoices or rebroadcast transactions are deduplicated. A model of missing coverage must be explicit; a large sample is not automatically representative.
Use payment evidence for payment decisions
A merchant can compare two small, legally available test checkouts through the actual services it intends to use. Record customer cost, amount delivered, observed acceptance and refund behaviour. That operational finding is useful even when it cannot identify a global winner.
For an investor, even demonstrated payment usage does not mechanically establish coin-holder returns. Fees, asset retention, conversion, competition and supply dynamics intervene. The old article's winner-and-loser portfolio implications exceeded its evidence.
Sources, worksheets and review scope
Use the payment comparison worksheet and synthetic results to keep denominators and assumptions visible. The linked BitPay, Visa and Coin Metrics materials were checked on 22 October 2026. No live purchases, global payment census or cross-network performance benchmark was conducted for this revision.
Frequently asked questions
Is there a verified worldwide winner in this article?
No. The earlier ranking lacked common definitions, observation windows and coverage. It has been withdrawn.
Does transfer volume equal merchant sales?
No. Transfers can include exchange movements, collateral, internal activity and other uses. Even adjusted metrics need their stated interpretation.
Can one asset lead count while another leads value?
Yes. The synthetic example gives Asset A 80% of count but 16.67% of value because average payment sizes differ.
Does BitPay share establish global share?
No. It describes BitPay's identified sample and metric. Other processors and direct payments need separate coverage.
Does channel capacity measure Lightning payment volume?
No. Capacity and completed payments over time are different quantities.
Were the fees and timings benchmarked live?
No. This revision provides a comparison method and explicit synthetic arithmetic, not a fresh checkout or settlement benchmark.
