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
81801 Address must have at least one field fill 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
81802 Company is too long Maximum 255 characters
81804 Extended address is too long Maximum 255 characters
81805 First name is too long Maximum 255 characters
81806 Last name is too long Maximum 255 characters
81807 Locality is too long Maximum 255 characters
81813 Postal code can only contain letters, numbers, spaces, and hyphens There are also length limitations, but that's a different validation error
81808 Postal code is required Applies when AVS rules are configured to require postal code
81809 Postal 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
81810 Region is too long Maximum 255 characters
81811 Street address is required Applies when creating a transaction or performing card verification when AVS rules are configured to require street address
81812 Street address is too long Maximum 255 characters
91803 Country name is not an accepted country We only accept specific country names
91815 Inconsistent country You can only specify one of country name, country code alpha2, country code alpha3 and country code numeric
91816 Country code alpha-3 is not accepted We only accept specific alpha-3 values
91817 Country code numeric is not accepted We only accept specific numeric values
91814 Country code alpha-2 is not accepted We only accept specific alpha-2 values
91818 Too many addresses per customer You will get this validation error when trying to add an address to a customer which has already reached the maximum of 50 addresses
91819 First name is invalid First name must be a string
91820 Last name is invalid Last name must be a string
91821 Company is invalid Company must be a string
91822 Street address is invalid Street address must be a string
91823 Extended address is invalid Extended address must be a string
91824 Locality is invalid Locality must be a string
91825 Region is invalid Region must be a string
91826 Postal code is invalid Postal code must be a string of 5 or 9 digits, optionally separated by a dash or a space.

Customer

Code Text Explanation
91602 Custom 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
91609 Customer ID has already been taken. Customer IDs have to be unique
91610 Customer ID is invalid. Valid characters are letters, numbers, - and _.
91611 Customer 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
91612 Customer ID is too long. Maximum 36 characters
91613 Id is required Customer IDs are required when updating
81601 Company is too long. Maximum 255 characters
81603 Custom 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
81604 Email 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
81605 Email is too long. Maximum 255 characters
81606 Email 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
81607 Fax is too long. Maximum 255 characters
81608 First name is too long. Maximum 255 characters
81613 Last name is too long. Maximum 255 characters
81614 Phone is too long. Maximum 255 characters
81615 Website is too long. Maximum 255 characters
81616 Website 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 a custom_fields

Marketplace

