How a payment moves through the RC-1 services, from the merchant to the dashboard, governed and proven at every hop.
Flow: Merchant → Gateway → Execution Governance → PQ Proof Service → Processor Sandbox / CyberSource → Settlement → Dashboard → SDK / Proof Portal.
A sale arrives from a terminal (PAX) or the API with the canonical request fields.
Authenticates under Zero Trust, normalizes to a canonical request, and routes.
Applies policy and records the governance decision, including processor selection.
Signs route and handoff proofs with ML-DSA-65; sign and verify exposed.
Captures through the processor abstraction layer against CyberSource.
Creates and completes the settlement instruction lifecycle.
Serves activity and reporting against the live local service URLs.
Verifies the Governance and PQ live APIs and surfaces proofs for review.
Diagram rendered with styled cards and inline SVG for portability. The processor stage runs against a sandbox in RC-1; full Gateway-backed live E2E is tracked on the Next Steps page.