All Validation Errors

Address

These validations apply when creating or updating addresses in the Vault directly, and also when providing billing and shipping details in requests like Braintree::Transaction.sale() or Braintree::PaymentMethod.create().

Code Text Explanation
81801Addresses must have at least one field filled in.

At least one of the address attributes must be present, but it doesn't matter which one. This doesn't apply when creating transactions—billing and shipping address can be blank unless AVS processing rules are configured to require billing street and postal.

81802Company is too long.

Maximum 255 characters.

81804Extended address is too long.

Maximum 255 characters.

81805First name is too long.

Maximum 255 characters.

81806Last name is too long.

Maximum 255 characters.

81807Locality is too long.

Maximum 255 characters.

81813Postal code can only contain letters, numbers, spaces, and hyphens.

There are also length limitations, but that's a different validation error.

81808Postal code is required.

Applies when AVS rules are configured to require postal code.

81809Postal code may contain no more than 9 letter or number characters.

The length only applies to letters or numbers; it ignores spaces, hyphens, and all other special characters.

81810Region is too long.

Maximum 255 characters.

81811Street address is required.

Applies when creating a transaction or performing card verification when AVS rules are configured to require street address.

81812Street address is too long.

Maximum 255 characters.

81827US state codes must be two characters to meet PayPal Seller Protection requirements.

US state codes must be two characters to meet PayPal Seller Protection requirements.

91803Country name is not an accepted country.

We only accept specific country names.

91815Provided country information is inconsistent.

You can only specify one of country name, country code alpha2, country code alpha3 and country code numeric.

91816Country code (alpha3) is not an accepted country.

We only accept specific alpha-3 values.

91817Country code (numeric) is not an accepted country.

We only accept specific numeric values.

91814Country code (alpha2) is not an accepted country.

We only accept specific alpha-2 values

91818Customer has already reached the maximum of 50 addresses.

You will get this validation error when trying to add an address to a customer which has already reached the maximum of 50 addresses.

91819First name must be a string.

First name must be a string.

91820Last name must be a string.

Last name must be a string.

91821Company must be a string.

Company must be a string.

91822Street address must be a string.

Street address must be a string.

91823Extended address must be a string.

Extended address must be a string.

91824Locality must be a string.

Locality must be a string.

91825Region must be a string.

Region must be a string.

91826Postal code must be a string.

Postal code must be a string.

91828Address is invalid.

Address must provided in a valid format.

Customer

Code Text Explanation
91602Custom field is invalid:

Custom field keys must match the API name of a custom field configured in the Control Panel. The error message for this validation error will contain a list of the invalid keys

91609Customer ID has already been taken.

Customer IDs have to be unique

91610Customer ID is invalid (use only letters, numbers, '-', and '_').

Valid characters are letters, numbers, dashes, and underscores.

91611Customer ID is not an allowed ID.

We reserve a few words that can't be used as IDs. 'all' and 'new' currently cannot be used

91612Customer ID is too long.

Maximum 36 characters

91613Customer ID is required.

Customer ID is required when performing updates

91617Nonce references a vaulted payment instrument - cannot be transferred between customers

Nonce references a vaulted payment instrument - cannot be transferred between customers

81601Company is too long.

Maximum 255 characters

81603Custom field is too long:

Custom field values must be less than or equal to 255 characters. The error message for this validation error will contain a list of the custom fields that were too long

81604Email is an invalid format.

Email must be a well-formed email address. If you are migrating from a system that does not have this constraint and want to record the email address in the Vault, you can use custom_fields

81605Email is too long.

Maximum 255 characters

81606Email is required if sending a receipt.

This only applies when creating a transaction. If you specify that you want to send a receipt then the customer email will be required

81607Fax is too long.

Maximum 255 characters

81608First name is too long.

Maximum 255 characters

81613Last name is too long.

Maximum 255 characters

81614Phone is too long.

maximum 255 characters

81615Website is too long.

maximum 255 characters

81616Website is an invalid format.

Website must be well-formed. The http:// at the beginning is optional. If you want to provide websites that may be not well-formed you can use custom_fields

Marketplace

Merchant Account

Code Text Explanation
82602Applicant merchant id is too long.

The merchant account id cannot be longer than 32 characters.

82603Applicant merchant id format is invalid.

You can only use letters, numbers, _ and - for the merchant account id.

82604Applicant merchant id is in use.

Merchant account ids need to be unique

82605Applicant merchant id is not allowed.

Merchant account ids may not be named 'all' or 'new'

82606Master merchant account ID is required.

You must provide a master merchant account id when creating a merchant account

82607Master merchant account ID is invalid.

You'll get this error if we cannot find a master merchant account with the id specified

82608Master merchant account must be active.

You'll get this error if the supplied master merchant account id is not active

82610Terms Of Service needs to be accepted. Applicant tos_accepted required.

You must indicate that the terms of service are accepted

82675Merchant account id can not be updated.

You'll get this error if the ID cannot be updated

82676Master merchant account id can not be updated.

You'll get this error if the merchant account ID cannot be updated

82674Merchant accounts with a status of pending or suspended cannot be updated.

The merchant account cannot be updated.

82609Applicant first name is required.

You must provide the first name of the applicant

82637Individual first name is required.

Applicant first name is required.

82611Applicant last name is required.

You must provide the last name of the applicant.

82638Individual last name is required.

