Mainnet Roadmap
Aruvi runs in production quality on Arc Testnet today. Circle has not yet launched Arc mainnet; when it arrives, this is the path from here to there.
Before launch
Third-party security audit. The contracts have been through an internal audit with all findings fixed and a 71-test suite. Before real money moves, an external firm will audit the full contract suite - gateway, names registry, and link registry - and the report will be published on the Audits page.
Fee switch for merchant payments. Aruvi is completely free on testnet. At mainnet, a small percentage fee will apply to checkout and payment-link payments - the tools that make businesses money. Person-to-person payments stay free forever; the only cost is Arc gas, about a cent. Final numbers will be published here before launch.
Mainnet contract deployment. Circle's mainnet token addresses and chain parameters get baked into a fresh deployment, with the testnet gateway left running for developers.
At launch
Automatic subscription billing. Today a subscription charge has to be triggered by hand once it is due - the merchant pulls or the subscriber pushes. That is not a design choice, it is how every blockchain works: a smart contract is passive and cannot wake itself on a schedule, so something has to send the transaction that runs each charge.
At mainnet, Aruvi runs that "something" for you. An off-chain automation service (a keeper) watches every active subscription, and the moment a charge comes due it calls executeSubscription on the merchant's behalf and covers the gas. The trust model does not change: the on-chain contract still enforces the exact amount and interval, still refuses early or oversized charges, and either party can still cancel at any time. The keeper can only do what the subscription already authorized - it cannot charge more, charge early, or charge a cancelled plan. If a charge fails because the subscriber's balance is short, it simply retries on the next cycle; nothing is queued as debt.
This needs a piece of always-on infrastructure that testnet does not run, which is why automatic billing is a mainnet feature. Until then, the Subscriptions page keeps the manual Charge now button for both sides.
EURC subscriptions. Subscriptions currently settle in USDC only, because the contract's createSubscription uses the default settlement token. The mainnet gateway adds a token parameter so a plan can be billed in EURC, matching the EURC support that already exists in Send, Request, and Refunds.
The Aruvi Card. A card that spends USDC straight from your own wallet - no top-ups, no conversion - previewed in the app today under Aruvi Card. Card programs and regional availability will be announced with mainnet.
Merchant webhooks and receipts. Today merchants get instant in-app notifications when a payment settles. Mainnet adds server-to-server webhooks and email receipts for stores that want fulfillment automation without watching a dashboard. The same webhook stream reports every automatic subscription charge as it settles.
After launch
Confidential payments. Arc's Privacy Sector will allow amounts to be shielded on-chain. The gateway was designed with this path in mind - see the Privacy Roadmap.
Deeper EURC. USDC and EURC are both live settlement tokens today across Send, Request, and Refunds. Beyond EURC subscriptions at launch, later work adds EURC to the merchant surface: EURC payment links, EURC checkout, and FX quotes so a store can price in one currency and accept the other.