Query & Update
Duplicate Token
Create a copy of an existing token, optionally adding a CVV and specifying property association and creator reference.
POST
Update Card Data Guide
Modify expiration dates and creator references on tokens
Duplicate Token method has been completed successfully, a new card token will be created and the token URI will be returned in the response header Location.
The result of this process would be that there are two card tokens in PCI Booking for the same card.
It is your responsibility to delete one of them to avoid getting charged for storage on both tokens.
Error Responses
Parameter Constraints
This endpoint is rate limited.
Parameters
Headers
Your API key prefixed with
APIKEY. Example: APIKEY your-api-key. For server-to-server calls.Alternative: Browser-Side Authentication
Alternative: Browser-Side Authentication
This endpoint also accepts token-based authentication via query parameters:
If multiple methods are provided, precedence: Session Token > Access Token > API Key.
Query String
The card URI (resource identifier for the card location within PCI Booking). For example,
https://service.pcibooking.net/api/payments/paycard/865ed8bec1f84366b97112a69cdbf915. The card URI should be URL encoded.Security code, as returned from the iFrame or other sources. If not provided, the new token will not contain any CVV.
A reference value that can be used to query for this card token.
The Property’s Username (user ID) found within PCI Booking (under “Property settings”) which has been given permission to view the card. The owner (Booker) always has permission to view the card.
Response
200 - Card duplicated. ALocation header is returned with the new token URI.
Remember to set the CVV Retention Policy on the new token if it includes a CVV.

