Code RoomPayout engine async bank settlement
HardPrep Room Coding #3506

Payout engine async bank settlement

System designDistributed systemsSenior~40 min

Design the payout engine that, on a schedule, nets each payee's earnings minus deductions into a single payout, batches thousands of payouts into ACH/SEPA files, submits them to a bank, and handles the slow, asynchronous, partially-failing nature of bank rails (a file is accepted but individual payouts bounce days later with return codes). ~800K payouts/day. A payout must be initiated exactly once, and a returned/failed payout must not be silently lost — the funds must flow back to the payee's available balance for retry. How do you keep the money correct across the multi-day async lifecycle?

What a strong answer looks like

Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.

Clarify4:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7:00 planned
0:00
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.