Payment Protocols > 3D Server To Server XML Protocol > 3D Secure authentication, Cardholder redirection

3D Secure authentication, Cardholder redirection

In the event of enrolled card, the Merchant must redirect the holder to the URL of the authentication page exposed by the Issuing Bank.

                                        construction example of the form                                    

                                    <form name="redirect" action="<%=acsUrl%>" method="POST">
 <input type=hidden name="PAReq" value="<%=pareq%>" />
 <input type=hidden name="TermUrl" value="<%=termURL%>" />
 <input type=hidden name="MD" value="<%=paymentId%>" />
</form>
                                

POST parameters

NAME

DESCRIPTION

FORMAT

PAReq	For ENROLLED result only: encrypted message to be sent to the authentication system of the card issuer (ACS)	AN
TermUrl	Return url to which the Bank's ACS will return the outcome	AN Max. length: 2083
MD	Id associated to the payment session (paymentID)	AN Max. length: 18

After completing authentication, the holder will be redirected to the TermUrl and receive two parameters: MD, authentication session identifier and PARes (Payer Authentication Response), authentication encrypted outcome.
The PARes will have to be forwarded to Nexi for validation, decoding, and extraction of the values required to submit the authorisation request in full/half secure mode.