Payment Orchestration & Routing

One charge routed across many PSPs — health-aware routing, failover, normalized events

Payment Orchestration & Routing One charge routed across many PSPs — health-aware routing, failover, normalized events Checkout · payment intent · Architecture component Checkout payment intent Orchestrator · validate + idempotency · Architecture component Orchestrator validate + idempotency Routing Engine · cost / auth / health · Architecture component · scoring Routing Engine cost / auth / health scoring Rules + Health · weights, breakers · Architecture component Rules + Health weights, breakers PSP A · acquirer · Architecture component PSP A acquirer PSP B · acquirer · Architecture component PSP B acquirer PSP C · acquirer · Architecture component PSP C acquirer Normalization · canonical events · Architecture component Normalization canonical events Consumers · ledger, fraud, email · Architecture component Consumers ledger, fraud, email intent reads failover Legend External Backend Database Frontend

Routing

  • • Score each PSP on cost, expected auth rate, health
  • • Highest score wins; ranked list is the failover order

Failover

  • • Retry only retryable / provider-attributable declines
  • • Per-intent attempt budget + derived idempotency keys

Normalization

  • • Adapters map webhooks to canonical events
  • • Verify signature, dedupe, correlate to intent

Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export