Code Text Explanation
82602 Merchant account id is too long. The merchant account id cannot be longer than 32 characters
82603 Merchant account is is not valid. You can only use letters, numbers, _ and - for the merchant account id
82604 Merchant account id is in use. Merchant account ids need to be unique
82605 Merchant account id is not allowed. Merchant account ids may not be named 'all' or 'new'
82606 Master merchant account id is required. You must provide a master merchant account id when creating a merchant account
82607 Master merchant account id is invalid. You'll get this error if we cannot find a master merchant account with the id specified
82608 Master merchant account must be active. You'll get this error if the supplied master merchant account id is not active
82610 TOS accepted is required. You must indicate that the terms of service are accepted
82675 Id cannot be updated. You'll get this error if the ID cannot be updated
82676 Master merchant account id cannot be updated. You'll get this error if the merchant account ID cannot be updated
82674 Cannot be updated. The merchant account cannot be updated
82609 82637 First name is required. You must provide the first name of the applicant
82611 82638 Last name is required. You must provide the last name of the applicant
82612 82639 Date of birth is required. You must provide the applicant's date of birth
82613 82640 Routing number is required. You must provide the applicant's bank routing number
82614 82641 Account number is required. You must provide the applicant's bank account number
82615 82642 SSN is invalid. The applicant's social security number must be valid (full 9 digits, with or without dashes, or last 4 digits)
82616 82643 Email address is invalid. The applicant's email must be valid
82627 82644 First name is invalid. The applicant's first name must not contain '/', '\', '&', '<', '>' or any control characters
82628 82645 Last name is invalid. The applicant's last name must not contain '/', '\', '&', '<', '>' or any control characters
82631 Company name is invalid. The applicant's company name must contain only letters, numbers, ampersands (&) hyphens (-), exclamation marks (!), at symbols (@), hashtag (#), dollar sign ($), beginning and end parentheses ( '(' and ')' ), single quotation mark ('), period (.), forward slash (/), plus symbol (+), comma (,) and double quotation mark ("). The maximum length is 40 characters
82632 82647 Tax id is invalid. The applicant's tax id must be 9 digits long
82633 Company name is required with tax id. If the applicant's tax id is provided then the company name must be provided as well
82634 Tax id is required with company name. If the applicant's company name is provided then the tax id must be provided as well
82635 82649 Routing number is invalid. The applicant's bank routing number must be valid
82621 Declined 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
82622 Declined 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
82623 Declined failed KYC. The applicant has failed a Know Your Customer check
82624 Declined SSN invalid. 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
82625 Declined SSN matches deceased. The applicant has been declined because the social security number provided appears in a database of social security numbers belonging to deceased persons
82626 Declined. After review, the applicant has been declined
82617 82657 Street address is required. You must provide the applicant's street address
82618 82658 Locality is required. You must provide the applicant's city, town, or municipality
82619 82659 Postal code is required. You must provide the applican'ts postal code
82620 82660 Region is required. You must provide the applicant's region
82629 82661 Street address is invalid. You must provide a valid street address for the applicant that includes at least one digit
82664 82668 Region is invalid. You must provide a valid region for the applicant. Only two-letter abbreviations are accepted, e.g. 'CA' but not 'California'
82630 82662 Postal code is invalid. You must provide a valid postal code for the applicant
82636 82656 Phone is invalid. The provided phone is not valid
82663 82666 Date of birth is invalid. You must provide a valid date of birth
82670 82671 Account number is invalid. The provided bank account number is not valid
82665 82667 Email address is required. You must provide an e-mail address
82672 82673 Tax id must be blank. The tax id must be blank if no company name / legal name is provided
82646 Dba name is invalid. The provided DBA name is not valid. The applicant's company name must contain only letters, numbers, ampersands (&) hyphens (-), exclamation marks (!), at symbols (@), hashtag (#), dollar sign ($), beginning and end parentheses ( '(' and ')' ), single quotation mark ('), period (.), forward slash (/), plus symbol (+), comma (,) and double quotation mark ("). The maximum length is 40 characters
82677 Legal name is invalid. The provided legal name is not valid. The applicant's company name must contain only letters, numbers, ampersands (&) hyphens (-), exclamation marks (!), at symbols (@), hashtag (#), dollar sign ($), beginning and end parentheses ( '(' and ')' ), single quotation mark ('), period (.), forward slash (/), plus symbol (+), comma (,) and double quotation mark ("). The maximum length is 40 characters
82669 Legal name is required with tax id. You must provide a legal name if a tax id has been provided
82648 Tax id is required with legal name. You must provide a tax id if a legal name has been provided
82685 Business street address is invalid. The provided business street address is not valid. It must contain at least one digit
82686 Business 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
82684 Business region is invalid. The provided business region is not valid. Only two-letter abbreviations are accepted, e.g. 'CA' but not 'California'
82679 Funding destination is invalid. You must provide a valid funding destination
82678 Funding destination is required. You must provide a funding destination
82681 Funding email is invalid. The provided funding e-mail address is not valid
82680 Funding email is required. You must provide a funding e-mail address when your funding destination is email
82683 Funding mobile phone is invalid. The provided funding mobile phone is not valid
82682 Funding mobile phone is required. You must provide a funding mobile phone when your funding destination is mobile phone.

Payment method

Code Text Explanation
92906 Payment method token is in use. Payment method tokens must be unique across all payment method types.
92907 Payment method nonce consumed. The payment method nonce has already been used once.)
92908 Payment method nonce unknown. The payment method nonce could not be found.
92909 Payment method nonce locked. The payment method nonce must be unlocked before it is used.

Apple Pay

