Description

The 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 PISP has previously sent a Request through a POST command.

• 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 was updated with the resource identifiers, and eventually the status of the Payment/Transfer Request and the status of the subsequent credit transfer.

Prerequisites

• The TPP was 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.2).
• The TPP has previously posted a Request which was 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 flow

The PISP asks to retrieve the Payment/Transfer Request that was 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 The status information must be available during at least 30 calendar days after the posting of the Payment Request. However, the ASPSP may increase this availability duration, based on its own rules.