Applicant last name is required.

82612Applicant date of birth is required.

You must provide the applicant's date of birth.

82639Individual date of birth is required.

Individual date of birth is required.

82613Applicant routing number is required.

You must provide the applicant's bank routing number

82640Funding routing number is required.

Funding routing number is required.

82614Applicant account number is required.

You must provide the applicant's bank account number

82641Funding account number is required.

Funding account number is required.

82615Applicant SSN must be blank, last 4 digits, or full 9 digits.

The applicant's social security number must be valid (full 9 digits, with or without dashes, or last 4 digits)

82642Individual SSN must be blank, last 4 digits, or full 9 digits.

Individual SSN must be blank, last 4 digits, or full 9 digits.

82616Applicant email is invalid.

The applicant's email must be valid

82643Individual email is invalid.

Individual email is invalid.

82627Applicant first name is invalid.

The applicant's first name must not contain '/', '\', '&', '<', '>' or any control characters

82644Individual first name is invalid.

Individual first name is invalid.

82628Applicant last name is invalid.

The applicant's last name must not contain '/', '\', '&', '<', '>' or any control characters

82645Individual last name is invalid.

Applicant last name is invalid.

82631Applicant company name is invalid.

The applicant's company name must contain only letters, numbers, and these characters: &-!@#$()'./+,". The maximum length is 40 characters.

82632Applicant tax ID is invalid.

The applicant's tax id must be 9 digits long

82688Business params provided in an invalid format.

You must provide the attributes for Business in the correct format.

82647Business tax ID is invalid.

Business tax ID is invalid.

82633Applicant company name is required with tax ID.

If the applicant's tax id is provided then the company name must be provided as well

82634Applicant tax ID is required with company name.

If the applicant's company name is provided then the tax id must be provided as well

82635Applicant routing number is invalid.

The applicant's bank routing number must be valid

82649Funding routing number is invalid.

Funding routing number is invalid.

82650An unexpected error occurred trying to save the merchant account; support has been notified and is looking into the issue. You may safely retry this request

An unexpected error occurred trying to save the merchant account; support has been notified and is looking into the issue. You may safely retry this request.

82621Applicant declined due to OFAC.

The applicant has failed an OFAC check. The OFAC search confirms whether a sub-merchant is on the criminal and terrorists watch lists collected from databases around the world

82622Applicant declined due to MasterCard MATCH.

The applicant has failed a Mastercard MATCH check. The Mastercard MATCH File is a database file used by payment processing banks to identify specific merchants and principals who may been terminated for reasons like fraud or violation(s) of Visa and/or Mastercard rules

82623Applicant declined due to failed KYC.

The applicant has failed a Know Your Customer check

82624Applicant declined due to invalid SSN.

The applicant's social security number is invalid. If you provide a social security number, you must provide either the entire number or the last four digits

82625Applicant declined due to SSN matching that of a deceased person.

The applicant has been declined because the social security number provided appears in a database of social security numbers belonging to deceased persons

82626Applicant declined after review.

After review, the applicant has been declined.

82617Applicant street address is required.

You must provide the applicant's street address

82657Individual street address is required.

Individual street address is required.

82618Applicant locality is required.

You must provide the applicant's city, town, or municipality

82658Individual locality is required.

Individual locality is required.

82619Applicant postal code is required.

You must provide the applicant's postal code

82659Individual postal code is required.

Individual postal code is required.

82620Applicant region is required.

You must provide the applicant's region

82660Individual region is required.

Individual region is required.

82629Applicant street address is invalid.

You must provide a valid street address for the applicant that includes at least one digit

82661Individual street address is invalid.

Individual street address is invalid.

82664Applicant region is invalid.

You must provide a valid region for the applicant. Only two-letter abbreviations are accepted, e.g. 'CA' but not 'California'

82668Individual region is invalid.

Individual region is invalid.

82630Applicant postal code is invalid.

You must provide a valid postal code for the applicant

82662Individual postal code is invalid.

Individual postal code is invalid.

82636Applicant phone is invalid.

The provided phone is not valid

82656Individual phone is invalid.

Individual phone is invalid.

82663Applicant date of birth is invalid

You must provide a valid date of birth

82666Individual date of birth is invalid.

Individual date of birth is invalid.

82670Applicant account number is invalid.

The provided bank account number is not valid

82671Funding account number is invalid.

Funding account number is invalid.

82665Applicant email is required.

You must provide an email address

82667Individual email is required.

Individual email is required.

82672Business tax ID must be blank unless business legal name is present.

The tax id must be blank if no company name/legal name is provided

82673Applicant tax ID must be blank unless company name present.

Applicant tax ID must be blank unless company name present.

82646Business DBA name is invalid.

The provided DBA name is not valid. The applicant's company name must contain only letters, numbers, and these characters: &-!@#$()'./+,". The maximum length is 40 characters.

82677Business legal name is invalid.

The provided legal name is not valid. The applicant's company name must contain only letters, numbers, letters, numbers, and these characters: &-!@#$()'./+,". The maximum length is 40 characters.

82669Business legal name is required with tax ID.

You must provide a legal name if a tax id has been provided

82648Business tax ID is required with business legal name.

You must provide a tax id if a legal name has been provided

82685Business street address is invalid.

The provided business street address is not valid. It must contain at least one digit

82686Business postal code is invalid.

