Skip to content

Settlement and reconciliation: a payments PM interview guide

How settlement and reconciliation work in card payments, why the topic shows up in payments PM interviews, and how to structure an answer to a settlement system design question.

On June 3, Mastercard announced plans to expand its settlement capabilities with intraday, weekend, and holiday options, including on-chain settlement in regulated stablecoins such as Circle's USDC and Ripple's RLUSD. Cross River, Lead Bank, and Nuvei are expected to be among the first to support the stablecoin option in the United States and Latin America. Four weeks later, more than 140 companies including Visa, Stripe, and Mastercard lined up behind Open USD, a consortium stablecoin announced on June 30 by Open Standard. Both moves target the same quiet layer of the payments stack: settlement.

If you are preparing for payments PM interviews, this layer deserves study, because settlement and reconciliation questions appear in system design rounds at networks, processors, and fintechs. Interviewers ask about it because payments PMs own the moments when money fails to land in the right account. A checkout flow has a UI you can demo. Settlement has files, cutoffs, and ledger entries that customers never notice until something goes wrong with a payout.

The vocabulary interviewers expect

Four terms anchor every settlement discussion. Authorization is the real-time yes or no on a transaction. Clearing is the exchange of transaction detail between acquirer and issuer, usually in batch files, so both sides agree on the amounts. Settlement is the actual movement of money between banks. Reconciliation is the work of proving that the money that moved matches the money you expected, record by record.

Clearing and settlement are easy to blur, and interviewers listen for the difference. Clearing moves information. Settlement moves funds. A transaction can clear today and settle tomorrow, and that gap is the origin of much of the complexity in this domain.

How card settlement works

A card purchase does not move money at the moment of the tap. The network totals what every issuer owes every acquirer, nets those obligations against each other, and instructs settlement banks to transfer the net amounts on a fixed cycle. Netting is the reason a network that processes billions in gross volume can settle with a far smaller set of wire transfers. The merchant then receives a payout from its acquirer on a schedule such as T+1 or T+2, minus fees.

Two details matter for interviews: cutoff times and settlement windows. A transaction cleared after the daily cutoff waits for the next window, which is why weekends and holidays create funding delays for merchants. That delay is the exact problem Mastercard's June announcement addresses, since intraday and weekend settlement shortens the time an acquirer or merchant waits for funds.

Where reconciliation fits

Settlement moves the money. Reconciliation proves the movement matched the plan. A payments company typically reconciles three records against one another: its own ledger, the processor or network settlement report, and the bank statement. This comparison is called a three-way match.

When a record in one source has no partner in another, the mismatch is called a break. Most breaks are timing differences, such as a transaction that settled a day earlier than the ledger's expected date. A smaller share are true errors, like duplicate captures or missing refunds. Those flow into an exception queue, where an operations analyst investigates each case.

Walking through the design question

A common prompt reads like this: design the settlement and reconciliation system for a marketplace that pays out thousands of sellers. Begin with the money flow before any database diagram. Trace one dollar from the buyer's card to the seller's bank account, and mark every point where it rests along the way: the acquiring bank, the platform's FBO account, the payout rail. Each resting point is a place where your records and someone else's records can disagree, so each one needs its own reconciliation job.

Next, define the source of truth. The internal ledger should capture the platform's view of every movement in double-entry form, independent of any external report. Reconciliation then becomes a comparison between that ledger and the outside world: network settlement files, bank statements, and processor payout reports.

Describe the matching logic in stages. Exact matches on amount and reference ID come first and clear the bulk of the volume. Looser matches on amount and date catch most of the remainder. Everything else lands in the exception queue with an owner and an age. Interviewers also want to hear how the design handles failure, so plan for late files, duplicate files, missing files, and partial files. Idempotent ingestion, which guarantees that a re-sent file cannot double-post, is the kind of detail that shows working familiarity with money movement.

Metrics that anchor the answer

A complete answer includes measurement. Match rate is the share of records that reconcile without human touch. Unreconciled aging tracks how long breaks stay open, bucketed by day. Time to close measures how quickly finance can finalize the books after a settlement cycle. Break rate by counterparty reveals which processor or bank produces the messiest data. Together these numbers show the health of the system and the location of the next engineering investment.

What always-on settlement changes

Connect the design back to the news. Intraday, weekend, and stablecoin settlement all shrink float, and float has long been a liquidity cushion. Raj Dhamodharan, who leads blockchain and digital assets at Mastercard, framed the change as a liquidity story: partners gain more control over how they manage liquidity in an always-on digital economy.

For a reconciliation system, always-on settlement removes the nightly boundary that used to define a reconciliation cycle. If money can move on a Sunday, matching jobs and exception queues need to run on a Sunday schedule. Stablecoin settlement also adds a new record type to the three-way match: the on-chain transaction. A public blockchain gives both counterparties a shared, timestamped record, which simplifies one leg of the match while adding wallet custody and treasury conversion as new sources of breaks.

An interview answer that touches these points demonstrates the reasoning interviewers are hiring for: you understand what faster settlement is worth, and you understand its price.

How to prepare

Spend an evening with public payout and reconciliation documentation from a processor such as Stripe, and sketch a three-way match for one real company. Then practice the marketplace prompt out loud, tracing the dollar, marking each resting point, and describing the exception flow. When the settlement question arrives in a real interview, the goal is to show how you reason about money at rest and money in motion, and how you design the checks that catch a missing cent before it reaches a customer.

Back to Live Blog