Network Tokenisation

Introduction 

Network Tokenisation enhances payment security and efficiency by replacing sensitive card details with a secure digital token. Managed by card networks like Visa, Mastercard, and Cartes Bancaires, these tokens process transactions without exposing actual card numbers. By replacing card details with secure digital tokens, Network Tokenisation reduces fraud risk, lowers costs, and improves authorisation rates, especially for Credential on File (COF) transactions. Seamlessly integrating with existing payment systems, it enhances security while ensuring a smooth customer experience. 

How It Works 

1. Token Generation: When a customer makes a purchase and decides to save it for a future usage (one click payment, subscriptions, etc.), their card details are sent to the card network’s token service, which creates a unique token. 
2. Token Usage: The token replaces the card number in transactions and can be reused for future payments, making checkout seamless. 
3. Security: Each customer initiated transaction includes a one-time cryptogram, adding an extra layer of protection. If a token is compromised, it can be replaced without affecting the customer’s actual card or others tokens created for others usage. 

Token Benefits   

• Stronger Security: reduces fraud risks by replacing card details with a token. 
• Automatic Card Updates: ensures smooth recurring payments without customer intervention. 
• Lower Transaction Costs: reduces acquiring costs for COF transactions. 
• Higher Authorization Rates: increases approval rates by using secure, trusted tokens. 
• Seamless Integration: no changes needed for merchants to benefit from network tokenisation. 

Requirements

Before integrating Network Tokenisation, ensure: 

• You comply with Strong Customer Authentication (SCA) where required. 
• Your acquirer supports Network tokenisation  
• Network tokenisation is activated in your account, please contact your account manager or support for that. 

Implementation 

Integrating Network Tokenisation is seamless and requires no changes on your side. Our platform automatically generates and manages network tokens for Credential on File (COF) transactions for security and efficiency. 

We detailled here some additional information we send back in the transactions if you wish to get more information when the transaction i processed with a Network toke. 

1. Token Creation Process
   A scheme token is automatically requested when a new COF series is created during the first Cardholder-Initiated Transaction (CIT). For detailed steps on creating a new COF series, refer to the guide "How to create a new COF series?" process runs asynchronously to prevent transaction delays.
2. Network Token Status
   After a transaction, the response will include the "networkTokenData" object, indicating the token’s status: 

• requested – a Network Token has been requested from the scheme.
• denied – a Network Token request has been denied from the scheme. 
• active – the linked Network Token is active and can be used for the subsequent payment in the payment series. 
• suspended – the linked Network Token is suspended and cannot be used for the subsequent payment in the payment series. Instead, PAN details would be used for the subsequent payment in the payment series. 
• deleted – the linked Network Token is deleted and cannot be used for the subsequent payment in the payment series. Instead, PAN details would be used for the subsequent payment in the payment series. 

CreatePayment response 

"networkTokenData": { 
 "networkTokenState": "requested", 
 "networkTokenUsed": false 
 }, 

Network Tokenisation offers a secure, cost-effective, and seamless solution for processing COF transactions. It requires no changes on the merchant’s side, automatically generating and managing tokens to improve payment security and performance. 

Token usage

If a Network token is linked to a COF series the Network token will automatically be used. Either iusing create paym,ent and the Alias or Using Subsequent Payment.

When you have requested a subsequent payment using create payment if the transaction had been processed with a network Token, you will receive an object "networkTokenData" in the feedback of the transaction.  

"networkTokenData": { 
  "bin": "489537", 
  "countryCode": "99", 
  "networkToken": "************6486", 
  "networkTokenState": "active", 
  "networkTokenUsed": true, 
  "tokenExpiryDate": "1225" 
}

This object will be provided in addition of the "card" object, allowing you to display the "real card" used for the payment as known by the customer.

"card": { 
       "bin": "48749706", 
       "cardNumber": "************2022", 
       "countryCode": "BE", 
       "expiryDate": "0725" 
}, 

When an Alias had been created for the COF series, you are also able to recover the information from the Network token linked to the alias with get Token:  
 
Example of get token response irth a Netork token linked to the token:  

"card": { 
 "alias": "518868XXXXXX6435", 
  "data": { 
   "cardWithoutCvv": { 
    "cardholderName": "Pierre Riat", 
    "cardNumber": "518868XXXXXX6435", 
    "expiryDate": "0129" 
   } 
  } 
 }, 
"id": "5512bd0dd8e445a4bfa9d266a8ad6615", 
"isTemporary": false, 
"networkTokenLinked": { 
   "expiryDate": "0328", 
   "maskedToken": "535412XXXXXX1566", 
   "tokenState": "active" 
 }, 
 "paymentProductId": 3 
}