Visa System Design Interview: Payment Gateway Prompt & 3-Day Prep

Last updated: October 2026

Quick Answer

The Visa system design interview is a reported 45-60 minute video round, usually the second technical round, where the most-reported prompt is “design a payment gateway”, with follow-ups on timeouts, retries, idempotency, double charging and reconciliation. Correctness under failure matters more than raw scale. Rehearse it aloud in the system design format of OphyAI Interview Practice, and on Premium run timed rounds in OphyAI Coding Interview.

Part	What candidates and guides report
Where it sits	Technical round 2, after the online assessment and a coding round
Length	About 45-60 minutes (reported; Visa publishes 30-60 minutes per round)
Core prompt	Payment gateway or payment processing platform
Other prompts	Fraud detection, API gateway for transactions
Scored on	Payment states, failure handling, idempotency, trade-offs, security

What Visa Is Testing in This Round

Visa’s network must answer every card swipe, even when a bank is down. The round tests whether you can design a system that never charges twice and never loses a transaction; reports describe probes on payment states, durable retries and repeated attempts.

Red flags that fail candidates:

• Drawing load balancers and caches before naming the actors: cardholder, merchant, acquirer, network, issuer.
• Treating a timeout as a failure. A timed-out authorization may have succeeded, so the design needs a reversal or a status check, not a blind retry.
• No idempotency key, so a client retry creates a second charge.
• No reconciliation between your ledger and what the network settled.

For the full loop, including the leadership principles round, read the Visa interview guide.

What to Expect

Visa’s careers pages describe two to four interview rounds of 30-60 minutes, mostly virtual. The design round’s contents are candidate-reported, so confirm the format with your recruiter.

• Format. A video call with a shared whiteboard or document. One prep guide describes it as part of a five-round loop.
• Prompts. Reports name a payment gateway handling very high transaction rates, a payment gateway API with concurrency, rate limiting, caching and idempotency, and a payment platform with multiple payment methods and retries.
• Level. New graduate loops sometimes get low-level design instead.

Useful scale anchors from Visa itself: its 10-K filings and VisaNet fact sheet state that VisaNet can handle more than 65,000 transaction messages per second (a capacity figure dated August 2017). Visa’s fiscal 2025 annual report puts processed transactions at about 257.5 billion for the year, which by our arithmetic averages roughly 8,200 a second.

Example Questions and How to Answer Them

These match reported themes, not a leaked list.

1. “Design a payment gateway.”

Approach: Start with the four-party happy path: the gateway sends an authorization request (ISO 8583 type 0100) via the acquirer and network to the issuer, which answers (0110). Then the gateway: an API taking an idempotency key, a payment record with explicit states (created, authorizing, authorized, captured, voided, failed), a durable write before any network call, and acquirer workers. Close with capture and settlement as a separate batch flow plus reconciliation.

2. “The authorization request times out. What do you do?”

Approach: You do not know whether the issuer approved. Send a reversal (0400) for the original so the hold drops, or query status before retrying with the same identifiers; never send a fresh authorization with a new ID. Mention Visa’s Stand-In Processing, which can decide on the issuer’s behalf when the issuer is unreachable.

3. “How do you prevent double charging?”

Approach: Idempotency at every hop. The gateway stores the client’s key plus a request hash and returns the stored result on a repeat; retries downstream reuse the original identifiers. Enforce it with a unique constraint, and say what happens when two requests with one key arrive at once.

4. “Design real-time fraud scoring for authorizations.”

Approach: Scoring sits on the authorization path, so it has a strict latency budget. Precompute features (card velocity, merchant risk), score with a timeout and a default decision, and feed chargeback labels back asynchronously.

5. “How would you scale this to peak holiday traffic?”

Approach: Partition by merchant or card token, shed non-critical work first, size for peak rather than average using the capacity anchor above, and explain how a payment record stays consistent if a region fails mid-flow.

How to Prepare in 3 Days

Day 1: the domain. Learn the four-party model, authorization versus capture versus settlement, and ISO 8583 pairs (0100/0110, 0400/0410).

Day 2: two full designs. Do the payment gateway and the fraud scoring service, 45 minutes each, out loud. Our system design interview guide gives the general framework.

Day 3: failure drills. Run a mock in OphyAI Interview Practice with the system design format and ask for pushback on failure: an acquirer timeout, a duplicate client request, a region outage, a reconciliation mismatch. Review the transcript for any case you hand-waved. Start practicing →

Common Mistakes

Boxes before money. Say what must never happen (a double charge, a lost authorization) before drawing anything.

Retrying blindly. A retry without the original identifiers is a second payment.

Related Guides

• Visa interview guide
• Plaid system design interview
• Affirm system design interview
• Revolut system design interview

Frequently Asked Questions

What is asked in the Visa system design interview?

Candidate reports and prep sites name payment-domain prompts: a payment gateway, a payment platform with retries, fraud detection, or an API gateway for transactions. Follow-ups cover timeouts, idempotency, double charging and reconciliation. Visa does not publish its question bank, so treat these as patterns.

How long is the Visa system design round?

Visa’s careers pages describe interview rounds of 30-60 minutes, and candidates report the technical design round at about 45-60 minutes. Plan to spend the first five to ten minutes on requirements and the payment flow, most of the time on the core design, and the last minutes on failure cases and scaling.

Do I need to know ISO 8583 for a Visa interview?

It is not required, but the basics help. Naming the authorization pair (0100 and 0110) and the reversal (0400) shows you know how a card payment moves. Interviewers care more that you know a timeout needs a reversal or status check than about field numbers.

Can I use AI tools during a Visa interview?

We found no published Visa policy on candidate AI use, so ask your recruiter and follow their answer. Our tracker of companies that allow AI in interviews lists what employers have said publicly. Either way, you need to defend every design choice yourself when the interviewer pushes on failure cases.

Sources and verification notes

Checked October 2026. The fetch tool could not reach external sites from this environment, so every source below was read through search summaries. Visa’s filings and fact sheet describe its network, not the interview; round format and prompts are candidate-reported or third-party.

• Visa Form 10-K, fiscal 2017 (SEC): VisaNet capacity of more than 65,000 transaction messages per second. First-party.
• Visa VisaNet fact sheet: 65,000+ capacity, footnoted as of August 2017. First-party.
• Visa Fiscal 2025 Annual Report: processed transactions for fiscal 2025 (about 257.5 billion, as reported in coverage of the results). First-party, figure via secondary summary.
• Visa, Smarter STIP: stand-in processing when issuers are unavailable. First-party.
• Visa Careers, interviewing: two to four rounds of 30-60 minutes. First-party.
• InterviewQuery, Visa software engineer guide: reported design prompts and loop. Third-party.
• Dataford, Visa software engineer interview: reported five-round loop and design focus. Third-party.
• Wikipedia, ISO 8583: message type indicators for authorization and reversal. Reference.
• Visa interview guide: the hub, with its own sources.