An issuer may update a banking profile to enable new features (for example, remote payment or transit).
Once the new profile is deployed in the Production Environment, Thales can trigger a re-personalization campaign for all active tokens.
Thales does not retain token data elements generated by the TSP.
Because of that, Thales calls the TSP to recover the existing elements and rebuild the full profile.
The TSP must recover the existing data associated with the token.
The TSP must not generate new data.
After receiving a successful notification from Thales, the TSP must set ATC to 0.
0
This keeps ATC synchronized between the device and the TSP.
Last updated 4 months ago
Was this helpful?
