USDC subscriptionsfor modernbusinesses

Accept recurring USDC payments with contract-backed plans, Web2-friendly onboarding, expiry tracking, and automation-ready renewals. Settlement runs on Arc.

Loading...

Arc-native USDC billing MVP, contract first.

SubArc starts with clone-based service contracts, safe subscriber-agreed terms, and a local relayer/indexer path for renewal execution and state tracking.

Subscriber-agreed terms

Subscribe and renew calls carry expected price, interval, and fee-cap guards so subscribers only pay under terms they accepted.

Clone-based contracts

Deploy lightweight service contracts for merchants using a Factory + Clone architecture designed for efficient subscription service creation.

Relayer-assisted renewals

Support external relayers that scan due subscriptions and execute renewals only when allowance, fee caps, and grace-window checks pass.

Local relayer / indexer path

The reference contracts repo includes relayer and indexing flows for renewal execution, renewal attempts, and service state tracking.

USDC-only MVP scope

The reference implementation is positioned as an Arc-native USDC billing MVP with focused subscription, renewal, and withdrawal flows.

Security-conscious design

Built around pause controls, renewal safety checks, ownership guards, and no-relayer-custody assumptions for subscriber funds.

Contract-first billing stack

SubArcFactoryV1

  • • Deploys merchant service clones
  • • Manages service creation and protocol-level configuration
  • • Anchors the Arc-native USDC billing MVP flow

SubArcLogicV1

  • • Stores plans, subscribers, renewals, and withdrawals
  • • Enforces subscriber-agreed renewal terms and fee caps
  • • Handles merchant withdrawals after contract-side accounting

App / checkout layer

  • • Sits outside the contracts repo as the user-facing integration layer
  • • Helps users approve USDC and call subscribe flows safely
  • • Can package the contract flow into a simple merchant checkout experience

Relayer / indexer

  • • Tracks services, plans, subscriptions, and renewal attempts
  • • Scans due renewals and checks allowance, fee caps, and grace windows
  • • Provides the external execution path for renew(user)

Future automation layers

  • • Broader automation can be layered on top of the relayer MVP later
  • • Gateway-assisted onboarding and stronger infra are future work
  • • Production-grade automation is intentionally out of current MVP scope

Integrate contract flows in minutes.

Start from the contract flow: approve USDC, call subscribe with explicit guards, and plug relayer-assisted renewals into your app or backend as the next step.

  • Safe subscribe calls with explicit price, interval, and fee-cap guards
  • Arc-native USDC billing MVP scope
  • Clone-based service deployment through factory + logic contracts
  • Arc testnet deployment and relayer demo scripts
  • Local relayer/indexer path for due-renewal execution
View Documentation

Built for real on-chain products.

SubArc supports Arc-native USDC subscription flows across modern on-chain products, from AI agents to membership passes.

AI Agents & Compute

Subscription access for AI inference, compute resources, and agent services.

Developer Tools & Infra

Subscription billing for SDKs, APIs, node providers, and developer platforms.

On-chain SaaS Tools

Stable USDC subscription billing for software and app experiences.

Membership & Access Tokens

Membership passes, paid access, and token-gated subscription experiences.

Planned automation path

Built for relay-assisted renewal infrastructure

SubArc starts with subscriber-agreed renewal terms plus relayer-assisted renewals for due subscriptions. The broader renewal layer can later add reminders, richer indexing, and opt-in automation on top.

1
MVP

On-chain expiry state

Service contracts already expose expiry timestamps, cancellation status, and subscription checks on-chain.

2
Planned

Renewal notifications

Planned apps and workers can trigger alerts, notifications, and merchant-facing reminders before subscriptions expire.

3
Planned

Opt-in auto-renewal

Future automation can extend the relayer model with richer spending caps, renewal limits, and revocable permissions.

Why not full automation on day one?

Smart contracts cannot execute themselves. In the reference contracts repo, renewals are triggered through an external relayer that checks cancellation, allowance, fee caps, and grace-window rules before calling `renew(user)`. Broader automation still requires explicit user authorization and carefully bounded payment limits, so future layers remain opt-in by design.

Security notes

Designed with safer subscription flows in mind

The current contract MVP uses security-conscious Solidity patterns, but it is still testnet-stage code with known MVP limitations and will require third-party audit review before production-scale deployment.

  • Reentrancy protection on payment-sensitive flows
  • Pause controls for emergency response
  • Ownership and pause controls across factory and service flows
  • Safe ERC-20 transfer handling
  • Payment-token rescue restrictions
  • Third-party audit planned before production-scale deployment

Why Arc + USDC for this MVP?

SubArc is positioned as an Arc-native USDC billing MVP, combining stablecoin predictability with a focused contract + relayer flow for subscriptions and renewals.

Arc Network
Arc Network

Arc gives you:

  • Native USDC integration and stablecoin-first design
  • Low transaction costs and fast finality
  • Developer-first tooling and ecosystem
  • Scalable infrastructure for growing dApps
USDC
USDC

USDC gives you:

  • Price stability for predictable billing
  • Widely accepted and trusted across exchanges
  • Fast settlement times on modern L2s
  • Regulatory clarity and transparent reserves

Ready to integrate Arc-native USDC billing flows into your app?

Read Docs →