Skip to main content
The card capture and CVV capture forms redirect the cardholder to your pages after submission. You provide a success URL and a failure URL. PCI Booking redirects to the appropriate page based on the outcome. These parameters are accepted on Request Card Entry Form, Send Card Capture Link, Request CVV Entry Form, and Send CVV Capture Link.

​
Success Page

Your success URL receives non-sensitive card capture data as query string parameters. Build your URL with placeholders for the parameters you need, and PCI Booking replaces them with actual values on redirect. Which placeholders are resolved depends on the form you used. The card entry forms resolve the full set below. The CVV capture forms resolve {cardToken} only - see CVV Capture Forms.

​
Card Entry Forms

Applies to Request Card Entry Form and Send Card Capture Link.

​
Example

Include only the parameters you need. At minimum, include {cardToken} to receive the token for subsequent API calls. These forms resolve either every placeholder you included or none of them.

​
CVV Capture Forms

Applies to Request CVV Entry Form and Send CVV Capture Link. These forms work on a card that is already stored. The operation copies the existing token to a new token and attaches the captured CVV to it. No card entry takes place, so the card data placeholders are not available.
Any other placeholder in a CVV capture success URL is passed through unchanged. A URL built with cardType={cardType}&cardNumber={cardNumber} redirects to your page with that literal text rather than with values, and no error is raised.

​
Example

Keep only {cardToken} in a CVV capture success URL. To get the card details for the new token, call Retrieve Token Metadata after the redirect. If you need card details in the redirect itself, use a card entry form instead.
Submit all URLs in encoded format. URLs must use HTTPS - an HTTP success/failure/postMessageHost URL causes mixed-content issues in the cardholder’s browser since the form itself is served over HTTPS.
If your success/failure URL resolves to a private/local network address from the cardholder’s browser, Chrome’s Private Network Access policy can block the redirect entirely. See Chrome Private Network Access for the fix (switch to the postMessage-based result flow).

​
Failure Page

The failure URL is a static URL. You do not need to add placeholders. PCI Booking automatically appends query parameters with the failure details.

​
Parameters Appended by PCI Booking

​
Example: What You Configure

​
Example: What the Redirect Looks Like

After a failed card capture:
After a failed charge-on-capture (with UPG gateway details):

​
Next Steps

Hosted Card Entry Form

Card capture form that uses these redirect URLs

CVV Capture

CVV-only capture form that uses the same redirect mechanism