Code Text Explanation
83502 Customer ID is required for vaulting. 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.
93503 Token is already in use. Payment method tokens must be unique across all payment method types.
93504 Payment method nonce consumed. The payment method nonce has already been used.
93505 Payment method nonce unknown. The payment method nonce could not be found.
93506 Payment method nonce locked. The payment method nonce must be unlocked before it is used.
83518 Apple Pay 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.
93507 Cannot update Apple Pay card using payment method nonce. A vaulted payment method cannot be updated with an Apple Pay nonce. Create a new payment method instead.
93508 Card number is required. The Apple Pay PKPaymentToken payment data was malformed (did not contain a card number).
93509 Card expiration month is required. The Apple Pay PKPaymentToken payment data was malformed (did not contain an expiration month).
93510 Card expiration year is required. The Apple Pay PKPaymentToken payment data was malformed (did not contain an expiration year).
93511 Cryptogram is required. The Apple Pay PKPaymentToken payment data was malformed (did not contain a cryptogram).
83512 Apple 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.
93513 Apple Pay support is not enabled. Your merchant account is not configured for Apple Pay support. Please contact Braintree Support to configure and enable Apple Pay.
93514 Apple Pay support is not configured. Your merchant account is not configured for Apple Pay support. Please contact Braintree Support to configure and enable Apple Pay.
93522 Key mismatch storing certificate. 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
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 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.
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. Maximum 36 characters.
91721 Token is not an allowed token. We reserve 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. Maximum 175 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.
81724 Duplicate card exists. Duplicate card exists in the vault.
81725 Payment method conflict. Credit card must include one of number or venmo_sdk_payment_method_code.
91726 Venmo sdk payment method code card type is not accepted. Credit card type is not accepted by this merchant account.
91727 Invalid venmo sdk payment method code. Invalid VenmoSDK payment method code.
91728 Invalid verification merchant account ID. There must be a merchant account with this ID.
91730 Verification not supported on this merchant account. This Merchant Account does not support Credit Card Verification.
91731 Payment method nonce consumed. The payment method nonce has already been used once.
91732 Payment method nonce unknown. The payment method nonce could not be found.
91733 Payment method nonce locked. The payment method nonce must be unlocked before it is used.
91734 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.
91735 Cannot update an existing card with a payment method nonce. A payment method nonce cannot be used to update an existing credit card.
91738 Payment method specified is not a credit card. This operation requires a credit card, and the payment method you specified is not a credit card.
81736 CVV verification failed. CVV was incorrect or not supplied.
81737 Postal code verification failed. Postal code was incorrect or not supplied.
91739 Verification amount cannot be negative. The amount you specified for verification was less than zero.
91740 Verification amount is invalid. The amount you specified for verification had an invalid format.
91741 Verification amount not supported by processor. The processor you are using for verification does not allow the verification amount you specified.
91745 Invalid params for credit card update. The payment method params you supplied are not valid for updating a credit card.

PayPal

Code Text Explanation
82901 Incomplete PayPal account information. You must specify an access token or a consent code for this operation.
82902 Cannot vault one time use PayPal account. When you vault a PayPal account, you must provide a payment method nonce that was retrieved via the transaction flow.
82903 Invalid PayPal account information. You cannot specify both an access token and a consent code for this operation.
82904 PayPal accounts are not accepted. Your account has not been enabled to accept PayPal.
82905 Customer ID is required for vaulting. When adding a PayPal account to an existing customer, the customer ID is required.
92910 PayPal Communication Error. There was an error communicating with PayPal.
92911 PayPal authentication expired. The authentication you received from your user has expired.
92912 Cannot specify funding source without access token. You cannot specify a funding source without also specifying an access token.
92913 Invalid funding source selection. You sent an invalid or incomplete funding source specification.
92914 Cannot update PayPal account using payment method nonce. A payment method nonce cannot be used to update an existing PayPal account.
92915 Invalid params for PayPal account update. The payment method params you supplied are not valid for updating a PayPal account.

Recurring billing

