USDC payment providers on Circle's Arc: who supports what

Eleven payment companies have a named, sourced relationship with Circle's Arc as of 6 September 2026, and none of them is live, because Arc's mainnet does not open until 16 September. What separates them is not feature sets — those are broadly similar — but the strength of the evidence behind the Arc claim, which ranges from a named line in Circle's own press release to a logo on a company's own homepage. The table below is sorted by that, strongest evidence first. Statuses follow [Built on Arc's payments category](https://builtonarc.app/category/payments-payouts?utm_source=trustswap&utm_medium=article&utm_campaign=arc-launch), which carries the dated source behind every one of them.

The table

How to read the evidence column, because it is the whole point

Four tiers, and the distance between the top and the bottom is larger than it looks.

Primary, Circle means Circle named the company, in writing, in a document about Arc. That is the strongest confirmation available before a chain exists, and it still only tells you a relationship was announced on 5 August 2026. Circle's release describes Rain, Thunes and Wirex in a single sentence covering all three; it does not say what any one of them has built.

Own statement, dated means the company said it itself, with a date, and can be held to it. PhotonPay saying in November 2025 that it had joined Arc's testnet is a narrower claim than a press-release mention, and a more testable one. In practice this tier ages better than the one above it.

Primary, Circle, not Arc-specific means Circle has acknowledged the company — a directory listing, a blog profile — in a context that is about USDC or about Circle's partner programme rather than about Arc. It is real, and it is not an Arc claim. Do not let a company's Circle relationship become an Arc relationship in your notes.

Secondary reporting and own site only mean nobody except the company or a downstream aggregator has said this. That is not an accusation; a small fintech genuinely inside a grant cohort has no way to make Circle publish a list. It does mean you should ask for the grant agreement or the Circle contact before you build a settlement dependency on it.

What none of this table tells you

Fees, custody model and licensing — deliberately. Fee schedules move faster than any page can track, and a stale number is worse than no number. Custody is the question that actually decides your risk profile and it cannot be reduced to a column: ask each provider to describe the precise moment at which control of funds passes and to whom, and do not accept "non-custodial" as an answer to it. Licensing has to be verified against the register in each jurisdiction you will operate in, not against a marketing page.

Nor does it tell you which of these will be working on 16 September. The honest answer is that nobody knows, including the providers, and that anyone promising you a live Arc integration on day one is describing a plan.

What to do with this before mainnet

Shortlist two or three from the top half of the table, on the basis of the corridors and currencies you actually need rather than the depth of the Arc relationship — the Arc leg is the easy part, and local payout coverage is what takes eighteen months to build. Ask each for sandbox or testnet access now, so your engineers can validate webhooks, idempotency and reconciliation against something before real money moves. Then ask the one question this table cannot answer for you: on what date, specifically, does your Arc mainnet integration go into production, and what is the fallback rail if it slips? A provider that answers that clearly is a different proposition from one that answers it with a press release.

Related on this site

If you are moving USDC onto Arc in the first place, start with the bridge guide. If you are choosing where the balance sits afterwards, start with the wallets page.