Symptoms
When users click the Tokenize button on a Payment Profile, the system returns an "Invalid card" error in the Tokenization Message field, even if the credit card is known to be valid.
Cause
This error occurs when attempting to manually re-tokenize a payment profile that has already been successfully tokenized.
For security compliance, once a payment profile is tokenized, the system automatically deletes the original credit card number and stores only the Token Key. If a user clicks the Tokenize button again, the system attempts to send the request to the payment gateway without a credit card number. Because the card data is missing, the gateway rejects the request with an "Invalid card" error.
How to Verify a Profile is Tokenized
You do not need to see a "Tokenization Successful" message to confirm a profile has a token. A payment profile is successfully tokenized and stored if:
The Credit Card Number field is empty.
The Expiration Month and Expiration Year are populated.
The Token Key field contains a value.
Frequently Asked Questions
Why is the Tokenization Message field blank on some valid profiles?
The Tokenization Message field only populates when a user manually clicks the Tokenize button.
If a Payment Profile is created automatically during a transaction (for example, if a customer checks a "Save for future payments" box on a payment page), this field will intentionally remain blank. A blank Tokenization Message does not indicate a failure.