Designing a Global Payment System Across Every Time Zone

Payment systems are among the most challenging distributed systems to build. They require high availability, strong consistency, regulatory compliance across jurisdictions, and zero tolerance for data loss. A global system operating across time zones adds the complexity of settlement windows, currency conversion, and fraud detection.

Key sources: "Designing Data-Intensive Applications" by Martin Kleppmann, Stripe documentation, PayPal developer guides.

The Core Challenges

Settlement Timing

In domestic payment systems, settlement happens within hours. In a global system, banks in different time zones operate on different schedules. A payment initiated in Tokyo at 3 PM Friday may not settle in New York until Monday morning.

Currency Conversion

Each currency has a floating exchange rate. The rate at authorization may differ from the rate at settlement. This creates a "mark to market" risk for the payment processor.

Compliance

Every jurisdiction has different regulations. Europe requires PSD2 (Strong Customer Authentication). India mandates 2FA for online payments. China requires licensing for payment processing.

The Dual-Message Model

Payment processing uses a two-phase model:

1. Authorization: Check that funds are available and reserve them. The response is immediate.
2. Clearing and Settlement: Transfer the funds. This happens later (hours or days).

Authorize: Hold $100 on card → Response: "Approved, auth_123"
... 24 hours later ...
Settle: Capture auth_123 → Transfer $100 to merchant account

This model works across time zones because the hold ensures funds are available, while settlement happens during business hours.

Reconciliation

Global payments generate complex reconciliation requirements. Each bank, card network, and payment method reports transactions differently. The system must cross-reference:

• Authorization records
• Settlement reports from banks
• Dispute and chargeback records
• Fee schedules

Reconciliation failures must be detected and investigated manually in many cases.

Key Takeaways

1. Global payments require handling time zone differences in settlement windows.
2. The dual-message model (authorization then settlement) decouples approval from funds transfer.
3. Currency conversion introduces exchange rate risk between authorization and settlement.
4. Regulatory compliance varies by jurisdiction and must be built into the payment flow.
5. Reconciliation across banks and card networks is a significant operational challenge.