Skip to main content
POST
Network-tokenizes a card that is already stored as a PCI Booking token. The card data is retrieved from the existing token, submitted to the card network, and the resulting network token is stored as a new PCI Booking token. Optionally, the original token can be deleted after successful network tokenization by setting deleteExisting=true.

Error Responses

Parameters

Headers

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

Query String

cardUri
string
required
The full URI of the existing PCI Booking token to network-tokenize (e.g. https://service.pcibooking.net/api/payments/paycard/tok_abc123).
deleteExisting
boolean
default:"false"
When true, the original PCI Booking token is deleted after successful network tokenization.
loc
string
Token storage region for the new network token. One of: US, IN, AU, JP, CA, IE, GB, BR. If omitted, uses the account default.

Request Body

The request body contains the same TokenizationRequest fields as Network Tokenize a Card, excluding the Card object (since card data comes from the existing token).
ConsumerLanguage
string
default:"en"
ISO 639-1 language code (exactly 2 characters).
CardHolder
object
Cardholder details required by the card network. See Network Tokenize a Card for the full field reference.
DeviceScore
integer
default:"5"
Device trust score (1-5).
AccountScore
integer
default:"5"
Account trust score (1-5).
DeviceLocationLat
number
Device latitude (-90 to 90).
DeviceLocationLon
number
Device longitude (-180 to 180).
DeviceIpAddress
string
Device IP address.
CardSource
string
Source of the card data.

Response

201 - Network token created. The Location header contains the new PCI Booking token URI. If deleteExisting=true was set, the original token is deleted.