Credit Card Validations
91701 Cannot provide both a billing address and a billing address ID.
When you create or update a credit card you can set the billing address using full billing address details, or you can set it to a billing address ID of an address already associated to the customer, but not both.
91702 Billing address ID is invalid.
If setting the billing address on a credit card using an ID, the ID must be an ID of an address associated to the customer.
91704 Customer ID is required.
When adding a credit card to an existing customer, the customer ID is required.
91705 Customer ID is invalid.
When specifying the customer ID to add a credit card to an existing customer, the ID must be the ID a customer stored in the vault.
91708 Cannot provide expiration_date if you are also providing expiration_month and expiration_year.
You can provide the credit card expiration date as a single field, or as month and year separately, but not all 3.
91718 Token is invalid.
If you’re specifying the credit card token, you can use letters, numbers, -, and _.
91719 Credit card token is taken.
Credit card tokens have to be unique.
91720 Credit card token is too long.
Must be less than or equal to 36 characters.
91721 Token is not an allowed token.
We reseve a few tokens: “new” and “all.”
91722 Payment method token is required.
When updating a credit card you can omit the token if you don’t want to change it, but you can’t set it to an empty string. If set to an empty string on creation, the gateway will generate a random token.
81723 Cardholder name is too long.
Must be less than or equal to 255 characters.
81703 Credit card type is not accepted by this merchant account.
Applies when specifying a credit card when creating a transaction, but not when only storing in the vault since vault records are not associated to specific merchant accounts.
81718 Credit card number cannot be updated to an unsupported card type when it is associated to subscriptions.
Only applies when using recurring billing. If a credit card is being used for recurring billing subscriptions, the card can only be updated to a card type that is accepted by the merchant account that is being used for the subscriptions.
81706 CVV is required.
CVV will only be required if CVV processing rules are configured to require it. If the rules are configured to require it, then CVV is required when storing a card in the vault and performing card verification or when creating transactions.
81707 CVV must be 3 or 4 digits.
This error message is self-explanatory, but since all other validation errors have a description we wanted to put something here for consistency.
81709 Expiration date is required.
Expiration date can be provided as a single field or as month or year separate, but it’s required one of the two ways.
81710 Expiration date is invalid.
Valid formats are M/YY, M/YYYY, MM/YY, and MM/YYYY. The month must be 1-12 or 01-12.
81711 Expiration date year is invalid.
It must be between 1976 and 2200.
81712 Expiration month is invalid.
It must be 1-12 or 01-12.
81713 Expiration year is invalid.
It must be between 1976 and 2200.
81714 Credit card number is required.
You’ll get this error if number is omitted or if it is an empty string.
81715 Credit card number is invalid.
The credit card number must pass a Luhn-10 check.
81716 Credit card number must be 12-19 digits.
Inclusive.
81717 Credit card number is not an accepted test number.
Only test numbers can be used in the sandbox.
91723 Update Existing Token is invalid.
Applies when updating a customer and credit card at the same time and specifying the token of the credit card to update. You’ll get this error if the token specified is for a credit card that does not exist, or references a credit card that does not belong to the customer that is being updated.