What is PIS?
The payment APIs, which follow the oAuth2 framework, will enable your application to initiate a SEPA payment from a KBC customer’s online payment account, with their explicit and authorised consent.
The process should begin by your application obtaining an explicit consent for the payment from a customer and then requesting the customer to authorise the consent using their KBC online banking/mobile banking credentials. Once the consent has been authorised, your application will be able to request the execution of the payment.
The payment APIs will enable your application to check the status of the consent authorisation and payment execution.
Who is it for?
• Third party payment service providers
• Financial services firms
KBC Ireland has provided the following endpoints to allow the initiation and execution of a payment from the application.
||Create a consent record.
||Retrieve the status of the consent record.
||Create a payment record. This API should be used to execute the authorised payment.
||Retrieve the status of the payment record.
These endpoints comply with the Payment Initiation API Specification of the Open Banking standards. Detailed documentation of our implementation is available post registration.
A outline for the payments flow can be seen below (source: Open Banking):
KBC Ireland will support both web redirection and mobile application redirection for consent authorisation. The TPP application on a mobile device will be able to deep link into the KBC Ireland mobile application. In the event the customer does not have the mobile application installed on their device, they can expect that the TPP application will automatically redirect the customer to KBC Ireland online banking website, using the web-redirect method.
Please read this document (pdf, 176 KB) for more information on the KBCI Authorisation flow.
September 13, 2019 – APIs are now live. Register your application using our Dynamic Registration APIs.