What activates network tokenization?
Selecting a supported tokenization partner in the contract configuration. From that point, the linkage between the network token and the existing NORBr Vault token happens at infrastructure level, in real time, for every eligible transaction under that contract. Existing payment data stays where it is, and the API contract stays as it was.
In detail
Selecting a supported tokenization partner in the contract configuration. From that point, network tokenization runs for every eligible transaction under that contract.
What happens at infrastructure level
The linkage between the network token and the existing NORBr Vault token happens at infrastructure level, in real time. Your merchants do not migrate card data, and their integration does not change: existing payment data stays where it is, and the API contract stays as it was.
During authorization, the platform checks whether a usable network token exists for the payment method. When the selected provider supports network tokens, the transaction carries the token and its cryptogram. When it does not, the platform falls back to the PAN and the transaction continues.
Before going live
A network tokenization contract has its own activation test. Depending on provider support, the scenarios include a token request, a token status check, a lifecycle event and a cryptogram request, so the configuration is validated before it touches live traffic.
Following the effect
Each transaction records which path it took. Dedicated indicators in the dashboards, such as network token usage rate and success rate on tokenized flows, let your merchants measure the effect on their own traffic. Recurring payments also benefit, because network tokens are updated by the scheme when a card is reissued.