Skip to main content
POST

Network Tokenization Guide

Create and manage network tokens for stored cards
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

Authentication

API key only. This endpoint does not accept access tokens or session tokens.
string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. The x-pcibooking-api-key header is also accepted. See the Authentication guide.

Query String

string
required
The full URI of the existing PCI Booking token to network-tokenize (e.g. https://service.pcibooking.net/api/payments/paycard/555fd7b49f134b42a5dbe4d576b2e527).
boolean
default:"false"
When true, the original PCI Booking token is deleted after successful network tokenization.
string
The region where the new PCI Booking token is stored. One of: US, IN, AU, JP, CA, IE, GB, BR. If omitted, your account’s default region is used, or Ireland if your account has no default. See Card Storage Regions.

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).
string
default:"en"
ISO 639-1 language code (exactly 2 characters).
object
Cardholder details required by the card network. See Network Tokenize a Card for the full field reference.
integer
default:"5"
Device trust score (1-5).
integer
default:"5"
Account trust score (1-5).
number
Device latitude (-90 to 90).
number
Device longitude (-180 to 180).
string
Device IP address.
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.