The provided business zip code is not valid. It must be 5 digits followed by an optional hyphen, space, and an additional 4 digits

82684Business region is invalid.

The provided business region is not valid. Only two-letter abbreviations are accepted, e.g. 'CA' but not 'California'

82679Funding destination is invalid.

You must provide a valid funding destination

82678Funding destination is required.

You must provide a funding destination

82681Funding email is invalid.

The provided funding email address is not valid

82680Funding email is required when destination is email.

You must provide a funding email address when your funding destination is email.

82683Funding mobile phone is invalid.

The provided funding mobile phone is not valid

82682Funding mobile phone is required when destination is mobile phone.

You must provide a funding mobile phone when your funding destination is mobile phone.

82687Individual params provided in an invalid format.

You must provide the attributes for Individual in the correct format.

Payment method

Code Text Explanation
93101Payment method params are required.

A top level payment method parameter is missing.

93102Nonce is invalid.

The nonce that was received is not a valid nonce.

93103Nonce is required.

A nonce was not provided.

93104Customer ID is required.

A customer id was not provided.

93105Customer ID is invalid.

The customer id does not reference a customer.

93106Cannot forward a payment method of this type.

Only credit cards may be forwarded.

93107Cannot use a payment_method_nonce more than once.

A payment method nonce may only be consumed once.

93108Unknown payment_method_nonce.

The payment method nonce was not found.

93109Nonce is not vaultable.

Nonce is not vaultable.

Apple Pay

Code Text Explanation
83501Apple Pay cards are not accepted by this merchant account.

Apple Pay cards are not accepted by this merchant account.

83502A customer ID is required to vault an Apple Pay Card.

When storing an Apple Pay card in the vault, you must provide the customer ID of a customer already stored in the vault to whom the card will belong.

93503Apple Pay token is taken.

Payment method tokens must be unique across all payment method types.

93504Cannot use a payment_method_nonce more than once.

The payment method nonce has already been used.

93505Unknown payment_method_nonce.

The payment method nonce could not be found.

93506Payment method nonce locked.

Deprecated
The payment method nonce must be unlocked before it is used.

83518Credit card type is not accepted by this merchant account.

The specified merchant account is not configured to accept cards from this payment network. Please specify the correct payment networks when initializing a PKPaymentRequest.

93507Payment method nonces cannot be used to update an existing Apple Pay Card.

A vaulted payment method cannot be updated with an Apple Pay nonce. Create a new payment method instead.

93508Number is required for Apple Pay Card

The Apple Pay PKPaymentToken payment data was malformed (did not contain a card number).

93509Expiration Month is required for Apple Pay Card

The Apple Pay PKPaymentToken payment data was malformed (did not contain an expiration month).

93510Expiration Year is required for Apple Pay Card

The Apple Pay PKPaymentToken payment data was malformed (did not contain an expiration year).

93511Cryptogram is required for Apple Pay Card

The Apple Pay PKPaymentToken payment data was malformed (did not contain a cryptogram). This is sometimes caused by misconfigured merchantCapabilities in the PKPaymentRequest. See our recommendations in the Apple Pay guide.

83512Apple Pay payment data decryption failed

The Apple Pay PKPaymentToken payment data could not be decrypted. This occurs when (a) the Apple Pay merchant id used in your iOS App entitlements does not match the values provided to Braintree; (b) the provisioning profile you used to sign your iOS App does not correspond to the iOS Developer Account with which the Apple Pay certificate was generated; (c) the payment data was not valid as it was received by the Gateway. Call Braintree Support if you cannot resolve this error.

93513Apple Pay is disabled for this merchant

Your merchant account is not configured for Apple Pay support. Please contact Braintree Support to configure and enable Apple Pay.

93514Apple Pay certificate, private key or merchant ID not configured

Your merchant account is not configured for Apple Pay support. Please contact Braintree Support to configure and enable Apple Pay.

93517Certificate provided is not valid

Certificate provided is not valid

93519Public key used to sign payment data does not match stored certificate

Public key used to sign payment data does not match stored certificate

83520Payment data is malformed

Payment data is malformed

93521Private key stored does not match private key used to encrypt payment data

Private key stored does not match private key used to encrypt payment data

93522Certificate does not match stored key pair

The Apple Pay certificate you uploaded does not match the key pair we have stored for your account. Please download a new CSR from the control panel and create a new certificate for your Apple Pay merchant ID using this CSR.

Credit card

Code Text Explanation
91701Cannot 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.

91702Billing 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.

91704Customer ID is required.

When adding a credit card to an existing customer, the customer ID is required.

91705Customer 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.

91708Cannot provide expirationdate 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.

91718Token is invalid (use only letters, numbers, '-', and '').

If you're specifying the credit card token, you can use letters, numbers, '-', and '_'.

91719Credit card token is taken.

Credit card tokens have to be unique.

91720Credit card token is too long.

Maximum 36 characters.

91721Token is not an allowed token.

We reserve a few tokens: 'new' and 'all'.

91722Payment 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.

91744Billing address format is invalid.

Billing address format is invalid.

81723Cardholder name is too long.

Maximum 175 characters.

81703Credit card type is not accepted by this merchant account.

Applies when specifying a credit card in a sale or verification request. Not applicable when only storing in the Vault, since Vault records are not associated to specific merchant accounts.

81718Credit 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.

81706CVV 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.

