ofOpen Finance Guide
GlossarySTETBlogContact
ISO20022object

SupplementaryData

ISO20022: Additional information that cannot be captured in the structured elements and/or any other specific block.

API: This structure is used to embed the relevant URLs for returning the status report to the PISP and to specify which authentication approaches are accepted by the PISP and which was chosen by the ASPSP

Fields (6)

  • acceptedAuthenticationApproachAuthenticationApproaches

    Can only be set by the PISP.

    Can only be set by the PISP. Authentication approaches that are supported by the PISP. The PISP can provide several choices separated by commas. Case of none of the accepted approaches is supported by the ASPSP, the latest will respond with HTTP400 (Bad request) and specify wich approaches are actually supported.

    Schema: AuthenticationApproach

    Code
    REDIRECT
    DECOUPLED
    EMBEDDED-1-FACTOR
    NONE
  • appliedAuthenticationApproachAppliedAuthenticationApproach

    The ASPSP, based on the authentication approaches proposed by the PISP, choose the one that it can processed, in respect with the preferences and constraints of the PSU and indicates in this field which approach was chosen.

    Schema: AppliedAuthenticationApproach

    The ASPSP, based on the authentication approaches proposed by the PISP, choose the one that it can processed, in respect with the preferences and constraints of the PSU and indicates in this field which approach was chosen. It may happen that the ASPSP considers that, in case of payment cancellation request, there is no need for authentication and will then return "NONE".

    Type: object

  • appliedAuthenticationstringenum · 3

    Can only be set by the ASPSP.

    Can only be set by the ASPSP. This field allows the ASPSP to inform the PISP about the way authentication was processed during the payment request confirmation.

    Code
    noAuthentication
    oneFactorAuthentication
    strongAuthentication
  • scaHintstringenum · 2

    can only be set by the PISP

    can only be set by the PISP Hint given by the merchant and/or the PISP about an SCA exemption context

    Code
    noScaExemption
    scaExemption
  • successfulReportUrlstring

    URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach

    URL to be used by the ASPSP in order to notify the PISP of the finalisation of the authentication and consent process in REDIRECT and DECOUPLED approach

  • unsuccessfulReportUrlstring

    URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach

    URL to be used by the ASPSP in order to notify the PISP of the failure of the authentication and consent process in REDIRECT and DECOUPLED approach If this URL is not provided by the PISP, the ASPSP will use the "successfulReportUrl" even in case of failure of the Payment Request processing