The request will trigger a message to be sent to the recipient (via email or text message) with a link to the card capture form.
We recommend that you first review the guide for this method.
When submitted successfully, the response body will be blank and there will be a header added:
Location: The URI for the card request which can be referenced later to retrieve status or cancel.
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.
Since the URLs provided in this request are provided in the body of the message instead of in the request URL's query string, the URLs mentioned above should not be urlEncoded.
Requests specific parameters vs account parameters
The following parameters -
CustomerSupportPhone- can be provided either as specific values for each individual request, or their value can be retrieved from your account settings (as set in our portal).
If specific values are provided in the request, they will override the values from the account and the specific values will be displayed in the card capture form.
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.