SCT lifecycle checkpoint
Check that you can follow a SEPA Credit Transfer end to end: what SEPA is, how the four-corner model works, how the message chain runs from pain.001 to the beneficiary credit, and what changes when the payment is instant.
QUESTIONS AS TEXT
Q1. What is SEPA, in one sentence?
Answer: A: A set of common schemes and rules that let customers make euro payments across participating countries as easily as domestic ones.
SEPA — the Single Euro Payments Area — standardizes euro credit transfers and direct debits across participating countries through scheme rulebooks maintained by the European Payments Council. The practical effect is that one set of formats, roles, and exception procedures works across borders, so a euro transfer from Lisbon to Helsinki follows the same scheme as one across town.
Q2. Order the steps of a SEPA Credit Transfer, from the customer's instruction to the beneficiary being credited.
Answer: 1. The debtor sends a pain.001 payment initiation to their bank (pain.001 is the customer's initiation — the lifecycle starts on the customer-to-bank leg.) 2. The debtor agent validates the instruction and debits the debtor's account (The debtor agent validates and debits before it creates any interbank obligation in the debtor's name.) 3. The debtor agent sends a pacs.008 into the CSM (Acceptance turns the customer instruction into an interbank pacs.008 heading into the clearing mechanism.) 4. The interbank obligation settles between the participants (The interbank obligation settles between participants before the beneficiary's credit is final.) 5. The creditor agent credits the creditor, and status and reporting messages confirm the outcome (Crediting the creditor and reporting the status close the loop once the interbank legs are done.)
The handoff in the middle is the one to remember: the customer's pain.001 becomes the interbank pacs.008 the moment the debtor agent accepts it. From there the CSM exchanges the instruction, settlement discharges the obligation between the banks, and the creditor agent completes the customer leg by crediting the account.
Q3. What is the key operational difference between SCT and SCT Inst?
Answer: A: SCT processes payments in cycles on business days; SCT Inst processes each payment individually, around the clock, with an immediate positive or negative confirmation within the scheme's time limit.
SCT is a batch scheme: instructions accumulate and clear through cycles on business days, so timing depends on cut-offs and the CSM's schedule. SCT Inst handles one transaction at a time, every day of the year, and the debtor agent learns the outcome — accepted or rejected — before telling the customer. That real-time confirmation is what makes the model demanding to operate: every component in the chain must answer within the scheme's time limit.
Q4. SEPA schemes are described with a four-corner model. What are the four corners, and what sits between them?
Answer: A: Debtor, debtor agent, creditor agent, and creditor at the corners, with the scheme and CSM connecting the two agents in the middle.
Each customer deals only with their own payment service provider: the debtor instructs the debtor agent, the creditor is credited by the creditor agent, and the two agents reach each other through the scheme's rules and a CSM. The model matters because it explains who can act on what — for example, why a debtor who wants funds back can only ask their own bank to start a recall, never contact the creditor agent directly.
Q5. The debtor agent receives this fictional fragment shortly after sending a pacs.008. What is it telling them?
Answer: A: It is a payment status report (pacs.002): the original transaction, identified by its end-to-end reference, has been accepted — this status code indicates settlement is completed.
The root element FIToFIPmtStsRpt marks this as a pacs.002 payment status report, and the OrgnlEndToEndId points back at the specific transaction it answers. Status codes come from the ISO 20022 external code sets — ACSC indicates acceptance with settlement completed, while a rejection would carry RJCT plus a reason code. In SCT Inst this message is what allows the debtor agent to tell its customer the payment succeeded. All references in the excerpt are fictional.