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
- Funds confirmation
- Requesting payment consent/payment status
- Requesting payment details
- Payment cancellation (for future dated payments only)
BBK payment initiation Open banking API allows the following types of payments:
- Single domestic payments;
- Single future dated domestic payments;
- Single international payments.
The Payment Initiation is intended to initiate a single payment 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 single payment journey.
Related security requirements:
- request must contain TPP public access token;
- request must contain user token.
- Bank responds with an identifier for the resource (PaymentConsentId) and redirection URL.
- The PISP redirects the customer to the BBK authorization page and Bank authenticates the customer. During authorisation, the customer can select debit account from the list of own accounts in the BBK authorization page in case this has not be done in TPP application. Once the consent has been authorised, the customer is redirected back to the PISP.
- PISP can confirm the availability of funds before submitting a payment using GET /{payment}-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}-payment.
Related security requirements:
- request must contain TPP consent access token;
- request must contain user token.
Single Domestic Payment API allows customer initiation of domestic payments including EFTS NRT, DNS and BIL payments.
Read more...
Single Future Dated Domestic Payment API allows customer initiation of scheduled EFTS DNS and BIL payments.
Read more...
Single International Payment API allows customer initiation of international SWIFT MT103 and GCCNET payments.
Read more...