Components 7 to 12: From Fraud Checks to Clearing

The Fraud Detection Engine scores every payment for the likelihood that it is unauthorised, manipulated or part of a scam. What comes in is the screened payment plus behavioural context, including device data, login history, typical amounts, payee history and velocity over the last 24 hours. What it does is run rules and machine learning models, compare the payment against the customer normal pattern, and produce a risk score with reasons. What goes out is an approval, a step up authentication challenge, or a block with a fraud case. If it fails, two bad outcomes follow. A false negative lets a 90,000 pound authorised push payment fraud through, while a false positive blocks genuine payments and drives customers to call the bank in frustration. The Payment Orchestrator is the conductor that coordinates the whole journey of a payment through the hub. What comes in is a screened and fraud checked payment plus the state of every downstream service. What it does is manage the workflow state machine, call components in the right order, handle branching for different payment types, and track each payment from received to settled or rejected. What goes out is a sequence of ordered service calls and a single consistent payment status that channels, operations and customers can all read. If it fails, payments stall in unknown states, duplicate processing becomes likely, and operations teams cannot tell a customer whether a 1 million dollar payment is sent, held or lost. The Routing Engine decides the best path for each payment to reach its destination. What comes in is the payment with amount, currency, destination country, urgency, cost limits and the beneficiary bank details. What it does is apply routing tables and business rules, choosing for example between SWIFT gpi, a local clearing system, an instant payment rail, or a correspondent bank, based on cost, speed, cut off times and availability. What goes out is a selected route with the next hop, the expected arrival time and the fee estimate. If it fails, payments take expensive or slow routes, miss cut off times, or fail entirely, so a time critical 5 million euro treasury payment may arrive a day late and breach a contract. The Payment Processing Engine executes the payment on the chosen route and manages the message exchange with the outside world. What comes in is a routed payment with the correct message format specification for its rail. What it does is build the outbound message, such as a pacs.008 for an ISO 20022 rail or an MT103 for a SWIFT payment, send it, wait for acknowledgements, and handle timeouts, retries and confirmations. What goes out is a transmitted message plus a delivery acknowledgement or a failure notice. If it fails, payments may be sent twice, never sent at all, or sent without confirmation, and a processing failure during a peak hour can leave thousands of payments in an unconfirmed state that operations must resolve manually. Liquidity Management makes sure the bank has enough funds in the right place at the right time to settle its payments. What comes in is the queue of outgoing payments plus the bank positions at central banks, correspondent banks and clearing accounts. What it does is forecast intraday liquidity, prioritise urgent payments, hold lower priority payments when funds are short, and move funds between accounts to cover shortfalls. What goes out is a funding decision for each payment, either release, hold, or queue with a scheduled release time. If it fails, the bank may overdraw a settlement account, miss a central bank deadline, or delay critical payments, and a liquidity shortfall of 200 million dollars at a CHAPS cut off can trigger regulatory attention and penalty interest. Clearing Connectivity is the set of adapters and connections that link the hub to external clearing systems and networks. What comes in is a formatted payment message ready for a specific rail, such as Faster Payments in the United Kingdom, SEPA in Europe, Fedwire in the United States, or SWIFT for cross border payments. What it does is manage secure connections, certificates, message queues, acknowledgements and end of day files for each clearing system. What goes out is a submitted clearing instruction and a clearing reference that proves submission. If it fails, the bank is cut off from that rail entirely, so every payment for that system queues up, customers see delays, and a four hour SWIFT connectivity outage can strand billions of dollars in pending cross border payments.