Code Text Explanation
81901 Cannot edit a canceled subscription After a subscription has been canceled it cannot be updated
81902 ID has already been taken Subscription IDs need to be unique
81903 Price 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
81904 Price is an invalid format Price must be formatted like "10" or "10.00"
81905 Subscription has already been canceled You can't cancel subscriptions that have already been canceled
81906 ID is invalid If specifying the ID for the subscription, you can only use letters, numbers, _ and -
81907 Trial duration is an invalid format It must be 1-3 digits
81908 Trial duration is required It's required if trial period is set to true
81909 Trial duration unit is invalid Valid values are "day" and "month"
81910 Cannot edit expired subscription You cannot edit a subscription with Expired status
81923 Price is too large The price of the subscriptions is too large
91901 Merchant 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
91902 Payment method token card type is not accepted by this merchant account Your merchant account must be configured to process transactions for the card type of the payment method token
91903 Payment method token is invalid You'll get this error if we can't find a payment method with the token specific
91904 Plan ID is invalid You'll get this error if we can't find a plan with the given ID
91905 Payment 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
91906 Number of billing cycles must be numeric It must be a number
91907 Number of billing cycles must be greater than zero It must be greater than 0
91908 Inconsistent number of billing cycles You cannot specify both a number of billing cycles and never expires
91909 Number of billing cycles is too small You cannot edit a subscription and change the number of billing cycles to be below the current count of billing cycles
91911 Cannot add duplicate addon or discount Add-Ons and Discounts must be unique, but you can change the quantity
91912 Number of billing cycles cannot be blank Blanks are not allowed
91913 Billing day of month must be numeric It must be a number
91914 Billing day of month is invalid Billing day of month must be 1-28 or 31 (for the last day of every month)
91915 First billing date is invalid The first billing date is an incorrect format
91916 First billing date cannot be in the past The first billing date cannot be in the past
91917 Inconsistent start date You can only specify one of trial period, start immediately, billing day of month, and first billing date
91918 Billing day of month cannot be updated Billing day of month cannot be updated
91919 First billing date cannot be updated First billing date cannot be updated
91920 Cannot edit price changing fields on past due subscription You cannot edit any fields which could change the price on a past due subscription
91921 Invalid request format The add-ons and discounts are in an invalid format
91922 Cannot 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
91923 Mismatch currency iso code Subscription Plan currency must be the same as the merchant account's currency
91924 Payment method nonce instrument type is not accepted. The supplied payment method nonce represents a payment method of a type that is not accepted by this merchant account
91925 Payment method nonce is invalid The supplied payment method nonce was not in a valid format or is unknown
91926 Payment method nonce not associated with customer The payment method nonce used to create a subscription must be vaulted and must belong to the customer owning the subscription
91927 Payment method nonce unvaulted instrument is not accepted 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
92001 Quantity is invalid Quantity must be a number
92002 Amount is invalid Amount must be formatted like "10" or "10.00"
92003 Amount cannot be blank Blanks are not allowed
92004 Quantity cannot be blank Blanks are not allowed
92005 Number of billing cycles is invalid Number of billing cycles must be numeric
92010 Quantity must be greater than zero Quantity must be greater than 0
92011 Existing id is invalid Modification ID must be associated with the subscription
92012 Existing id is Required Modification ID is required to update a modification
92013 Inherited from id is invalid Modification with that inherited from ID is not available
92014 Inherited from id is required Must provide an inherited from ID
92015 Cannot update and remove Cannot update and remove a modification at the same time
92016 Id to remove is not present Cannot remove an ID that is not present
92017 Number of billing cycles cannot be blank Blanks are not allowed
92018 Inconsistent number of billing cycles Number of billing cycles is blank and never expires is not set to true
92019 Number of billing cycles must be greater than zero Number of billing cycles must be greater than 0
92020 Existing id is incorrect kind Existing ID must be of the type of modification that is being edited
92021 Id to remove is incorrect kind Existing ID must be of the type of modification that is being removed
92022 Cannot edit modifications on past due subscription Unable to edit modifications on subscriptions that are past due
92023 Amount is too large Amount cannot be greater than 99999.99
92024 Missing Modification is missing from the API call.

Transaction

