Customer Experience Enablers Technical FAQs

Yes, you can apply a temporary block on a physical card without impacting the token statuses if you have enabled the DPAN over FPAN status configuration option in the tokenisation configuration setup for your programme. For details, see DPAN over FPAN Status in the Tokenisation Guide.

This depends on the use case. If you want separate card controls or usage groups for physical versus mobile wallet usage, then an option might be to create two card records. as follows:

• Physical card — for use in stores, with its own card controls.

• Virtual card — which can be tokenised on a mobile device and have its own usage groups.

For more information, see the Virtual Cards Guide.

No, you cannot transition mobile wallet tokens (DPANs) to a new physical card (FPAN). The DPAN must be set up by the cardholder using a token activation request, which results in a new DPAN being created that is linked to the FPAN. See the Tokenisation Guide: Token Provisioning.

Usually, a new Token Activation Request (ProcessCode = 330000) creates a new Payment Token with a new payment_token_id. However, if a Token Activation Request message arrives with the same digitisation_ref (Correlation ID) and creator (MC-MDES/VISA-T), and there is already a token in the table that is marked as deleted txn_status = D, then instead of creating a new token, the system reuses the existing payment_token_id and updates that record. This behaviour supports how Mastercard or Visa reuse digitisation references for deleted tokens.

Therefore, if you see multiple Token Activation Requests tied to the same payment_token_id, it is likely falling under that scenario.