HalAuthenticationRequest
Data forwarded by the ASPSP top the PISP after creation of the Payment Request resource creation 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".
Fields (3)
- appliedAuthenticationApproachAuthenticationApproach
Authentication approaches that can be applied.
Schema: AuthenticationApproach
Code REDIRECTDECOUPLEDEMBEDDED-1-FACTORNONE - nonceNonce
Challenge to be sent in order to avoid replay of the authentication process.
Schema: Nonce
Challenge to be sent in order to avoid replay of the authentication process.
Type: string
Constraints: maxLength: 70
- _linksPaymentRequestResourceCreationLinks
links that can be used for further navigation, especially in REDIRECT approach
Schema: PaymentRequestResourceCreationLinks
links that can be used for further navigation, especially in REDIRECT approach
Link Description consentApproval URL to be used by the PISP in order to start the ASPSP authentication and consent management process - consentApprovalGenericLink
hypertext reference
Schema: GenericLink
hypertext reference
- hrefstringrequired
URI to be used. HREF stands for Hypertext REFerence.
Constraints: maxLength: 2000
- templatedboolean
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570.
This field must be set with "true" when [href] is an URI template, i.e. with parameters that will be set by the client afterwards. Parameter fields must be included by the API server according to RFC6570. Otherwise, this property must be absent or set to false default value: false