81707CVV must be 4 digits for American Express and 3 digits for other card types.

CVV must be 4 digits for American Express and 3 digits for other card types.

81709Expiration 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.

81710Expiration date is invalid.

Valid formats are M/YY, M/YYYY, MM/YY, and MM/YYYY. The month must be 1-12 or 01-12.

81711Expiration date year is invalid. It must be between 1975 and 2200.

It must be between 1975 and 2200.

81712Expiration month is invalid.

It must be 1-12 or 01-12.

81713Expiration year is invalid.

It must be between 1976 and 2200.

81714Credit card number is required.

You'll get this error if number is omitted or if it is an empty string.

81715Credit card number is invalid.

The credit card number must pass a Luhn-10 check.

81716Credit card number must be 12-19 digits.

Inclusive.

81717Credit card number is not an accepted test number.

Only test numbers can be used in the sandbox.

91723Update 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.

81724Duplicate card exists in the vault.

Duplicate card exists in the vault.

81725Credit card must include number, payment_method_nonce, or venmo_sdk_payment_method_code.

Credit card must include number, payment_method_nonce, or venmo_sdk_payment_method_code.

91726Credit card type is not accepted by this merchant account.

Credit card type is not accepted by this merchant account.

91727Invalid VenmoSDK payment method code

Invalid VenmoSDK payment method code.

91728Verification Merchant Account ID is invalid.

There must be a merchant account with this ID.

91729Update Existing Token is not allowed when creating a customer.

Update Existing Token is not allowed when creating a customer.

91730Verifications are not supported on this merchant account

This Merchant Account does not support Credit Card Verification.

91731Cannot use a payment_method_nonce more than once.

The payment method nonce has already been used once.

91732Unknown payment_method_nonce.

The payment method nonce could not be found.

91733Payment method nonce locked.

Deprecated
The payment method nonce must be unlocked before it is used.

91734Credit 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.

91735Payment method nonces cannot be used to update an existing card.

A payment method nonce) cannot be used to update an existing credit card.

91738Payment method is not a credit card payment method.

This operation requires a credit card, and the payment method you specified is not a credit card.

91742Verification Merchant Account is suspended.

Verification Merchant Account is suspended.

91743The current user does not have access to the specified verification_merchant_account_id

The current user does not have access to the specified verification_merchant_account_id

81736CVV verification failed.

CVV was incorrect or not supplied.

81737Postal code verification failed.

Postal code was incorrect or not supplied.

91739Verification amount cannot be negative.

The amount you specified for verification was less than zero.

91740Verification amount is invalid.

The amount you specified for verification had an invalid format.

91741Verification amount not supported by processor.

The processor you are using for verification does not allow the verification amount you specified.

91745Payment method params supplied are not valid for updating a credit card.

The payment method params you supplied are not valid for updating a credit card.

81750Credit card number is prohibited.

Cannot transact with an issuer on OFAC's prohibited list.

American Express industry data

Code Text Explanation
93401Industry type is invalid.

Industry type is invalid.

93402Lodging data is empty.

Lodging data is empty.

93403Folio number is invalid.

Folio number is invalid.

93404Check in date is invalid.

Check in date is invalid.

93405Check out date is invalid.

Check out date is invalid.

93406Check out date must occur during or after the check in date.

Check out date must occur during or after the check in date.

93407Data fields are unknown.

Data fields are unknown.

93408Travel and Cruise data is empty.

Travel and Cruise data is empty.

93409Data fields are unknown.

Data fields are unknown.

93410Travel Package is invalid.

Travel Package is invalid.

93411Departure date is invalid.

Departure date is invalid.

93412Lodging check in date is invalid.

Lodging check in date is invalid.

93413Lodging check out date is invalid.

Lodging check out date is invalid.

PayPal

Code Text Explanation
82901Incomplete PayPal account information.

You must specify an access token or a consent code for this operation.

82902Pre-Approved Payment enabled PayPal account required for vaulting.

When you vault a PayPal account, you must provide a payment method nonce that was retrieved via the transaction flow.

82903Invalid PayPal account information.

You cannot specify both an access token and a consent code for this operation.

82904PayPal Accounts are not accepted by this merchant account.

Your account has not been enabled to accept PayPal.

82905A customer ID is required to vault a PayPal Account.

When adding a PayPal account to an existing customer, the customer ID is required.

92906PayPal Account token is taken.

PayPal account tokens have to be unique.

92907Cannot use a payment_method_nonce more than once.

A payment method nonce may only be consumed once.

92908Unknown payment_method_nonce.

The payment method nonce was not found.

92909Payment method nonce locked.

Deprecated
The payment method nonce) must be unlocked before it is used.

92910Error communicating with PayPal.

There was an error communicating with PayPal.

92911PayPal authentication expired.

Deprecated
The authentication you received from your user has expired.

92912Funding source selection was given without an access token.

You cannot specify a funding source without also specifying an access token.

92913Funding source object is invalid or missing required fields.

You sent an invalid or incomplete funding source specification.

92914Payment method nonces cannot be used to update an existing PayPal account.

A payment method nonce) cannot be used to update an existing PayPal account.

92915Payment method params supplied are not valid for updating a PayPal account.

The payment method params you supplied are not valid for updating a PayPal account.

Recurring billing

Add-ons/Discounts

Code Text Explanation
92001Quantity is invalid.

Quantity must be a number.

