GRgroupebpce
PISP

Retrieval of the Credit Transfert Transactions that were processed for a given payment request (PISP)

Description

The PISP gets the execution history of a payment request. This entry-point is an alternative to the retrieval of the history through the retrieval of the payment request. So, each ASPSP may choose or not to implement this entry-point.

Prerequisites

  • The TPP was registered by the Registration Authority for the PISP role
  • The TPP has previously posted a Standing Order Request which was saved by the ASPSP (cf. § 4.5.3)
    • The ASPSP has answered with a location link to the saved Payment Request (cf. § 4.5.4)
    • The TPP has retrieved the saved request in order to get the relevant resource Ids (cf. § 4.6).
  • The TPP and the ASPSP have successfully processed a mutual check and authentication
  • The TPP was provided with an OAUTH2 "Client Credential" access token by the ASPSP (cf. § 3.4.2).
  • The TPP presented its "OAUTH2 Client Credential" access token.

Business flow

The PISP post the history request. The ASPSP answers with the list of relevant transactions.

get/payment-requests/{paymentRequestResourceId}/transactions

Request

  • Base URL
    https://www.18919.live.api.89c3.com/stet/psd2/v1.6.2
  • Auth
    OAuth 2
    Client credentials
    Token URL: /stet/psd2/oauth/token scopes: pisp

Path parameters

paymentRequestResourceIdstring required

Identification of the Payment Request Resource

Headers

Authorizationstring required

Access token to be passed as a header

PSU-IP-Addressstring

IP address used by the PSU's terminal when connecting to the TPP

PSU-IP-Portstring

IP port used by the PSU's terminal when connecting to the TPP

PSU-HTTP-Methodstring

Http method for the most relevant PSU’s terminal request to the TTP

PSU-Datestring

Timestamp of the most relevant PSU’s terminal request to the TTP

PSU-GEO-Locationstring

Geographical location of the PSU as provided by the PSU mobile terminal if any to the TPP

PSU-User-Agentstring

"User-Agent" header field sent by the PSU terminal when connecting to the TPP

PSU-Refererstring

"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.

PSU-Acceptstring

"Accept" header field sent by the PSU terminal when connecting to the TPP

PSU-Accept-Charsetstring

"Accept-Charset" header field sent by the PSU terminal when connecting to the TPP

PSU-Accept-Encodingstring

"Accept-Encoding" header field sent by the PSU terminal when connecting to the TPP

PSU-Accept-Languagestring

"Accept-Language" header field sent by the PSU terminal when connecting to the TPP

PSU-Device-IDstring

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.

Digeststring

Digest of the body

Signaturestring required

http-signature of the request 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-IDstring required

Correlation header to be set in a request and retrieved in the relevant response

Response

retrieval of the Payment Request enriched with the status report

Changes

No recorded changes to this operation across all 1 revision of this API.