USDC payment providers on Arc, compared by criteria

Built on Arc doesn't rank payment providers — a chain-adjacent directory ranking the partners it lists is a conflict of interest, and a single "best" answer would be false anyway since the right provider depends on your custody preference, settlement needs, and geographic footprint. This guide gives you the criteria to run the comparison yourself, against the current directory of providers with a stated or confirmed relationship to Arc.

Why "provider" means several different things in this category

Before comparing anything, it's worth separating what's actually being offered, because "USDC payment provider" gets used for at least four distinct businesses that don't compete directly with each other. A checkout/gateway provider sits at the point of sale and handles the customer-facing payment flow — closest in shape to a traditional payment processor. A wallet-as-a-service provider issues and manages wallets (often non-custodial, often with gasless transaction sponsorship) that another business builds a payment or account experience on top of. A treasury/settlement router moves USDC (and sometimes EURC) between accounts, converts between fiat rails and stablecoin, and handles the back-office side rather than the checkout side. And a cross-border/remittance network specializes in the corridor problem — getting value from one country's payment rails to another's, with USDC as a settlement layer in the middle rather than the customer-facing product.

A provider comparison that doesn't separate these ends up comparing apples to oranges — a checkout gateway's transaction fee against a treasury router's FX spread is not a meaningful comparison. Work out which of the four jobs you actually need done before evaluating anyone.

Criterion one: custody model

This is the single most consequential axis, and it should be the first question you ask any provider, not the fifth. Does the provider take custody of funds at any point (fully custodial), do they offer a non-custodial architecture where you or your customer retain keys, or is it a hybrid — non-custodial wallet infrastructure with the provider still operating the transaction plumbing? Ask them to describe this precisely rather than accepting "non-custodial" as a marketing label; the exact point at which control of funds passes, and to whom, is the thing that matters for your risk assessment, not the word on the pricing page.

Criterion two: settlement — fiat off-ramp, USDC balance, or both

Some providers convert every incoming USDC payment to fiat automatically and deposit to your bank account, functioning much like a traditional processor from the merchant's point of view. Others let you hold a USDC balance indefinitely and choose when (or whether) to convert. A provider that only does one of these may not fit a business that wants flexibility — ask specifically whether fiat settlement is instant, batched daily, or requires manual initiation, and what the FX or conversion spread is on that leg. Built on Arc's FX on Arc guide covers where that spread actually sits in more depth. Note that "what yield can I earn holding USDC in the meantime" is explicitly not a question this directory answers — see arcyield.app for that.

Criterion three: corridor and currency coverage

A provider's real value in this category is often not the checkout technology — that's broadly similar across vendors — but which corridors and local payout currencies they've actually built rails for. This matters more than it might initially seem: developed-market enterprise demand for stablecoin payments is currently intent more than volume (13% of organisations report having used stablecoins as of the most recent survey data, even as 87% call it a competitive advantage), while the real transaction volume — inside the ~$350–550bn/yr real-economy stablecoin payment figure against a $46tn gross headline number — concentrates disproportionately in emerging-market corridors where local banking rails are slow or expensive. A provider with deep Africa, Southeast Asia, or Latin America coverage is solving a different, more proven problem than one offering only US/EU checkout. Ask for named countries and named local payout methods, not a marketing map.

Criterion four: fees — and what's actually disclosed

Compare, specifically: a per-transaction fee (flat or percentage), an FX/conversion spread on any fiat leg, and any withdrawal or payout fee separate from the transaction fee itself. Do not accept a single headline number as the full cost — ask for a worked example at your expected transaction size and frequency. This guide will not publish fee figures for any provider, because fee schedules change and an unverified number here would be worse than no number; get current pricing directly from each provider you shortlist.

Criterion five: compliance and licensing — verify, don't assume

A provider's compliance posture — money transmitter licensing, KYC/AML program, sanctions screening — is not something to infer from their marketing. Ask directly: which jurisdictions do they hold a license or registration in, and for which activities specifically (money transmission, e-money issuance, payment services)? This directory does not state a regulatory position for any provider it has not independently verified, and neither should you accept one without documentation. This matters more, not less, in a stablecoin context — the regulatory framework is newer and more fragmented across jurisdictions than traditional card acquiring.

Criterion six: Arc-specific status — announced, testnet, or confirmed integration

Separate from all of the above: what is the provider's actual, confirmed status with respect to Arc specifically, as distinct from Circle or USDC generally? A provider can have a long, credible history processing USDC on Ethereum or elsewhere with no confirmed Arc-specific integration at all. Circle's 5 August 2026 founding-validator-and-integrations press release named a specific set of integration partners — Rain, Thunes, Wirex, and others — directly; that is the strongest tier of pre-mainnet confirmation available, and it is still not the same as a shipped, testable Arc integration, because nothing is live on Arc mainnet until 16 September 2026. Treat "named in Circle's release" as one tier, "own public statement about Arc plans" as a second and weaker tier, and "no verifiable Arc-specific statement at all" as a third. Built on Arc's individual project pages, linked from the directory below, carry this status distinction for each named provider — check the specific entry rather than assuming from a company's general reputation.

The directory

Cross-reference each entry against the six criteria above rather than reading down the list in order — the table's status column tells you where a given entry sits on the Arc-specific confirmation question (criterion six), but it won't tell you about custody model or corridor coverage, which you'll need to check on the provider's own site or by asking them directly.

What to actually do with this before mainnet

Given that nothing is live until 16 September 2026, the useful action right now is narrowing your shortlist to two or three providers that fit your custody preference and corridor needs, and requesting sandbox or testnet access where it exists so your engineering team can validate the integration mechanics before there's any live volume at stake. Built on Arc's API comparison guide covers what to test at the API level specifically — webhooks, idempotency, sandbox availability — once you've narrowed the field using the criteria here.

Built on Arc is an independent directory. Arc is a Circle product; we are not affiliated with, endorsed by, or operated by Circle.

Sources: - Circle Announces Founding Validator Cohort and Major Integrations for Arc - Arc | The Economic OS — official site