Skip to main content

InitiatePaymentLinks

A list of hyperlinks to be recognised by the TPP. The actual hyperlinks used in the response depend on the dynamical decisions of the ASPSP when processing the request.

Remark: All links can be relative or full links, to be decided by the ASPSP.

Type of links admitted in this response, (further links might be added for ASPSP defined extensions):

  • 'scaRedirect': In case of an SCA Redirect Approach, the ASPSP is transmitting the link to which to redirect the PSU browser.
  • 'scaOAuth': In case of a SCA OAuth2 Approach, the ASPSP is transmitting the URI where the configuration of the Authorisation Server can be retrieved.The configuration follows the OAuth 2.0 Authorisation Server Metadata specification.
  • 'confirmation': Might be added by the ASPSP if either the "scaRedirect" or "scaOAuth" hyperlink is returned in the same response message. This hyperlink defines the URL to the resource which needs to be updated with
    • a confirmation code as retrieved after the plain redirect authentication process with the ASPSP authentication server or
    • an access token as retrieved by submitting an authorization code after the integrated OAuth based authentication process with the ASPSP authentication server.
  • 'startAuthorisationWithPsuIdentification': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU identification data.
  • 'startAuthorisationWithPsuAuthentication': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while uploading the PSU authentication data.
    • 'startAuthorisationWithEncryptedPsuAuthentication': Same as startAuthorisactionWithPsuAuthentication where the authentication data need to be encrypted on application layer in uploading.
  • 'startAuthorisationWithAuthenticationMethodSelection': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while selecting the authentication method. This link is contained under exactly the same conditions as the data element "scaMethods".
  • 'startAuthorisationWithTransactionAuthorisation': The link to the authorisation end-point, where the authorisation sub-resource has to be generated while authorising the transaction e.g. by uploading an OTP received by SMS.
  • 'self': The link to the payment initiation resource created by this request. This link can be used to retrieve the resource data.
  • 'status': The link to retrieve the transaction status of the payment initiation.
  • 'scaStatus': The link to retrieve the scaStatus of the corresponding authorisation sub-resource. This link is only contained, if an authorisation sub-resource has been already created.

    scaRedirect

    object

    Link to a resource.

    href stringnullable

    href Entry.

    scaOAuth

    object

    Link to a resource.

    href stringnullable

    href Entry.

    confirmation

    object

    Link to a resource.

    href stringnullable

    href Entry.

    startAuthorisation

    object

    Link to a resource.

    href stringnullable

    href Entry.

    startAuthorisationWithPsuIdentification

    object

    Link to a resource.

    href stringnullable

    href Entry.

    startAuthorisationWithPsuAuthentication

    object

    Link to a resource.

    href stringnullable

    href Entry.

    startAuthorisationWithAuthenticationMethodSelection

    object

    Link to a resource.

    href stringnullable

    href Entry.

    startAuthorisationWithTransactionAuthorisation

    object

    Link to a resource.

    href stringnullable

    href Entry.

    self

    object

    Link to a resource.

    href stringnullable

    href Entry.

    scaStatus

    object

    Link to a resource.

    href stringnullable

    href Entry.

    status

    object

    Link to a resource.

    href stringnullable

    href Entry.