The response of calling this method is the HTML content of the Card Capture Form itself (Click here for an example of the content). You can use the request URL either as the page URL that a customer is directed to or as the source URL of an iframe element on your page.
3D Secure challenge timeout
Please note that if you enable 3DS processing during card capture, the 3DS challenge window will have a 5 minute timeout period. If the card owner does not submit the response to the 3DS challenge within that timeframe, their authentication will be rejected.
Access Token Vs. Session Token
Between the two options of using the Access Token or the Session Token, we would recommend using the Access Token.
Multiple Authentication Methods allowed
This method accepts multiple forms of authentication methods (Session Token and Access Token). If more than one authentication method is provided, the Session Token will take precedence.
All URLs should be https.
Please note to urlEncode all components!
CVV Retention Policy
Remember to set the CVV Retention Policy for this token.
Custom Merchant Information
Please do not use the
merchantNameparameter in the request unless you have followed our guide on managing merchant information for 3D Secure authentication as this may cause problems in your 3DS processing.
If you plan to use the PCI Booking merchant information for 3DS Authentication, please set "ThreeDs" as
Trueand "merchantName" blank.
Please note that the PCI Booking merchant can only be used to perform 3D Secure authentication on Visa and Mastercard cards.