The Payments Initiation BBK Open Banking API enables TPP applications to make payments directly from a customer's account. Customers remain in control, providing approval for each payment.
BBK payment initiation Open banking API provides the following services to TPPs:
- Payment initiation (international future dated single payments, bulk/batch payments, domestic standing order, international standing order)
- Funds confirmation (for International Future Dated Payments only)
- Requesting payment consent/payment status
- Requesting payment details
BBK payment initiation Open banking API allows the following types of payments:
- Bulk/Batch Payment
- International Future Dated Payment
- Domestic Standing Order Payment
- International Standing Order Payment
The Payment Initiation is intended to initiate a payment (international future dated single payments, bulk/batch payments, domestic standing order, international standing order) with the consent of the customer.
The process of gaining confirmation of payment request from a customer is a multi-step process. TPP must complete each of the steps below in order to initiate a payment request:
- User consents to a PISP to make a payment on behalf a customer and PISP connects to Bank’s API to create a payment-consent resource using POST /{payment type}-payment-consents. This request is an instruction to the Bank to begin the Bulk/Batch payment journey.
- Bank responds with an identifier for the resource (PaymentConsentId) and redirection URL.
- For Bulk/Batch Payments, PISP additionally sends pain.001 file with payment details to Bank’s using POST /file-payment-consents/{ConsentId}/file.
Related security requirements:
- request must contain TPP public access token;
- request must contain user token.
- The PISP redirects the customer to the BBK authorization page and Bank authenticates the customer. Once the consent has been authorised, the customer is redirected back to the PISP.
- For International Future Dated Payments, PISP can confirm the availability of funds before submitting a payment using GET /international-future-dated-payment-consents/{ConsentId}/funds-confirmation.
- Once the payment-consent has been authorised by the customer, the PISP can proceed to submitting the payment for processing using POST /{payment type}.
Related security requirements:
- request must contain TPP consent access token;
- request must contain user token.
Bulk/Batch Payment API allows customer initiation of domestic payment bulk/batch including EFTS NRT, DNS and BIL payments.
Read more...
International Future Dated Payment API allows customer initiation of scheduled international SWIFT MT103 and GCCNET payments.
Read more...
¶ Domestic Standing Order Payment
Domestic Standing Order Payment API allows customer initiation of Standing Order Payment for scheduled EFTS NRT, DNS and BIL payments.
Read more...
¶ International Standing Order Payment
International Standing Order Payment allows customer initiation of Standing Order Payment for scheduled international SWIFT MT103.
Read more...