Skip to Contact an Expert Skip to Main Content
cardpointe logo
Developer Docs
Statuspage
Search Icon
Support
hamburger-menu
    Developer Docs
    Statuspage
  • Support
  1. CardPointe
  2. Marketplace & Add-ons
  3. Network Token Service from Fiserv
  • Marketplace & Add-ons
  • Card Account Updater
  • InstantAccept
  • Network Token Service from Fiserv
    • Overview
    • Benefits
    • Getting Started
    • How it Works
    • FAQs
    • On This Page

      Overview
    • On This Page

      Benefits
    • On This Page

      Getting Started
    • On This Page

      How it Works
    • On This Page

      FAQs

Overview

The Network Token Service from Fiserv offers enhanced security and reduces fraud while maintaining a seamless payment experience for you and your customers.

 

Network tokens act as substitutes for cardholders' sensitive primary account numbers (PANs) in card-on-file transactions. They automatically update to ensure that credentials remain current, even if there are changes to the underlying card data.

 

The Network Token Service from Fiserv provides a single integration point to all four major card networks (Visa®, Mastercard®, American Express®, and Discover®), you to implement network tokens without any change to the way you accept payments.

CardPointe currently supports network tokens for Visa and Mastercard accounts.

Support for Discover and Amex is coming soon.

Benefits

Merchants enrolled in the Network Token Service from Fiserv  take advantage of the folliowing benefits:

  • Enhanced security and fraud protection
  • Higher approval rates and revenue growth
  • Better payment and checkout experience
  • Potential cost savings in interchange fees

Additionally, the Network Token Service provides your customers the following benefits:

  • Peace of mind that card details are secure
  • Reduced friction and frustration at checkout
  • Automatic updates when a card is expired or replaced

Getting Started

To enroll in the Network Token Service from Fiserv, contact your account representative to get started.

How it Works

The Network Token Service generates merchant-specific account tokens for use in card-on-file (COF) payments. This increases security by authenticating the payment with single-use cryptograms and merchant-specific data, instead of using the account's PAN. 

 

Network Tokens are automatically maintained by the card networks and dynamically updated in real time to ensure credentials are always up to date.

 

When you accept a payment, The CardPointe Gateway securely transmits the transaction data to the Network Token Service from Fiserv to obtain the network token prior to sending the authorization request to the card networks. 

 

The following diagram illustrates the CardPointe transaction lifecycle using the Network Token Service from Fiserv:



Frequently Asked Questions

CardSecure tokens are generated by CardSecure, CardPointe's P2PE-validated encryption and tokenization solution. CardSecure tokens can only be used by the CardPointe Gateway. CardSecure tokens can optionally be enrolled in the Card Account Updater service in order to detect and apply account updates from the card networks.

 

Network Tokens are issued directly by the card networks, not the payment service provider. They are acquirer and payment gateway agnostic, and are automatically kept up-to-date by the card networks.

There is no change to the way CardSecure tokens are created or function.  Network Tokens provide an additional layer of security and convenience. Network Tokens are stored in the token vault, and when a card is used in a subsequent payment, the Network Token is retrieved and used to complete the payment.

There are several benefits to combining both the Network Token Service from Fiserv and the Card Account Updater (CAU) service for CardPointe merchants. 


For example, Network Tokens can help prevent declines, while CAU can help to potentially recover declines on certain transaction types, like PIN debit. 

Generally, Network Token transactions display like any other credit card transactions in CardPointe; however, when the service returns updated account details (for example, a new account number) then the transaction reporting will include two transaction records for the same payment.

 

In this case, the original transaction is displayed with a status of “Batched.” The updated transaction displays as a “T” (third-party) transaction, including the updated account details and a status of “Processed.” Both records share the same Authcode, so you can use that value to pair the original and updated records.

 

Note that the payment is only processed once; the cardholder is only charged once and you are only funded once. The appearance of a duplicate transaction record in CardPointe is strictly to display the updated account information used in the final, processed payment.

Site Selector