Skip to main content
GET

Card By Link Guide

Send secure card capture links via email or SMS
Use this endpoint to check the current status and configuration of a Card By Link request. The response includes the request parameters, delivery status, and the card token URI if the cardholder has already submitted their card details.

Error Responses

Error detail

Each condition below gives the exact moreInfo text, why it happens and how to resolve it. The full set is on the Error Handling page.
HTTP status: 404message: Uri not foundmoreInfo:
Reason. No card request exists for the requestID given. Card requests are not permanent: once completed or expired, a request is no longer retrievable.How to resolve.
  1. Check the requestID is the one returned when the request was created.
  2. Check the request has not already been completed by the cardholder, or passed its expiry.
  3. Confirm the credential belongs to the account that created the request.
HTTP status: 401message: You are not authorized to access this resource. Please contact customer support.moreInfo:
Reason. The SenderID in the body does not match the account the API key authenticates as. The API will not let one account send a card request on behalf of another.How to resolve.
  1. Set SenderID to the user ID of the account whose API key you are using.
  2. If you operate several accounts, check you have not paired one account’s key with another account’s SenderID.

Parameters

Headers

string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. See the Authentication guide.

Path Parameters

string
required
The request ID returned from sending a card capture link or CVV capture link.

Response

200 Returns the full request configuration and its current status.
string
The current status of the request. Possible values:
string
The unique identifier for this request.
string
The type of request: Card for card capture, CVV for CVV-only capture.
string
The PCI Booking token URL for the stored card. Only populated when Status is CardStored.
string
Timestamp of the last status change (ISO 8601 format).
string
The original token URL. Only present for CVV-only requests (RequestType: CVV).
For CVV-only requests, PCI Booking creates a new token that is a full copy of the original card details plus the captured CVV (returned in CardUri). The original token (OriginCardUri) is not modified and does not contain the CVV. You should delete the original token if it is no longer needed, otherwise it will continue to incur monthly storage fees.
Once Status is CardStored, remember to set the CVV Retention Policy on the token.