ArcLedger Trust and Security Posture

Current operating model

ArcLedger is shipping as a controlled pilot for real business workflows on Arc. The product is focused on hosted checkout, payment verification, reconciliation, webhooks, and payouts. Merchant activation is intentionally limited and operator-reviewed.

Platform controls

• Role-based dashboard access for operators and workspace owners.
• Audit-aware operator flows for invoices, verification, payouts, and webhooks.
• Signed hosted checkout verification for public payment confirmation.
• Webhook delivery controls, replay support, and queue-based processing.
• Health and incident visibility for controlled production operations.

Merchant onboarding posture

ArcLedger is evaluating vendor-assisted KYB, KYC, and sanctions screening for real merchant onboarding. During the current rollout, onboarding remains intentionally conservative and may involve manual review before production access is enabled.

Network and rollout posture

ArcLedger remains testnet-safe by default while Arc mainnet infrastructure and operational guidance continue to mature. The goal is to prove operational discipline before broadening the product posture.

What ArcLedger does not claim

ArcLedger avoids implying capabilities that are not yet fully live. The public product posture is deliberately narrower than the long-term roadmap, especially around compliance automation and infrastructure assumptions that still depend on external vendors or network guidance.