Circle's Arc Launch Adds a USDC Fee Model to XRP's Settlement Competition

Direct answer: Arc changes the fee comparison for XRP payment routes

Circle launched Arc's public mainnet on September 16, 2026, with transaction fees paid in USDC. For XRP payment providers, that creates another settlement option to evaluate. It does not establish that Ripple partners have abandoned XRP, or that a dollar-denominated network fee makes an entire payment route cheaper.

Section sources[1][2]

Circle Arc is live, while validator onboarding remains phased

Confirmed: Circle's September 16 announcement establishes a public network launch. The Block independently reports the launch and its USDC fee model. That is a meaningful change from a test environment or a promised opening date: operators can begin assessing a production route rather than evaluating only a roadmap.

The deployment boundary matters. Circle describes a phased rollout of its founding validator cohort, which includes SBI Group and Standard Chartered alongside other institutions. The Block also reports phased participation. This article therefore does not treat a named institution as a verified active validator at a particular time. A cohort announcement and a live node record answer different questions.

Analysis: procurement teams should keep separate evidence for availability, operational participation and customer use. A network opening supplies the first category. A named validator or application does not by itself supply the other two. Before committing a payment service, an operator should request a supported production workflow, accountable service contacts and evidence that the required functions are usable today.

Section sources[1][2]

USDC already exists on XRPL, but the fee asset is different

Confirmed: Circle announced native USDC on the XRP Ledger on June 12, 2025, including support through Circle Mint and its APIs. The Block reported that launch independently on the same date. Arc's arrival therefore does not create a simple choice between the USDC issuer and the XRP Ledger. The issuer's stablecoin already has a presence on the ledger associated with XRP.

XRPL's transaction-cost documentation specifies that its network charge is paid in XRP and destroyed. Ledger's independent technical explainer corroborates the fee-burning mechanism. A USDC transfer on XRPL consequently has two distinct asset roles: the stablecoin being transferred and XRP consumed as the ledger fee. Arc instead uses USDC for its network charge. Neither description establishes the total amount a customer pays to complete a cross-border transaction.

Analysis: compare the asset being delivered separately from the asset paying for execution. A treasury already funding USDC transactions may find dollar-denominated fees easier to budget. An XRPL operator may already have mature XRP fee provisioning. The practical benefit depends on each operator's existing accounts, controls and funding process. No measured savings for either group are established by the launch sources.

Section sources[3][4][5][6][1][2]

SBI and Standard Chartered show why institutional roles need precise labels

The overlap is real, but its meaning is narrower than a network-switching headline. Standard Chartered announced an investment in Ripple on September 15, 2016. Ripple and SBI announced a memorandum about distributing RLUSD in Japan on August 22, 2025. Independent reports from City A.M. and The Block corroborate those two announcements, respectively, without turning either historical record into evidence of a current network switch. Those dated records establish relationships; the older announcements should not be read as a current inventory of every commercial arrangement.

Analysis: investment, stablecoin distribution, validation and transaction routing are different decisions. An institution can assess a network's governance while its customers use another network for a particular payment. A name appearing in two ecosystems does not disclose how much capital or transaction volume it allocates to either. It also does not identify the asset used inside any individual transfer.

Unresolved: the cited launch records do not quantify XRP-linked payment flows moving to Arc, specify a terminated Ripple relationship, or measure a resulting change in XRP demand. Readers evaluating a migration claim should look for an institution's explicit service announcement and comparable transaction evidence. Familiar names can help identify whom to ask, but cannot substitute for the missing operational record.

Section sources[7][8][9][1][10]

The useful cost test starts with the same recipient outcome

Analysis: a fair comparison should hold the payment objective constant. Specify the starting asset, starting location, amount, recipient asset and destination before seeking quotes. Comparing an Arc USDC transfer with an XRP trade followed by a bank withdrawal would otherwise combine different services. A lower network charge can coexist with a more expensive overall route, just as a higher network charge can coexist with better available liquidity.

Consider a hypothetical business that already holds USDC and must deliver local currency into a supplier's bank account. Its worksheet should include conversion spread, platform charges, withdrawal charges, the cost of obtaining any required fee asset and the final amount credited. It should also record when the recipient can actually use the money. These are proposed comparison fields, not measured Arc or XRPL results, and this example makes no claim that a particular provider supports that corridor.

The separate USDC and XRP fee roles documented above help define that worksheet. Request executable quotes for the same amount and time window, then reconcile each completed transfer against the quote. Track failed attempts and recovery procedures as well. A headline about fee denomination answers one input question; the receipt and the exception log answer whether the service met the business requirement.

Section sources[5][6][3][4][1][2]

Treasury teams should test live features before relying on the roadmap

Confirmed limitation: Circle describes network-wide opt-in privacy as still in development, a distinction also reported by The Block. A public launch should not be interpreted as confirmation that every advertised confidentiality feature is available. Operators with sensitive payment data need to verify the actual exposure of their proposed workflow before entering production.

Analysis: a pilot acceptance test should cover the entire operating cycle. Fund the account, submit the transfer, verify the intended recipient's credit, reconcile the fee and exercise the support process for a rejected instruction. Document who can approve a payment and who can obtain transaction records. Where a required capability remains on a roadmap, the decision should explicitly depend on delivery and testing of that capability.

For wallet and payment developers, the fee-asset difference also makes balance presentation an important design choice. A customer should be able to distinguish spendable funds from funds needed to execute an instruction. For XRP holders, the relevant evidence is sustained, identifiable use of XRP within actual services. A competing network's opening supplies a new comparison point, but it does not provide a price forecast.

Section sources[1][2][5][6]

What evidence would change the XRP settlement assessment?

Analysis: the strongest follow-up would pair named production services with repeatable delivery evidence. Published fee schedules, supported deposit and withdrawal routes, observed completion times and clear treatment of failed payments would make the comparison more concrete. The same criteria should apply to an Arc provider and an XRPL provider, using identical payment objectives wherever a valid comparison is possible.

Uncertainty remains around customer allocation, realized cost and usage at scale. This report does not infer them from validator names, asset availability or a launch announcement. An operator selecting a route should focus next on a documented service it can test. An investor assessing XRP demand should focus on evidence that distinguishes ledger fees, bridge-asset use and unrelated corporate relationships.

Section sources[1][2][3][4][9][5]