Timeline comparison across rails

Four rails can carry the same EUR 10,000 payment from Paris to Berlin, and the timelines are so different that the choice of rail is a business decision, not a technical default. The four rails are SCT Inst through TIPS, SEPA Credit Transfer through STEP2, a cross-border correspondent payment through SWIFT, and a card payment through the card scheme, and the comparison below uses the same amount, the same debtor and creditor, and the same business day, Monday 9 November 2026, so the differences are the rails, not the payment. Source: Regulation (EU) 2024/886; European Payments Council, SCT and SCT Inst Rulebooks 2025; Bank for International Settlements, Committee on Payments and Market Infrastructures. On SCT Inst the timeline is 10 seconds. At 10:00:00 the customer submits a pain.001, at 10:00:04 Bank A sends a pacs.008, at 10:00:09 TIPS settles in central bank money, and at 10:00:10 the supplier is credited and the customer is confirmed. The cost is low, the data is rich, because the pacs.008 carries full remittance information, and the failure handling is a rejection within 10 seconds, with the reservation released. The customer submits at 10:00, Bank A sends a pacs.008. The cost is low, the data is rich, and the failure handling is a return by pacs.004, which can take a day. The difference between the two is speed and settlement timing, not the message, because both use pacs.008. On a cross-border correspondent payment the timeline is 4 hours to 2 days, depending on the chain, the time zones and the cut-offs. The customer submits at 10:00, Bank A sends a pacs.008 to the intermediary at 11:00, the intermediary forwards at 13:00, the beneficiary bank credits at 15:00, and the confirmation reaches the customer at 16:00, if every bank in the chain is open and no bank holds the payment for review. The cost is higher, because each bank in the chain charges a fee, and the data can be truncated at each hop, because the pacs.008 is re-created by each bank, and a field that one bank does not support may be lost. The failure handling is a pacs.002 rejection or a pacs.004 return, which can take days to travel back through the chain. On a card payment the timeline is split into authorisation and settlement, which is a different model from the other three. At 10:00:00 the customer pays by card, at 10:00:02 the issuer authorises, and the merchant is told the payment is approved, but the merchant is not yet paid. The authorisation is instant, the settlement is next day, and the merchant bears the chargeback risk for up to 120 days under the scheme rules. The cost is higher than a credit transfer, because interchange, scheme fees and acquirer margin are all deducted, and the data is limited, because the ISO 8583 authorisation carries less remittance data than a pacs.008. The failure handling is a decline at authorisation, a chargeback after settlement, or a reversal, each with its own message and timeline. The comparison shows that speed, cost, data and risk trade off against each other, and no rail wins on all four. SCT Inst wins on speed and settlement, SEPA Credit Transfer wins on cost and data for non-urgent payments, the correspondent payment wins on reach, because it can pay any bank in the world, and the card payment wins on authorisation, because the merchant knows instantly that the payment is approved, even though settlement is later. A business analyst who recommends a rail on speed alone will choose SCT Inst for a payment that needs rich data and low cost. The correct recommendation states the requirement first, then the rail that meets it, with the timeline, the cost, the data and the failure handling for each option. The effect on the bank, the customer and operations is that the rail choice decides the whole operating model. For the customer, the rail decides when the money arrives, what it costs, what data travels with it, and what happens when it fails. For the bank, the rail decides the message set, the clearing system, the settlement account, the liquidity need and the regulatory reporting. For operations, the rail decides the exception queue, the reason codes, the return timelines and the reconciliation source. A product that routes silently, without telling the customer, will generate complaints when the payment arrives late or with a fee the customer did not expect. For a business analyst, product owner or subject matter expert, the test is to produce this comparison for any payment and to defend the recommendation. Ask what the deadline is, what the amount is, what the currency is, where the beneficiary bank is, how much data must travel, what the cost budget is, and what the failure tolerance is. Ask how the customer is told which rail was used, and how the status is tracked. The sources for the timelines are the scheme rulebooks: the EPC SCT and SCT Inst Rulebooks 2025, Regulation (EU) 2024/886 for the 10-second rule, and the SWIFT CBPR+ usage guidelines for the cross-border chain, and each must be cited with version and effective date. Two mistakes are common in rail comparison. The first is to compare the authorisation time of a card payment with the settlement time of a credit transfer, which makes the card look instant when it is not, because the merchant is not paid until the next day. The second is to compare the customer credit time with the interbank settlement time, which makes a retail payment look settled when it has only been cleared, and the interbank settlement is still to happen. The correct comparison states, for each rail, the authorisation time, the customer credit time, the interbank settlement time and the finality time, as four separate times, so that the comparison is honest and the customer is not misled. Takeaway: SCT Inst settles in 10 seconds, SEPA Credit Transfer credits by the next business day, a correspondent payment takes 4 hours to 2 days through a chain, and a card payment authorises in seconds but settles the next day. No rail wins on speed, cost, data and risk at once, so choose by requirement and state the timeline, the cost, the data and the failure handling for each option. Further reading: Regulation (EU) 2024/886; European Payments Council, SCT and SCT Inst Rulebooks 2025; Bank for International Settlements, Committee on Payments and Market Infrastructures. Last reviewed 7 November 2026.