ORIGINAL COMPANY-CONTEXT PRACTICE
Track a simulated cross-border transfer
Original practice scenario: A fictional banking exercise moves a transfer through several institutions, currencies and business calendars. Design its customer-visible status model.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
A transfer is a multi-stage workflow with independent acknowledgements and reversals. Customer-visible states should reflect confirmed evidence instead of promising finality from an intermediate message.
Work through it
- Create a stable transfer identity and append stage events with source, effective time, currency and amount; define legal transitions and unresolved states.
- Separate quote acceptance, debit, intermediary progress and beneficiary confirmation, using idempotent outbound requests and reconciled inbound events.
- Test duplicate callbacks, delayed confirmations, partial fees, calendar boundaries and corrections, with an exception queue for mismatched amounts or references.
Tradeoffs to discuss
- A detailed state model improves transparency but must translate technical stages into understandable customer messages.
Common pitfalls
- Do not label an intermediary acknowledgement as final settlement.
- Keep synthetic conversion rates and calendars explicit rather than implying current banking rules.