Design a Payment System
Payments came up in two Visa design rounds in 2026, both in Bengaluru. In June a Staff candidate got the prompt above, focused on payment states, payment methods, durable execution and retries. They drew the high-level design, then coded the main entities and a service class, with the strategy pattern handling the different payment methods. Their verdict was that it had too many requirements for one round. In July a Senior candidate's second round went deep on their own projects and then on a payment gateway design.
Older reports cover the same ground. In 2025 a US hiring manager asked a Software Engineer I candidate for the backend of a peer-to-peer payment app like Venmo or Zelle. That year also brought transaction management for merchants (Senior, Bengaluru) and a payment gateway squeezed into one hour with coding (Lead Engineer, US). Going further back, there was a UPI app (2023) and a PhonePe-style payment service that had to give every transaction a unique id (2021). Visa uses this prompt alongside several others, and it isn't the standard round. Its follow-ups are worth learning anyway, because idempotency and retries come up in other Visa design rounds too.
VisaPremium lesson · System design round
The Visa design, worked end to end.
- Requirements and scopeSystem design
- The API and data model
- The design, drawn out2 diagrams
- 5 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports
Visa interview guideKnow what Visa asks before you walk in.
30 coding · 8 system design · 20 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.