Skip to main content
POST

Network Tokenization Guide

Create and manage network tokens for stored cards
Submits raw card details to the card network (Visa, Mastercard, or Amex) for network tokenization. On success, the resulting network token is stored as a PCI Booking token and the token URI is returned in the Location header.
Network tokenization replaces the real card number with a network-issued token that is bound to your merchant. The network token receives automatic card-on-file updates from the issuer, reducing declines from expired or replaced cards.

Error Responses

Parameter Constraints

  • Card.Number: Valid card number (Visa, Mastercard, or Amex).
  • Card.ExpirationMonth: Range 1-12.
  • Card.SecurityCode: 3-4 digits (regex ^\d{3,4}$).
  • TokenizationRequest.ConsumerLanguage: Exactly 2 characters, ISO 639-1 language code. Defaults to en.
  • TokenizationRequest.CardHolder.CountryCode: Exactly 2 uppercase letters (ISO 3166-1 alpha-2).
  • TokenizationRequest.DeviceScore: Range 1-5, defaults to 5.
  • TokenizationRequest.AccountScore: Range 1-5, defaults to 5.
  • TokenizationRequest.DeviceLocationLat: Range -90 to 90.
  • TokenizationRequest.DeviceLocationLon: Range -180 to 180.

Parameters

Headers

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

Query String

string
Token storage region. One of: US, IN, AU, JP, CA, IE, GB, BR. If omitted, uses the account default.

Request Body

object
required
The card details to network-tokenize.
object
required
Network tokenization parameters including cardholder and device information.

Response

201 - Network token created. The Location header contains the PCI Booking token URI for the network-tokenized card.