GRgroupebpce
PISP

Confirmation of a payment request using an OAUTH2 Authorization code grant (PISP)

Description

The PISP confirms one of the following requests or modifications:

  • payment request on behalf of a merchant
  • transfer request on behalf of the account's owner
  • standing-order request on behalf of the account's owner The ASPSP answers with a status of the relevant request and 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 Request (cf. § 4.5.4)
  • The TPP has retrieved the saved request in order to get the relevant resource Ids (cf. § 4.6).
  • The PSU was authenticated by the ASPSP through an OAUTH2 authorization code grant flow (REDIRECT approach) and the PISP got the relevant token
  • The TPP and the ASPSP have successfully processed a mutual check and authentication
  • The TPP has presented its "OAUTH2 Authorization Code" access token

Business flow

Once the PSU was authenticated through an OAUTH2 authorization code grant flow (REDIRECT approach), it is the due to the PISP to confirm the Request to the ASPSP in order to complete the process flow. The ASPSP must wait for confirmation before executing the subsequent Credit Tranfer. Any further confirmation by the PISP on the same Payment-Request must be ignored.

post/payment-requests/{paymentRequestResourceId}/confirmation

Request

  • Base URL
    https://www.18919.live.api.89c3.com/stet/psd2/v1.6.2
  • Auth
    • OAuth 2
      Authorization code: /psd2/oauth/authorize
      Token URL: /stet/psd2/oauth/token scopes: pisp
    • or 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

Request body

noncestring

Challenge to be sent in order to avoid replay of the authentication process.

psuAuthenticationFactorstring

authentication factor forwarded by the TPP to the ASPSP in order to fulfil the strong customer authentication process

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.