Operations & architecture
What payment operations teams actually do, how payment hubs are built, the accounting behind every transfer, and how exceptions get investigated.
- 0110 MINA day in payment operationsQueues, cut-offs, and exceptions: what a payment operations team actually watches from start of day to close, and why straight-through processing is the metric.AFTER: The payment lifecycle
- 0215 MINPayment engines and hub architecturePayment engines and hubs: the systems between channels and rails, and the design choices that decide how painful every future change will be.AFTER: A day in payment operations
- 0312 MINAccounting entries and ledgersEvery payment ends as balanced ledger entries: customer accounts, nostros, and the suspense accounts that hold whatever cannot post cleanly.AFTER: Money, accounts, and ledgers · Correspondent banking, nostro & vostro
- 0412 MINExceptions and investigationsWhen a payment goes wrong after it has left: cases, queries, cancellation requests, and the discipline that gets money and explanations back.AFTER: A day in payment operations · R-transactions: reject, return, recall
- 0512 MINNostro reconciliationMatching what your ledgers say happened against what your correspondents say happened — and chasing every unexplained break until it is explained.AFTER: Accounting entries and ledgers
- 068 MINPayment security and fraud basicsPayment security in layers: authentication, dual control, Verification of Payee, monitoring, and why instant rails move controls earlier.AFTER: A day in payment operations