92002Amount is invalid.

Amount must be formatted like '10' or '10.00'.

92003Amount cannot be blank.

Blanks are not allowed.

92004Quantity cannot be blank.

Blanks are not allowed.

92005Number of billing cycles is invalid.

Number of billing cycles must be numeric.

92010Quantity must be greater than zero.

Quantity must be greater than 0.

92011Existing ID is invalid.

Modification ID must be associated with the subscription.

92012Existing ID is required.

Modification ID is required to update a modification.

92013Inherited From ID is invalid.

Modification with that inherited from ID is not available.

92014Inherited From ID is required.

Must provide an inherited from ID.

92015Cannot update a removed add-on or discount.

Cannot update and remove a modification at the same time.

92016Cannot remove add-on or discount if not already associated with subscription.

Cannot remove add-on or discount if not already associated with subscription.

92017Number of billing cycles cannot be blank.

Number Of Billing Cycles cannot be blank if the subscription expires.

92018Cannot specify both number of billing cycles and never expires as true.

Number of billing cycles is blank and never expires is not set to true.

92019Number of billing cycles must be greater than zero.

Number of billing cycles must be greater than 0.

92020Existing ID is not of the correct kind.

Existing ID must be of the type of modification that is being edited.

92021ID to remove is incorrect kind.

Existing ID must be of the type of modification that is being removed.

92022Cannot edit add-on or discount on a past due subscription.

Unable to edit modifications on subscriptions that are past due.

92023Amount is too large.

The amount cannot be greater than the maximum allowed by the processor. Contact our Support team for your specific limit.

92024Cannot pass null modification.

Modification is missing from the API call.

92025ID to remove is invalid.

ID to remove is invalid.

Subscription

Code Text Explanation
81901Cannot edit a canceled subscription.

After a subscription has been canceled it cannot be updated.

81902ID has already been taken.

Subscription IDs need to be unique.

81903Price cannot be blank.

If you provide a price, it can't be an empty string. If you omit the price, then the subscription will inherit the price from the plan.

81904Price is an invalid format.

Price must be formatted like '10' or '10.00'.

81905Subscription has already been canceled.

You can't cancel subscriptions that have already been canceled.

81906ID is invalid (use only letters, numbers, '-', and '').

If specifying the ID for the subscription, you can only use letters, numbers, and -.

81907Trial Duration is an invalid format.

It must be 1-3 digits.

81908Trial Duration is required.

It's required if trial period is set to true.

81909Trial Duration Unit is invalid.

Valid values are "day" and "month".

81910Cannot edit an expired subscription.

You cannot edit a subscription with Expired status.

81923Price is too large.

The subscription price cannot be greater than the maximum allowed by the processor. Contact our Support team for your specific limit.

91901Merchant Account ID is invalid.

If specifying the merchant account to use to process transactions for this subscription it needs to be the ID for one of your merchant accounts.

91902Payment method token payment instrument type is not accepted by this merchant account.

When providing a payment method token, your merchant account must be configured to accept the payment method type represented by the token.

91903Payment method token is invalid.

You'll get this error if we can't find a payment method with the token specified.

91904Plan ID is invalid.

You'll get this error if we can't find a plan with the given ID.

91905Payment method token does not belong to the subscription's customer.

When updating a subscription and changing the payment method token, you can only use tokens associated to the same customer that the subscription is currently associated to.

91906Number Of Billing Cycles must be numeric.

It must be a number.

91907Number Of Billing Cycles must be greater than zero.

It must be greater than 0.

91908Cannot specify both number of billing cycles and never expires as true.

You cannot specify both number of billing cycles and never expires as true.

91909Number Of Billing Cycles is less than the current billing cycle.

You cannot edit a subscription and change the number of billing cycles to be below the current count of billing cycles.

91911Cannot add duplicate add-on or discount.

Add-Ons and Discounts must be unique, but you can change the quantity.

91912Number Of Billing Cycles cannot be blank if the subscription expires.

Blanks are not allowed.

91913Billing Day of Month must be numeric.

It must be a number.

91914Billing Day of Month must be between 1 and 28, or 31.

Billing day of month must be 1-28 or 31 (for the last day of every month).

91915First Billing Date is invalid.

The first billing date is an incorrect format.

91916First Billing Date cannot be in the past.

The first billing date cannot be in the past.

91917Cannot specify more than one type of start date.

You can only specify one of trial period, start immediately, billing day of month, and first billing date.

91918Billing Day of Month cannot be updated.

Billing day of month cannot be updated.

91919First Billing Date cannot be updated.

First billing date cannot be updated.

91920Can only edit id, merchant account id, payment method token, and descriptor on a past due subscription.

You cannot edit any fields which could change the price on a past due subscription.

91921Invalid request format.

The add-ons and discounts are in an invalid format.

91922Cannot update subscription to a plan with a different billing frequency.

You will get this validation if you try to update the plan on a subscription and the billing cycle for the new plan is not the same as the billing cycle of the old plan.

91923Subscription Plan currency must be the same as the merchant account's currency.

Subscription Plan currency must be the same as the merchant account's currency.

91924Payment method nonce payment instrument type is not accepted by this merchant account.

The supplied payment method nonce represents a payment method of a type that is not accepted by this merchant account.

91925Payment method nonce is invalid.

The supplied payment method nonce was not in a valid format or is unknown.

