Visa data highlights stablecoin use in business card programs

Sourced news briefing

Visa published the development on 1 October 2026. Visa said approximately 17 percent of its stablecoin-linked card volume in fiscal 2026 year to date occurred across business and commercial card programs. It reported support for more than 160 stablecoin-linked card programs across consumer, business and commercial activity. Visa said payment volume across those programs grew nearly 200 percent year over year. The release identified settlement, treasury management, payouts and cross-border commerce as business use cases. The figures describe Visa activity and should not be generalized to the entire market.

This briefing reports only the source announcement. The release does not establish stablecoin suitability, merchant eligibility, profitability or regulatory treatment for a particular business. The remaining sections are independent FixPays analysis for merchants; they are not claims made by Visa.

Independent analysis: interpret the denominator

A percentage of stablecoin-linked card volume describes a selected ecosystem and does not reveal the share of all commercial card spending. Record the population and period behind each metric. Separate program growth from merchant economics. Avoid presenting network data as universal adoption. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

Decision papers should state the metric definition, source date and unanswered questions. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: map treasury conversion

A stablecoin-linked card can combine fiat funding, token balances, card authorization and merchant settlement without those stages being equivalent. Identify every asset and counterparty. Document conversion points and fees. Define redemption and liquidity contingencies. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

The treasury diagram should connect token issuer, wallet, program manager, network, acquirer and bank account. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: measure operational outcomes

Volume growth alone does not show authorization quality, refunds, disputes, customer support effort or settlement reliability. Compare stablecoin-linked and conventional flows. Segment results by corridor and use case. Include failure and recovery costs. For implementation, name an accountable owner, the authoritative system, the exception route and the evidence retained after each decision.

A scorecard should use stable definitions and retain the underlying transaction population. Review the arrangement by entity, market, currency, payment method and customer journey where those dimensions matter. A provider announcement cannot replace contract review, testing or a documented assessment of the merchant's actual operating model.

Independent analysis: merchant implementation checklist

Verify the exact program and provider available to the merchant. Connect that control to the program agreement and retain the result in a metric definition. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Calculate total conversion and network cost. Connect that control to the wallet ledger and retain the result in a treasury map. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Test refund and dispute handling. Connect that control to the card transaction and retain the result in a reconciliation archive. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Reconcile token and fiat records. Connect that control to the settlement account and retain the result in a pilot scorecard. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Review counterparty and network concentration. Connect that control to the program agreement and retain the result in a metric definition. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Keep external adoption claims accurately scoped. Connect that control to the wallet ledger and retain the result in a treasury map. Test a successful transaction and a realistic failure, then record what changed, who approved the response, how customers were treated and whether finance could reconcile the final outcome.

Commercial review should cover service levels, settlement timing, data duties, incident handling, customer support, termination rights and migration assistance. Finance should model both normal volume and stressed conditions rather than relying on a headline feature or a successful demonstration.

After launch, monitor authorization, abandonment, unmatched items, reversals, refunds, complaints, fraud, support effort and settlement differences using stable definitions. Segment results sufficiently to expose a corridor, method or product that performs differently from the portfolio average.

A controlled pilot should define scope, duration, success measures, stop conditions and rollback ownership. Preserve transaction traces and customer communications so reviewers can distinguish a product limitation, integration defect, user error, provider incident and deliberate risk decision.

Finance should reconcile the program agreement with the wallet ledger on a stated timetable. Unmatched items need aging, ownership and escalation thresholds. A manual journal can correct accounting, but it should never erase the original variance, the investigation evidence or the reason a difference occurred.

Customer support needs status language that reflects the underlying system rather than guessing from a single dashboard. Staff should distinguish authorization, acceptance, processing, settlement, reversal and refund, then use a metric definition to locate the authoritative reference before promising a time or outcome.

Risk teams should compare new behavior with established baselines while allowing for legitimate changes in channel and geography. Monitoring should reveal concentrated failures and unusual sequences without treating every unfamiliar pattern as fraud. Confirmed weaknesses belong in a treasury map with an owner and response date.

Data governance matters because a new payment route often adds identifiers, vendors and cross-border transfers. Record which party receives each field, why it is needed, how long it remains available and how an access or correction request reaches the responsible organization.

Provider due diligence should be refreshed when the product, contracting entity, settlement account or subcontractor changes. Review permissions, financial and operational dependencies, security responsibilities, complaint cooperation and termination support. Evidence should describe the current service rather than an earlier sales presentation.

A management review should combine financial, customer, risk and operational measures. Record the decision to expand, constrain, remediate or stop the flow, including dissent and unresolved assumptions. This creates an auditable link between observed performance and the merchant's continuing use of the development.

Review follow-up resolution communication status beneficiary identity pricing data retention complaint fulfilment relevant merchant payment customer provider settlement refund dispute reconciliation risk compliance operational contractual financial technical security privacy support exception records carefully.