The request will retrieve the card data request to check on its status.
Below the reference you will find the possible status codes and their explanations.
We recommend that you first review the guide for this method.
|Email / SMS||Message queued||MessageQueued||Message was added to the PCI Booking queue.|
|SMS||Message sent||MessageSent||The message was sent to the recipient.|
|SMS||Message failed||MessageFailed||Message delivery to the recipient failed.|
|SMS||Message delivered||MessageDelivered||Message was successfully delivered to the recipient.|
|Email / SMS||Form viewed||FormViewed||Recipient viewed the capture form.|
|Email / SMS||Card stored||CardStored||The recipient has entered the card in the form and the credit card stored at PCI Booking.|
The status response will include a
|Email / SMS||Link expired||LinkExpired||The link to the capture form has expired.|
|Email / SMS||Store Failed||StoreFailed||Capture form submission failed.|
Card Security Code Requests
As a result of this form submission, the card details of the original token will be duplicated to a new token and the CVV data captured in this form will be added to the new token.
It is your responsibility to clear the original token that was stored in PCI Booking. If this token is not cleared, it will be charged the monthly storage fee.
CVV Retention Policy
Once the status of the card request is
CardStored, remember to set the CVV Retention Policy for this token.