91926Payment method nonce does not belong to the subscription's customer.

The payment method nonce used to create a subscription must be vaulted and must belong to the customer owning the subscription

91927Payment method nonce represents an un-vaulted payment instrument.

You cannot create a subscription with a nonce representing an unvaulted payment instrument. Use the payment method nonce to create a vaulted payment method first.

91928Payment instrument type is not valid for subscriptions.

Payment instrument type is not valid for subscriptions.

91929Payment instrument type is not valid for subscriptions.

Payment instrument type is not valid for subscriptions.

91930Merchant Account does not support the given payment instrument type.

Merchant Account does not support the given payment instrument type.

Search

Code Text Explanation
82301Settlement Date is required

You must provide a settlement date as the first argument.

82302Settlement Date is invalid

The settlement date provided must be a valid date.

82303Group By Custom Field is not a valid custom field

The custom field provided must be valid.

Transaction

Code Text Explanation
81501Amount cannot be negative.

Even if creating a credit transaction, the amount should be given as x.xx, not -x.xx.

81502Amount is required.

You'll get this error if amount is not given or is blank.

81503Amount is an invalid format.

Amount must be formatted like '10' or '10.00'. If the currency does not use decimal places, the amount cannot include decimal places.

81528Amount is too large.

The amount cannot be greater than the maximum allowed by the processor. Contact our Support team for your specific limit.

81509Credit card type is not accepted by this merchant account.

The credit card card type must be accepted by your merchant account. Note that there is a different error code when you get this error when creating transactions using tokens (91517).

81527Custom field is too long:

Custom field values must be less than 255 characters. The error message for this validation error will contain a list of the custom fields that were too long.

91501Order ID is too long.

Order ID must be less than 255 characters.

91530Cannot provide a billing address unless also providing a credit card.

If you're creating a transaction using a credit card token, then we will use the billing address associated to that token in the Vault. You'll get this error if creating a transaction using a token and specifying a billing address

91504Transaction can only be voided if status is authorized or submitted_for_settlement.

Unless the transaction status is authorized or submitted_for_settlement, it cannot be voided.

91505Credit transactions cannot be refunded.

Only sale transactions can be refunded.

91506Cannot refund a transaction unless it is settled.

Transaction status must be settled to refund it.

91507Cannot submit for settlement unless status is authorized.

Transaction status must be authorized to submit the transaction for settlement.

91508Cannot determine payment method.

You must specify the payment method to charge, either directly (by payment_method_nonce, payment_method_token, credit_card, paypal_account, etc.) or indirectly (by customer_id, subscription_id, etc.)

91526Custom field is invalid:

Custom field keys must match the API name of a custom field configured in the control panel. The error message for this validation error will contain a list of the invalid keys.

91510Customer ID is invalid.

You'll get this error if you create a transaction using a customer ID and the customer ID isn't in your Vault.

91511Customer does not have any credit cards.

When creating a transaction using a customer ID, we'll use the customer's default credit card. If the customer does not have any credit cards associated to it, you'll get this error.

91512Transaction has already been completely refunded.

Transactions can only be refunded once.

91513Merchant account ID is invalid.

If you specify the merchant account ID to use to process a transaction and it does not match any of your merchant accounts, you'll get this error.

91514Merchant account is suspended.

You'll get this error if you try to create a transaction using a suspended merchant account.

91515Cannot provide both payment_method_token and credit_card attributes.

If you specify both a Vault token and a full credit card number you'll get this error.

91516Cannot provide both payment_method_token and customer_id unless the payment_method belongs to the customer.

If you specify both a customer ID and a payment method token when creating a transaction, the payment_method_token must belong to the customer ID.

91527Cannot provide both payment_method_token and subscription_id unless the payment_method belongs to the subscription.

If you specify both a payment method token and a subscription ID the subscription ID must be associated to the token given.

91517Payment instrument type is not accepted by this merchant account.

When providing a payment method token, your merchant account must be configured to accept the payment method type represented by the token.

91518Payment method token is invalid.

You'll get this error if the payment method token isn't in the Vault.

91519Processor authorization code cannot be set unless for a voice authorization.

You can only set the processor authorization code for voice authorization transactions.

91521Refund amount is too large.

You cannot refund more than the amount submitted for settlement.

91538Cannot refund a transaction with a suspended merchant account.

You cannot refund a transaction associated with a suspended merchant account.

91522Settlement amount is too large.

You cannot settle more than the authorized amount unless your industry and processor support settlement adjustment (settling a certain percentage over the authorized amount); contact our Accounts team for details.

91529Cannot provide both subscription_id and customer_id unless the subscription belongs to the customer.

If you give both a customer ID and a subscription ID the subscription must be associated to the customer.

91528Subscription ID is invalid.

You'll get this error if the subscription ID given isn't one of your subscriptions.

91523Transaction type is invalid.

Valid transaction types are "sale" and "credit"

91524Transaction type is required.

We need to know if you want to create a sale or a credit.

91525Vault is disabled.

If you set the option to store in Vault, your Vault needs to be enabled.

91531Subscription status must be Past Due in order to retry.

A subscription must be in past due status in order to manually retry the charge.

91547Merchant account does not support refunds.

The merchant account account does not support refunds.

81531Amount must be greater than zero.

The amount of a transaction cannot be zero.

81534Tax amount cannot be negative.

The tax amount cannot be less than zero.

