Introduction

Network tokens are surrogate values that replace Primary Account Number (PAN) stored electronically throughout the payments system. Network Tokens can be used to conduct payment transactions securely and can provide improved protection against fraud, because network tokens can require cryptogram validation or be limited to use in a specific domain or circumstance, such as token requestor, device or channel.
The purpose of this article is to describe the process how to generate and use the network tokens in the Gateway.

Initial Setup and Conditions

In order to utilise network tokens, it is necessary to change your account setup respectively. Please contact your boarding team or customer support team to manage the setup for you.

In case you are located in India, due to compliance requirements you need to obtain and capture customer’s consent and perform Strong Customer Authentication (SCA) before customer’s credit card is tokenized. You can authenticate your customer by using a 3-D Secure request followed by successful authorization which thereby provides you with the permission to request a network token. Please note, that you should not store card number at your end and generate the token instead.

Payments API Integration

RESTful Payment API solution specifics can be found here: REST API Network Tokenisation

Hosted Payment Page Integration

Hosted Payment Pages solution specifics can be found here: HPP Network Tokenisation

SOAP API Integration

SOAP API specifics can be found here: SOAP API Network Tokenisation