Hello, my name is Guillaume, I’m a software engineering intern at TESOBE. Today I’m going to present how we can send a SEPA credit transfer transaction with the OBP SEPA Adapter.
Firstly, maybe to remember how the adapter works, we have an application that needs a kind of core banking solution, we consider that the OBP API provides this core banking solution and that the OBP SEPA Adapter is connected to the Clearing & Settlement Mechanism and the OBP API, and provides the SEPA payment solution like a translator to translate the information sent by OBP API into XML files.
So, let’s see how we can process a SEPA transaction with this adapter. First of all, the application can create a SEPA transaction request, then the transaction request is accounted for in the OBP database. Once the transaction request passes to the completed status – it can be instantly, or after achieving completion – the “Make payment” message is sent to the OBP SEPA adapter through Akka. The adapter first saves the transaction in OBP, this is going to withdraw the transaction amount from the OBP account and save the transaction in OBP.
So, up to this moment, the app can get the transaction to see the transaction in OBP. It’s not a transaction request anymore. Then, once the transaction has been saved in the OBP API, the SEPA adapter is going to save the transaction in its database, and then about 3 or 4 times a day, the SEPA adapter is going to process all the pending transactions that haven’t been sent yet.
It’s going to pack all of those transactions into one XML find and then send this XML file to the Clearing & Settlement Mechanism.
So, I can show you a demonstration. We can suppose that I currently have an OBP API instance running. Also an instance of my adapter running. So I have an account with this balance and with a routing scheme by IBAN. So, I also have no transactions at the moment on this account and I have a counterparty existing in my account with a bank-routing scheme to BIC, with the BIC address, and the corresponding IBAN for my counter-party.
I want to create a transaction request to send money to Louis Dupont, who has this IBAN. So, I can set up the amount. So let’s send, for example, €50. So we can send the transaction request… OK, it succeeds. So what happened? The transaction request passed to the completed status and called my SEPA adapter and then created a transaction in OBP.
Here we have a transaction ID: 9206. And if we go to a transaction for our account, we have 9206. We have the transactions in OBP API. So everything is ok on the OBP API side, now let’s see what happened on the Adapter side.
On the adapter side, a transaction has been created. In the SEPA adapter, we are only dealing with IBAN and BIC to identify accounts and banks. So, we are here: adapter name, adapter account, and adapter agent. The same for the creditor, we have the description, the creation date, and other ID that will be present in the SEPA file, and it’s currently unprocessed.
Another thing is that a SEPA message has been created. For the moment, the SEPA message is unprocessed but the SEPA message is linked to our transaction through this table. So now we want to send the transaction to the Clearing & Settlement Mechanism so we are currently here. We have all credit transfer transactions saved in our SEPA adapter database and we want to generate the XML file.
To do this, we just simply execute some script to process your outgoing file… I’m going to run this… ok, it says one transaction has been accounted for in this file, we can open the file, which is this one, format it and see that we have all the corresponding information to our transaction request. Then, it’s these kinds of files that are sent to the CSM.
Thank you for listening and in the next video, we’ll see how we can receive transactions from SEPA. Thank you.