The 4 requests of the PISP role (STET V1.4.0.47)
The Payment Service Provider with the role of PISP can make 4 requests to the account holder's bank (ASPSP) of the debited customer (PAO).The Payment Service Provider with the role of PISP can make 4 requests to the account holder's bank (ASPSP) of the debited customer (PAO).
- /PaymentRequestsPost
This method sends all the information necessary to make a payment to the ASPSP. Payment may have been requested by the beneficiary (for example, the merchant or PSU) or by the account holder himself (the PAO).
- /PaymentRequestsGet
This method makes it possible to obtain the payment initiation data enriched with the initiation and payment status.
- /PaymentRequestsPut
This method makes it possible to send to the ASPSP a request to modify an already registered payment initiation request, provided that the payment has not yet been executed. This method is not yet available, the call to this request will return an HTTP code 405.
- /PaymentRequestsConfirmationPost
This method, linked to the so-called "embedded" authentication mode, allows confirmation of the payment request or cancellation of the payment request to the ASPSP by transmitting an authentication factor of the account holder debited so that the ASPSP may continue the request. This method is not yet available, the call to this request will return an HTTP code 405.