Skip to main content

Carrying Over Network Tokens

Updated

Table of Contents

Overview

Typically, existing network tokens from outside sources/platforms cannot be used in the place of a PAN on the NMI Gateway, requiring old Credential-on-File chains to be restarted with customers. However, we support an undocumented Payment API field, initial_network_transaction_id, which takes in the network transaction ID itself. The format for this field is the raw trace/scheme ID. This field can be used with the scheme ID received from the platform you are migrating from. You can migrate recurring customers in one of two ways:

  1. Always use this undocumented field for the old transactions, and send initial_transaction_id for any new recurring transactions sent to our system, as documented.
  2. Just use this undocumented field for a migration where you run a single transaction with that initial_network_transaction_id, then use the NMI transaction ID you get back from that as your initial_transaction_id for future subsequent transactions.

This feature is currently supported on the processing platforms TSYS and FDMS Nashville, and we can enable this feature on an NMI merchant or partner account basis. If supported, this will allow you to continue existing Credential-on-File chains on NMI without needing to restart the chain with the cardholder.

Enabling the Feature

If you are interested in using this feature, please reach out to integration support at integration@nmi.com with the details of the platform you are migrating from, and confirming that you have access to the Visa/MC/Discover/etc. IDs from that platform. You must also confirm which processor was in use and the processor you are looking to use on NMI, as this will determine whether this feature is supported.