If you see the message "Failed to Tokenize Card" while trying to add a payment method, it means our secure encryption system was unable to create a "Security Token" with your bank.
Common Reasons for This Error
Data Mismatch: If the cardholder information does not match exactly what is on file with your card issuer, the request may be rejected. This can happen due to simple input errors (like a typo in the name), an outdated billing address, or automated fraud checks by your bank.
Security Protocol Issues: While strict security protocols are required to protect your data, sometimes overly restrictive or misconfigured security settings on the bank's side can block a legitimate tokenization request.
Invalid Card Information: Tokenization will automatically fail if the card being used is expired, cancelled, has been reported lost, or is otherwise deemed invalid by the credit card network.
How to Resolve This Issue
To successfully add your card and clear this error, please follow these steps:
Verify Your Billing Details: Ensure the name, street address, and postal code match exactly what is printed on your latest bank statement.
Check Card Status: Confirm with your bank that the card is active and authorized for international or online transactions.
Clear Your Browser Cache: Sometimes old session data can interfere with the security "handshake." Clear your cache or try using an Incognito/Private browser window.
Try a Different Payment Method: If the issue persists with one card, it may be due to a specific security block from that bank. Attempting to add a different card can often bypass local bank restrictions.
Still having trouble?
If you have verified your details and the error continues, we recommend contacting your bank's security or fraud department. They can confirm if they are seeing an "Authorization Request" from Rebel.com and why their system might be preventing the secure token from being created.
Comments
0 comments
Please sign in to leave a comment.