SEPA CREDIT TRANSFER – HAPPY PATH

-

 Sepa Credit Transfer – Happy Path:

Now that we understand the primary actors of the 4 corner model it is time to seal that understanding by taking an example of the happy path of an Sepa Credit Transfer scheme. We will discuss about the different messages that are involved and in which order they are exchanges between the different actors.

Sepa credit transfer
S0701

Before we decipher the above picture for ease of understanding I have made the following assumptions

  1. The payment is initiated by a private customer some like you and me
  2. The payment is processed by a CSM containing only the two banks involved
  3. Payments are not cleared in Batch
  4. Customers receive notification from the bank Via. SMS/email

Step 1: Customer (Originator) logs into their internet banking portal, enters the details of the beneficiary and initiates payment.

Step 2: The IT system of the bank (Originator PSP) converts the customer’s instruction into a pain.001 messages and sends into the bank’s payment engine.

Step 3: Originator PSP’s payment engine processes the payment instruction received from the originator by performing different checks that include balance checks.

Step 4: Originator PSP recognizes that the beneficiary belongs to another bank (Beneficiary PSP). It debits the Originator’s account and sends a pacs.008 message as per the rule of the SCT scheme Via CSM.

Step 5: CSM validates & settles the payment. It forwards the pacs.008 to the beneficiary bank.

Step 6: Beneficiary PSP receives the pacs.008 from the CSM validates the payment and completes the processing.

Step 7: Funds are made available to the beneficiary.   

What are these pain.001 and pacs.008 messages that I talk about ?? To get an answer to this question please refer to my earlier article on the SEPA payment messages.

Do ckeck out the SEPA rulkebook and the next article Reject flow

Popular posts from this blog

SWIFT MT – SERIAL AND COVER METHOD

-
Image
  SWIFT MT – Serial and Cover Method This is one of the most important articles from SWIFT payments’ perspective and it is critical that you fully understand the concepts laid out here. Payments are cleared and settled via 2 primary methods: Through a payment market infrastructure (PMI) Through correspondent banking Through payment market infrastructure: This is the case where bank A and bank B are direct participants of this PMI aka CSM. IN General usage the concept of serial and cover does not apply here but if you put a gun to my head, I would say is very close to the serial method. Through correspondent banking: This is the case where banks open accounts with each other (Nostro/Vostro) and settle funds directly. The prerequisite here is that banks need to open accounts with each other or in other words they need to have an  accounting relationship  with the other bank. Now, let us try to understand the connection between sending/receiving SWIFT messages and the moveme...
Read more

PAYMENT ENGINES

-
Image
  Payment Engines: I am really excited about this topic as it’s my favorite and the one in which I have the most experience. In this article, we will be discussing about a piece of software called “payment engine” . They are part of the bank’s IT ecosystem and they help banks process hundreds of thousands of payments a day seamlessly. In the previous articles, we discussed the different message types and how banks send these messages to each other. Payment engines help banks to send, receive and process payments. We will discuss only credit transfers here. Direct debits can be parked for the Future. We will approach this subject  without any particular payment engine or message scheme in our minds . Once we get the bigger picture knowing specifics will be much easier. A0501 From a payment engines’ perspective there are 4 types of payments: Incoming Outgoing Book Redirect We will briefly see what these types are and then dive right into the flows. Banks processes each of these ...
Read more

SWIFT MTS – BLOCKS 1 THROUGH 5

-
Image
  SWIFT MTs – Blocks 1 Through 5 We have discussed in our previous article that there are 5 blocks in a SWIFT MT message. Now we will dive deep into each of these blocks and try to understand them in detail. Please save this page for your future reference (At least till 2025) There are some common details and we will try to understand what they are All the blocks start with “{” The Block number or block identifier will be displayed at the very beginning followed by a “:” (Separator) This will be followed by the contents of the block The block will end with a “}” Basic Header Block (Block 1 ) This block is the only mandatory block and contains general information identifying a message.  Let us now dissect the block {1:F01CITIFRPPAXXX0070970817} This can be split into different components ( Split using spaces) {  1  :  F  01  CITIFRPPAXXX  0070 970817} F  – This is application Identifier or AppID . F Indicated that it is a FIN message 01  ...
Read more