This method is used to initiate a payment at the ASPSP.
Variants of payment initiation requests
There are the following payment products:
- Payment products with payment information in JSON format:
- aspsp
- domestic
- foreign
Furthermore the request body depends on the payment-service:
- payments: A single payment initiation request.
- bulk-payments (NOT IMPLEMENTED YET): A collection of several payment initiation requests.
- periodic-payments (NOT IMPLEMENTED YET):
Create a standing order initiation resource for recurrent i.e. periodic payments addressable under {paymentId}
with all data relevant for the corresponding payment product and the execution of the standing order contained in a JSON body.
This is the first step in the API to initiate the related recurring/periodic payment.
Single and mulitilevel SCA Processes
The payment initiation requests are independent from the need of one or multilevel
SCA processing, i.e. independent from the number of authorisations needed for the execution of payments.
But the response messages are specific to either one SCA processing or multilevel SCA processing.
For payment initiation with multilevel SCA, this specification requires an explicit start of the authorisation,
i.e. links directly associated with SCA processing like 'scaRedirect' or 'scaOAuth' cannot be contained in the
response message of a Payment Initation Request for a payment, where multiple authorisations are needed.
Also if any data is needed for the next action, like selecting an SCA method is not supported in the response,
since all starts of the multiple authorisations are fully equal.
In these cases, first an authorisation sub-resource has to be generated following the 'startAuthorisation' link.