Code Text Explanation
81501 Amount cannot be negative. Even if creating a credit transaction, the amount should be given as x.xx, not -x.xx.
81502 Amount is required. You'll get this error if amount is not given or is blank.
81503 Amount is an invalid format. Amount must be formatted like "10" or "10.00".
81528 Amount is too large. The maximum amount of a transaction varies depending on your region, but is generally between 8 and 10 characters including the decimal place.
81509 Credit 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).
81527 Custom 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.
91501 Order ID is too long. Order ID must be less than 255 characters.
91530 Cannot 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.
91504 Transaction 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.
91505 Cannot refund credit Only sale transactions can be refunded.
91506 Cannot refund a transaction unless it is settled. Transaction status must be settled to refund it.
91507 Cannot submit for settlement unless status is authorized. Transaction status must be authorized to submit the transaction for settlement.
91508 Cannot 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.)
91526 Custom 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.
91510 Customer 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.
91511 Customer 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.
91512 Transaction has already been refunded. Transactions can only be refunded once.
91513 Merchant 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.
91514 Merchant account is suspended. You'll get this error if you try to create a transaction using a suspended merchant account.
91515 Cannot 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.
91516 Cannot 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.
91527 Cannot 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.
91517 Credit card type is not accepted by this merchant account. When providing a payment method token, your merchant account must be configured to accept the card type of the card represented by the token.
91518 Payment method token is invalid. You'll get this error if the payment method token isn't in the Vault.
91519 Processor authorization code cannot be set unless for a voice authorization. You can only set the processor authorization code for voice authorization transactions.
91521 Refund amount is too large. You cannot refund more than the amount submitted for settlement.
91538 Cannot refund transaction with suspended merchant account. You cannot refund a transaction associated with a suspended merchant account.
91522 Settlement 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.
91529 Cannot 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.
91528 Subscription ID is invalid. You'll get this error if the subscription ID given isn't one of your subscriptions.
91523 Transaction type is invalid. Valid transaction types are "sale" and "credit"
91524 Transaction type is required. We need to know if you want to create a sale or a credit.
91525 Vault is disabled. If you set the option to store in Vault, your Vault needs to be enabled.
91531 Subscription status must be past due A subscription must be in past due status in order to manually retry the charge.
91547 Merchant account does not support refunds The merchant account account does not support refunds.
81531 Amount must be greater than zero The amount of a transaction cannot be zero.
81534 Tax amount cannot be negative. The tax amount cannot be less than zero.
81535 Tax amount is an invalid format. The tax amount must be a number
81536 Tax amount is too large. The tax amount cannot be bigger than 9999999.99
91537 Purchase order number is too long. The purchase order number cannot be larger than 17 characters.
91539 Voice Authorization is not allowed for this card type The specified card type does not support voice authorization codes.
91540 Transaction cannot be cloned if payment method is stored in Vault Instead, create a new transaction using the payment method's token
91541 Cannot clone voice authorization transactions Cloning voice authorizations is currently unsupported.
91542 Unsuccessful transaction cannot be cloned. Only transactions that were authorized or settled are cloneable.
91543 Credits cannot be cloned. You may only clone sale transactions
91544 Cannot clone transaction without submit_for_settlement flag. You must specify whether or not to submit the cloned transaction for settlement upon creation.
91545 Voice Authorizations are not supported for this processor Your processor does not support voice authorizations.
91546 Credits are not supported by this processor Your processor does not support credits.
91548 Purchase order number is invalid The purchase order number must be printable ASCII characters
81520 Processor authorization code is invalid Processor authorization code must be 6 characters.
91549 Payment method conflict with venmo sdk Cannot provide more than one of payment_method_token, credit_card, and venmo_sdk_payment_method_code attributes.
91550 Channel is too long Channel is too long.
91551 Settlement amount is less than service fee amount The settlement amount must be greater than or equal to the service fee amount.
91552 Service fee is not allowed on credits Service fees are allowed on sale transactions only.
91553 Sub merchant account requires service fee amount Transactions for sub merchant accounts need a service fee amount.
91554 Service fee amount cannot be negative Service fee amount must be greater than or equal to zero.
91555 Service fee amount format is invalid Service fee amount must be formatted like "10" or "10.00".
91556 Service fee amount is too large Service fee amount must be less than the transaction amount.
91557 Service fee amount not allowed on master merchant account Transactions for a master merchant account cannot have a service fee amount.
91558 Merchant account does not support MOTO This merchant account cannot be used for Mail Order/Telephone Order.
91559 Cannot refund with pending merchant account A Merchant Account must be Active in order to refund a transaction.
91560 Cannot hold in escrow The Transaction cannot be held in escrow.
91561 Cannot release from escrow The Transaction cannot be released from escrow.
91562 Cannot cancel release The Transaction's release cannot be canceled.
91563 Cannot partially refund escrowed transaction The Transaction must be fully refunded after being held in escrow.
91564 Payment method nonce consumed The payment method nonce has already been consumed.
91565 - Payment method nonce unknown The payment method nonce cannot be found among those generated for the merchant.
91576 PayPal not enabled PayPal is not enabled for your merchant account.
91577 Payment instrument not supported by merchant account Merchant account does not support payment instrument.
92201 Company 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.
92202 Phone 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
92203 Dynamic descriptors not enabled. Dynamic descriptors have not been enabled for this account. Please contact us.
92204 Descriptor name is invalid. Descriptor name must be less than or equal to 15 characters and can only contain alphabets and numbers. This will be prefixed by the preset company name for this account.
92205 International phone number is invalid. Phone can only contain numbers, dashes and periods and must be less than or equal to 13 characters.
92206 URL must be 13 characters or shorter.

Note: A different error message may be returned if the processor has different validation restrictions. The processor validation rules must be followed instead.

3D-Secure

Code Text Explanation
91570 ThreeDSecureTransactionDataDoesntMatchVerify The credit card number and expiration date used for 3D Secure verification must match the values used to create the transaction
91584 MerchantAccountDoesNotMatch3DSecureMerchantAccount The merchant account used for 3D Secure verification must match the merchant account used to create the transaction
91585 AmountDoesNotMatch3DSecureAmount The amount used for 3D Secure verification must match the amount used to create the transaction

Search

Code Text Explanation
82301 Settlement date is required You must provide a settlement date as the first argument.
82302 Settlement date is invalid The settlement date provided must be a valid date.
82303 Custom field is invalid The custom field provided must be valid.