Network Tokenization
Network Tokenization enables merchants to create and manage network tokens for card-on-file transactions. Network tokens replace the actual card PAN with a token issued by the card network (Visa, Mastercard), improving authorization rates and security.
All Network Tokenization endpoints use V2 API conventions and require Basic Auth authentication.
Network Tokenization must be enabled for your merchant account. Contact your onboarding manager to configure a tokenization provider.
Setup Requirements
To get started, contact your onboarding manager. As part of the setup, you will need to provide a Network Token Postback URL — a dedicated endpoint for receiving network token lifecycle updates (e.g., token status changes, card-on-file updates). This is separate from transaction postback URLs — transaction postback URLs can change per request, while the network token postback URL must be a stable, persistent endpoint.
Hosted Payment Page Integration
When Network Tokenization is enabled, all card payments on the hosted payment page follow this flow:
- Card data is tokenized during checkout.
- The network token is used for processing instead of the raw card number.
- The first transaction postback includes the
network_token_idused for the payment. - The merchant can save this ID and use it to retrieve token information or manage the token going forward.
Testing
To test the end-to-end Network Tokenization flow:
- Ensure Network Tokenization has been enabled for your account (see Setup Requirements).
- Process a card payment through the hosted payment page.
- Observe the
network_token_idin the transaction postback. - Use the management API endpoints to query or manage the token.