81535Tax amount is an invalid format.

Tax amount must be formatted like '10' or '10.00'. If the currency does not use decimal places, the amount cannot include decimal places.

81536Tax amount is too large.

The tax amount cannot be longer than 9 digits.

81571Failed to authenticate, please try a different form of payment.

Failed to authenticate, please try a different form of payment.

91537Purchase order number is too long.

The purchase order number cannot be larger than 12 characters for AIB and 17 characters for other all other processors.

91539Voice Authorization is not allowed for this card type

The specified card type does not support voice authorization codes.

91540Transaction cannot be cloned if payment method is stored in vault.

Instead, create a new transaction using the payment method's token

91541Cannot clone voice authorization transactions.

Cloning voice authorizations is currently unsupported.

91542Unsuccessful transaction cannot be cloned.

Only transactions that were authorized or settled are cloneable.

91543Credits cannot be cloned.

You may only clone sale transactions

91544Cannot clone transaction without submit_for_settlement flag.

You must specify whether or not to submit the cloned transaction for settlement upon creation.

91545Voice Authorizations are not supported for this processor.

Your processor does not support voice authorizations.

91546Credits are not supported by this processor.

Your processor does not support credits.

91548Purchase order number is invalid.

The purchase order number must be printable ASCII characters

81520Processor authorization code must be 6 characters.

Processor authorization code must be 6 characters.

91549Cannot provide more than one of payment_method_token, payment_method_nonce, credit_card, and venmo_sdk_payment_method_code attributes.

Cannot provide more than one of payment_method_token, payment_method_nonce, credit_card, and venmo_sdk_payment_method_code attributes.

91550Channel is too long.

Channel is too long. This field is for use by Partners and shopping cart providers only.

91551Settlement amount cannot be less than the service fee amount.

The settlement amount must be greater than or equal to the service fee amount.

91552Credits not allowed with service fee.

Service fees are allowed on sale transactions only.

91553Sub merchant account requires a service fee.

Transactions for sub merchant accounts need a service fee amount.

91554Amount cannot be negative.

Service fee amount must be greater than or equal to zero.

91555Amount is an invalid format.

Service fee amount must be formatted like '10' or '10.00'. If the currency does not use decimal places, the amount cannot include decimal places.

91556Service fee amount is larger than transaction amount.

Service fee amount must be less than the transaction amount.

91557Service fee not supported on master merchant account.

Transactions for a master merchant account cannot have a service fee amount.

91558Merchant account does not support MOTO transactions unless configured by processor.

This merchant account cannot be used for Mail Order/Telephone Order.

91559Cannot refund a transaction with a pending merchant account.

A Merchant Account must be Active in order to refund a transaction.

91560Transaction could not be held in escrow.

The Transaction cannot be held in escrow.

91561Cannot release a transaction that is not escrowed.

Cannot release a transaction that is not escrowed.

91562Release can only be cancelled if the transaction is submitted for release.

Release can only be canceled if the transaction is submitted for release.

91563Escrowed transactions cannot be partially refunded.

The Transaction must be fully refunded after being held in escrow.

91564Cannot use a payment_method_nonce more than once.

The payment method nonce has already been consumed.

91565Unknown payment_method_nonce.

The payment method nonce cannot be found among those generated for the merchant.

91567Payment instrument type is not accepted by this merchant account.

Payment instrument type is not accepted by this merchant account.

91568Three D Secure Token is invalid.

3D Secure token is invalid.

91569payment_method_nonce does not contain a valid payment instrument type.

payment_method_nonce does not contain a valid payment instrument type.

91572Current payment method does not support use_billing_for_shipping flag.

Current payment method does not support use_billing_for_shipping flag.

91575Cannot transition transaction to settled, settlement_confirmed, or settlement_declined

Cannot transition transaction to settled, settlement_confirmed, or settlement_declined

91576PayPal is not enabled for your merchant account.

PayPal is not enabled for your merchant account.

91577Merchant account does not support payment instrument.

Merchant account does not support payment instrument.

91570Transaction data does not match data from Three D Secure verify call.

The credit card number and expiration date used for 3D Secure verification must match the values used to create the transaction.

91573Transaction cannot be cloned if payment method is a PayPal account.

Transaction cannot be cloned if payment method is a PayPal account.

91574Cannot refund a transaction transaction in settling status on this merchant account. Try again after the transaction has settled.

Cannot refund a transaction transaction in settling status on this merchant account. Try again after the transaction has settled.

91578Service fee can not be applied on PayPal transactions.

Service fee can not be applied on PayPal transactions.

91580PayPal custom fields must be less than 256 characters in length.

PayPal custom fields must be less than 256 characters in length.

91581Shipping address customer does not match customer in request.

Shipping address customer does not match customer in request.

91582PayPal unilateral transactions must also be submitted for settlement.

A unilateral payment is a payment that is made to a receiver who does not have a PayPal account.

91583This PayPal account was not vaulted with the required data

This PayPal account was not vaulted with the required data

91584Merchant account must match the 3D Secure authorization merchant account.

The merchant account used for 3D Secure verification must match the merchant account used to create the transaction.

91585Amount must match the 3D Secure authorization amount.

The amount used for 3D Secure verification must match the amount used to create the transaction.

91586Shared billing address ID cannot be used in the same call as a standard billing address ID

