Overview
The Payment product allows you to create payments (e.g. single payments and periodic payments).
The product is PSD2-compliant.
Step-by-step how to use the Payment product
Initial activities
Enrollment and TPP security need to be in place.
For every payment
This flow shows how to initiate and authorize a payment (including Strong Customer Authentication):
Signing basket (for WebBank Corporate agreements only)
A corporate PaymentServiceUser (PSU) can initiate several payments and sign all payments using a signing basket.
The feature is not available for private PaymentServiceUsers.
Here is the simple step-by-step:
POST a payment and get a paymentID in return.
POST several payments. Check limitations in the payment yaml-file.
Create a signing basket using all the paymentIDs and use the flow shown above.
Let a corporate PSU sign the content of the signing basket.
If the payments require signing by more than 1 PSU, you can create a new signing basket with paymentIDs needing further signing.
Additional authentications of payments can also be handled by PSUs in the WebBank Corporate using the payment overview.
Get account-list if you only have PISP role
Use the paisprepare scope and get consent from the PSU to get account-list before initiating a payment.
The paisprepare scope does not give access to accountbalances nor transactions.
The process is similar to using the aisprepare scope.