← PayPal Interview Insights

PayPal·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Apr 2026

Summary

PayPal system design round focused on cross-border payments. One meaty question, no fluff, they clearly wanted to see if you'd thought about the regulatory and real-time data complexity that comes with international transfers.

Questions Asked (1)

Q1

Design a cross-border money transfer service similar to Remitly, accounting for country-specific transfer restrictions and real-time exchange rate lookups.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

I started with the happy path and immediately regretted it.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then design a high-level architecture that separates concerns: user-facing APIs, transfer orchestration, compliance/restrictions engine, FX rate service, and payment rails. Dive into the two highlighted challenges—country-specific restrictions and real-time FX—by proposing data models, caching strategies, and fallback mechanisms, while discussing trade-offs around consistency, latency, and cost.

Pro tip: Emphasize idempotency and exactly-once processing for transfers, and discuss how you'd handle FX rate volatility with rate locks and circuit breakers—these show you understand real-world financial systems beyond just scaling.

1. Clarify Requirements and Scope

Ask about expected scale (transfers per second, countries supported), latency requirements, consistency needs, and regulatory constraints. Define core user flows: quote, transfer initiation, funding, FX conversion, payout, and status tracking.

2. High-Level Architecture

Sketch main components: API gateway, transfer service, compliance service, FX service, payment processor integrations, ledger, and notification service. Explain how they interact via synchronous calls and asynchronous events (e.g., Kafka).

3. Country-Specific Restrictions Engine

Design a rules engine that evaluates transfer eligibility based on sender/receiver countries, amount limits, and regulatory requirements. Discuss how to store and update rules (e.g., database with versioning), and how to enforce them at quote and transfer time.

4. Real-Time FX Rate Lookup

Propose a service that aggregates rates from multiple providers, caches them with short TTL, and offers rate locking for a short period. Discuss fallback to last-known rate, handling provider outages, and ensuring consistency between quote and execution.

5. Trade-offs and Scalability

Discuss trade-offs: consistency vs. availability for FX rates, synchronous vs. asynchronous compliance checks, and cost vs. latency for payment rails. Address scaling with sharding, idempotency, and monitoring.

Key Points to Mention

  • Idempotency and exactly-once processing for transfers to avoid duplicate payments
  • Data model for country restrictions: rules, limits, and versioning
  • FX rate aggregation, caching, and rate locking with TTL
  • Use of message queues for asynchronous processing and decoupling
  • Compliance and AML checks integration, including sanctions screening
  • Ledger design for double-entry accounting and audit trails

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.