Shared billing address ID cannot be used in the same call as a standard billing address ID

91587Shared customer ID cannot be used in the same call as a standard customer ID

Shared customer ID cannot be used in the same call as a standard customer ID

91588Shared payment method token cannot be used in the same call as a standard payment method token

Shared payment method token cannot be used in the same call as a standard payment method token

91589Shared payment method token cannot be used in the same call as a non-shared identifier param

Shared payment method token cannot be used in the same call as a non-shared identifier param

91590Shared identifier param cannot be used with non-shared payment method token

Shared identifier param cannot be used with non-shared payment method token

91591Shared shipping address ID cannot be used in the same call as a standard shipping address ID

Shared shipping address ID cannot be used in the same call as a standard shipping address ID

91592Shared payment methods cannot be vaulted

Shared payment methods cannot be vaulted

91593Shared payment methods cannot be vaulted

Shared payment methods cannot be vaulted

91594Shared shipping addresses cannot be vaulted

Shared shipping addresses cannot be vaulted

91595Shared payment methods cannot be updated

Shared payment methods cannot be updated

91597Cannot provide both shared_payment_method_token and shared_customer_id unless the payment_method belongs to the customer.

Cannot provide both shared_payment_method_token and shared_customer_id unless the payment_method belongs to the customer.

91598Payment instrument type is not accepted by this merchant account.

Payment instrument type is not accepted by this merchant account.

91599Shared Shipping address customer does not match customer in request.

Shared Shipping address customer does not match customer in request.

91596Shared payment method token is invalid.

Shared payment method token is invalid.

915100Shared Customer ID is invalid.

Shared Customer ID is invalid.

915103Cannot submit for partial settlement.

Cannot submit for partial settlement.

915101Payment instrument type is not accepted.

Payment instrument type is not accepted.

915102Partial settlements are not supported by this processor.

Partial settlements are not supported by this processor.

915104Delayed settlements are not supported for this processor. The submit for settlement option is required.

Delayed settlements are not supported for this processor. The submit for settlement option is required.

915105Merchant account does not support Amex rewards.

Merchant account does not support Amex rewards.

915106Points amount is too large.

Amex Pay with Points amount is too large.

915107Updating order_id on submit_for_settlement is not supported by this processor.

Updating order_id on submit_for_settlement is not supported by this processor.

915108Updating descriptor on submit_for_settlement is not supported by this processor.

Updating descriptor on submit_for_settlement is not supported by this processor.

915109PayPal supplementary data fields must be less than 4001 characters in length:

PayPal supplementary data fields must be less than 4001 characters in length:

915110Cannot clone facilitated transactions.

Cannot clone facilitated transactions.

915111PayPal supplementary data field count must be less than 101.

PayPal supplementary data field count must be less than 101.

915112Shared payment method token originated from another merchant and is not allowed to be shared

Shared payment method token originated from another merchant and is not allowed to be shared.

915113EciFlag is required.

ECI flag is required for 3D Secure Pass Thru transactions.

915114EciFlag is invalid.

The provided ECI flag is invalid. Valid ECI Flags are:

  • 00
  • 01
  • 02
  • 05
  • 06
  • 07

915115Xid is required.

XID is required for 3D Secure Pass Thru transactions.

915116Cavv is required for specified EciFlag.

CAVV is required when ECI Flag is 01, 02, 05 or 06.

Descriptor

Code Text Explanation
92201Company name/DBA section is invalid.

The descriptor name is made up of two parts, company/DBA name and product separated by an asterisk (*). Some examples of valid descriptor names are:

  • • cmp*productdescription
  • • company*product name
  • • company name*myurl.com

Company name/DBA section must be either 3, 7 or 12 characters and the product descriptor can be up to 18, 14, or 9 characters respectively (with an * in between for a total descriptor name of 22 characters). You can only use alphanumeric characters, spaces, and periods in your dynamic descriptors. URLs can use alphanumeric characters and periods.

This validation doesn't apply for Marketplace transactions.

92202Phone number is invalid.

Phone must be 10 - 14 characters and can only contain numbers, dashes, parentheses and periods. The phone number can be from 10 - 14 characters. Some example phone numbers are:

  • 3125556666
  • 312-555-6666
  • (312)555-6666

92203Dynamic descriptors have not been enabled for this account. Please contact support@braintreepayments.com.

Dynamic descriptors have not been enabled for this account. Please contact us.

92204Descriptor format is invalid.

Descriptor name must be less than or equal to 15 characters and can only contain letters and numbers. This will be prefixed by the preset company name for this account.

92205International phone number is invalid.

Deprecated
Phone can only contain numbers, dashes and periods and must be less than or equal to 13 characters.

92206URL must be 13 characters or shorter.

The url/web address to a customer's statement must be less than or equal to 13 characters.

Verification

Code Text Explanation
94201Verification amount cannot be negative.

Verification amount cannot be negative.

94202Verification amount is invalid.

Verification amount is invalid.

94203Verification amount not supported by processor.

Verification amount not supported by processor.

94204Verification Merchant Account ID is invalid.

Verification Merchant Account ID is invalid.

94205Verification Merchant Account is suspended.

Verification Merchant Account is suspended.

94206The current user does not have access to the specified merchant_account_id

The current user does not have access to the specified merchant_account_id

Still Have Questions?

If you can’t find an answer, give us a call at 877.434.2894 or email our Support team.