Set up success / failure redirection pages
Both the Card Capture and Card Security Code Capture forms require the use of success and failure pages for redirection. These redirects will occur after the card owner has entered the card details to the form and submitted it.
If the form was submitted successfully, the card owner will be redirected to the success page.
If the form was submitted and there was a problem, the card owner will be redirected to the failure page.
URL encoding
Please make sure to submit all URLs in encoded format.
Setting Up the Success Page
The base URL of the success page can be in your web environment. With the redirect to the success page, PCI Booking will relay some information regarding the capture (only non-secure information). These will relayed as query string parameters in the URL - you will then need to extract these parameters from the URL for further processing.
The parameters passed along in the URL are:
Parameter Name | Description | Required |
---|---|---|
{cardToken} | The returned card token | Yes |
{cardType} | The card type | No |
{cardNumber} | Masked card number - first 6 digits and last 4 digits | No |
{expiration} | Credit card expiration date | No |
{cardHolderName} | Credit card holder name | No |
{cvv} | Masked CVV - if present. | No |
{threeDSecIndication} | 3DS authentication status | No |
An example of a success URL:
https://mySite.com/success?cardToken={cardToken}&cardType={cardType}&cardNumber={cardNumber}&expiration={expiration}&cardHolderName={cardHolderName}&cvv={cvv}&threeDSecIndication={threeDSecIndication}
Setting Up the Failure Page
The failure page is a static page on your web environment which does not process any parameters from PCI Booking.
This should be a simple URL to a page on your system.
An example of a failure URL:
https://mySite.com/failure
PCI Booking will append the failure URL with the failure reason.
Updated almost 2 years ago