How it works
When a customer chooses to pay by bank using one of the registered Third Party apps, the Payment Initiation API standard enables the following:
- The Third Party starts the payment initiation flow by sending the customers payment request to the API Provider (e.g. the customer’s bank).
- The Third Party directs the customer to their bank app or website where they can be authenticated. You can learn more about the customer experience options here.
- The API Provider displays the payment request details, and the customer selects the account they will pay from before authorising the payment.
- The API Provider sends confirmation to the Third Party that the customer has authorised the payment.
- The Third Party submits the payment for processing.
The API Provider processes the payment.
Payment Initiation API illustration
Enduring Payment Consent
It's possible for the customer to authorise multiple payments at once. This enables, for example, regular fixed subscription payments, bill that might vary from month to month, or smooth experience at the coffee shop they frequent.
Using the Enduring Payment Consent, the authorisation flow is streamlined so the customer will not have to authorise their bank to make each individual payment.
Enduring payment consent illustration
