Top 5 Payments Interview Questions
Browse 5 real-world technical and behavioral interview questions about Payments. Review scenarios, edge cases, and architectural best practices.
A payment instruction is about to leave your firm that is a hundred times the usual size for that counterparty. What in your systems should stop it, and who should be looking at it?
The control has to sit before the irreversible boundary, and the strongest one is that the payment is derived from a recorded obligation rather than typed and approved. Four eyes on the same screen is not a second opinion, and an out-of-pattern check that runs in the morning reconciliation is running after the money has gone.
Design the checkout flow for a marketplace with multiple sellers per order.
Persist the order in a pending state before you touch the payment gateway, quote tax and shipping per seller shipment, authorise once behind an idempotency key, and commit the remaining steps through a transactional outbox and a saga whose compensations void the authorisation and release reserved stock.
A payment API times out and the client retries. How do you guarantee the customer is not charged twice?
Prevent a double charge on payment retry with an idempotency key tied to the purchase intent, a unique constraint, atomic charge recording, honest in-flight retry responses and settlement reconciliation.
Two people book the last seat at the same moment. Neither is allowed to see a failure after paying. What happens?
Preventing double booking seats means claiming the seat before payment, not racing two payments and reconciling later. A short atomic hold serialises buyers, payment only starts for the winner, and uncertain payment outcomes are settled by reconciliation rather than silent expiry.
When do you take the customer's money, and how much fraud are you willing to accept?
Authorise at checkout and capture when the goods leave, because an authorisation is a reversible hold and a capture is a refund waiting to happen; then set the fraud threshold from the full cost of a decline against the full cost of a chargeback, which usually means accepting more fraud than instinct suggests.