Salesforce / FinTech · Interactive Demo

Payment Orchestrator

Enterprise-grade payment routing built on Salesforce for a restaurant SaaS platform. Four gateway integrations with automatic failover, async transaction processing via Queueable Apex, and real-time analytics. Click "Simulate Gateway Failure" to see failover routing in action.

Platform: Salesforce (Apex, LWC) Gateways: Stripe · Adyen · Square · Heartland Success Rate: 98.4% Architecture: Queueable Apex / SOA
98.4%
Success Rate
247
Transactions Today
$84,392
Volume Processed
Transaction Log Live
TX ID Restaurant Amount Gateway Status
Failover Logic
1

Route to Primary Gateway

Every transaction hits Stripe first. Queueable Apex processes asynchronously — no governor limit timeouts on high-volume batches.

2

Detect Failure in Real Time

If Stripe returns a gateway error, the orchestrator catches the exception immediately — no manual intervention, no lost transaction.

3

Re-route to Fallback

Adyen is queued as first fallback. Square and Heartland follow in priority order. Each retry is logged with full context in Salesforce.

4

Confirm & Surface to Dashboard

Successful transactions update the LWC analytics dashboard in real time. Failed attempts trigger alerts and log to the escalation record.

Gateway Status
Stripe Primary 99.1%
Adyen Fallback 1 98.7%
Square Fallback 2 97.9%
Heartland Fallback 3 96.4%
Simulate Failure
⚠ Gateway Failure Detected
Stripe returned GATEWAY_ERROR. Routing to Adyen fallback. Transaction preserved — no data lost.
✓ Failover Complete
Payment re-routed via Adyen. Logged to Salesforce escalation record. Success rate holding at 98.4%.
Technical Notes
Queueable Apex — async processing avoids governor limits on high-volume restaurant batches
Custom LWC terminal — staff-facing payment UI built in Lightning Web Components
SOA pattern — gateways are swappable service layers; adding a 5th provider requires no core logic changes
Full audit trail — every routing decision logged to custom Salesforce objects for compliance
This is an interactive simulation. Transaction data is generated for demonstration purposes. The architecture, failover logic, and Apex patterns reflect the actual system built on Salesforce. View on GitHub →