The model assembles three core agent populations operating on a shared settlement infrastructure. Banks are the primary agents: each holds an intraday liquidity position (reserves at the central bank), a queue of outgoing payment obligations with associated deadlines and priorities, and a behavioral strategy governing when to release payments versus hold them in queue. Bank populations range from 15 to 80 in realistic calibrations (matching actual LVPS participant counts) and 5 to 20 in browser-scale demonstrations. The central bank is the second agent: it sets intraday credit terms (collateralized or free), operates the settlement mechanism (RTGS queue, netting algorithm, or hybrid), and intervenes when gridlock threatens systemic stability. The third population is an exogenous payment generator that produces the daily flow of payment obligations between banks, calibrated to match the empirical distribution of payment values, timing, and bilateral concentration observed in actual system data.
Interaction happens through the settlement network. When Bank A submits a payment to Bank B, the system checks whether A has sufficient reserves (including any available intraday credit). If yes, the payment settles immediately: A's reserves decrease, B's reserves increase. If not, the payment enters A's queue. Queued payments create dependencies: B may be waiting for that incoming payment to fund its own outgoing obligations to C, D, and E. The netting or offsetting algorithm periodically scans for cycles of queued payments that can be settled simultaneously without any bank's balance going negative. This cycle-detection mechanism is the key institutional feature that separates modern hybrid RTGS systems from pure gross settlement. The network topology - who pays whom and in what amounts - is drawn from empirical transaction data showing heavy concentration among a few core banks.
State variables update within each simulated business day on a minute-by-minute or payment-by-payment basis. The intra-day timeline proceeds: (1) banks receive their day's payment obligations, (2) at each tick, banks decide which payments to release based on their strategy, (3) submitted payments settle immediately if funded or enter the queue, (4) the netting algorithm runs periodically (every N minutes or when the queue exceeds a threshold), (5) the central bank monitors aggregate queue depth and may inject emergency liquidity, (6) at end-of-day, remaining queued payments are either force-settled using end-of-day borrowing or fail. This granular intra-day resolution is what distinguishes payment system ABMs from models that treat settlement as a single daily event.