Ideal partner
Agencies and studios
Teams billing internationally that need stablecoin checkout and operator-reviewed payouts.
Founder-led design partner pilot
Merchant settlement and payout infrastructure for businesses building on Arc.
ArcLedger is focused on one narrow operating layer: stablecoin invoicing, hosted checkout, payment verification, reconciliation, webhook delivery, and payout operations for internet businesses and agentic commerce teams.
ArcLedger is testnet-safe by default until Arc mainnet guidance and infrastructure are finalized.
Merchant onboarding is intentionally controlled, with manual review before live activation.
Current rollout
Controlled onboarding before scale
Controlled rollout
The current go-to-market motion is founder-led onboarding with limited merchant activation and explicit manual review.
Operational visibility
Invoices, payment verification, webhooks, and payouts all map back to auditable operator actions inside the dashboard.
Compliance posture
ArcLedger is evaluating vendor-supported KYB, KYC, and sanctions screening for real merchant onboarding.
Ideal partner
AI-native software businesses
Products collecting onchain revenue that still need receipts, reconciliation, and webhook delivery.
Ideal partner
Service operators with manual review
Founder-led teams that want a controlled merchant onboarding flow before broader self-serve rollout.
Why this matters for onboarding
ArcLedger is deliberately being built to support real merchant review, not anonymous open signup.
Production onboarding for a payment and payout product requires clear business identity, merchant review, sanctions awareness, and auditability. The product posture on this site is intentionally aligned with that reality.
Live product signals
Hosted checkout links with signed payment verification
Operator audit trails for onboarding, payouts, and webhook delivery
Webhook replay support and queue-based processing for failed downstream events
Role-based access controls across dashboard and API workflows
Public posture
Testnet-safe by default, with a tighter production checklist instead of vague promises.
ArcLedger is intentionally conservative about what it claims. The product is shipping a controlled pilot first, while merchant onboarding, verification, and compliance tooling are hardened for real production use.
ArcLedger is testnet-safe by default until Arc mainnet guidance and infrastructure are finalized.
Merchant onboarding is intentionally controlled, with manual review before live activation.
Compliance automation is being layered in carefully rather than implied before it is real.
The product is optimized for a small design-partner pilot instead of broad anonymous self-serve signups.