GET - paymentRequestsGet
Retrieval of a payment request (PISP)
DescriptionThe following use cases can be applied:
- retrieval of a payment request on behalf of a merchant
- retrieval of a transfer request on behalf of the account's owner
- retrieval of a standing-order request on behalf of the account's owner
The ASPSP has registered the Request, updated if necessary the relevant identifiers in order to avoid duplicates and returned the location of the updated Request.
The PISP gets the Request that might have been updated with the resource identifiers, the status of the Payment/Transfer Request and the status of the subsequent credit transfer.
- The TPP has been registered by the Registration Authority for the PISP role
- The TPP was provided with an OAUTH2 "Client Credential" access token by the ASPSP (cf. § 3.4.3).
- The TPP has previously posted a Request which has been saved by the ASPSP (cf. § 4.5.3)
- The ASPSP has answered with a location link to the saved Payment/Transfer Request (cf. § 4.5.4)
- The TPP and the ASPSP have successfully processed a mutual check and authentication
- The TPP has presented its "OAUTH2 Client Credential" access token
Business flowThe PISP asks to retrieve the Payment/Transfer Request that has been saved by the ASPSP. The PISP uses the location link provided by the ASPSP in response of the posting of this request.
The ASPSP returns the previously posted Payment/Transfer Request which is enriched with:
- The resource identifiers given by the ASPSP
- The status information of the Payment Request and of the subsequent credit transfer
|Authorization (required)|| |
Access token to be passed as a header
|paymentRequestResourceId (required)|| |
Identification of the Payment Request Resource
IP address used by the PSU's terminal when connecting to the TPP
IP port used by the PSU's terminal when connecting to the TPP
Http method for the most relevant PSU’s terminal request to the TTP
Timestamp of the most relevant PSU’s terminal request to the TTP
Geographical location of the PSU as provided by the PSU mobile terminal if any to the TPP
"User-Agent" header field sent by the PSU terminal when connecting to the TPP
"Referer" header field sent by the PSU terminal when connecting to the TPP. Notice that an initial typo in RFC 1945 specifies that "referer" (incorrect spelling) is to be used. The correct spelling "referrer" can be used but might not be understood.
"Accept" header field sent by the PSU terminal when connecting to the TPP
"Accept-Charset" header field sent by the PSU terminal when connecting to the TPP
"Accept-Encoding" header field sent by the PSU terminal when connecting to the TPP
"Accept-Language" header field sent by the PSU terminal when connecting to the TPP
UUID (Universally Unique Identifier) for a device, which is used by the PSU, if available. UUID identifies either a device or a device dependant application installation. In case of installation identification this ID need to be unaltered until removal from device.
Digest of the body
|Signature (required)|| |
http-signature of the request (cf. https://datatracker.ietf.org/doc/draft-cavage-http-signatures/) The keyId must specify the way to get the relevant qualified certificate. It is requested that this identifier is an URL aiming to provide the relevant Qualified Certificate.
|X-Request-ID (required)|| |
Correlation header to be set in a request and retrieved in the relevant response
|200||Retrieval of the previously posted Payment Request|
|405||Method Not Allowed|
|429||Too Many Requests|
|500||Internal Server Error|