Error messages are returned by the API when the client’s request to the TabaPay API is misconfigured.

Error Messages	Description	Possible Status Code	Client Action
Account	The account object may be formatted wrong or incorrect	400	Check your JSON formatting and the account object fields
Accounts	The account object may be formatted wrong or incorrect		Check your JSON formatting and the account object
Account Card Expiration Date	The card in the account object or saved in the accountID may be expired		Check the card expiration date by using Query Card API to check card details
account.accountID	The accountID field may be formatted wrong or incorrect		Check your JSON formatting and the sourceAccountID or destinationAccountID within accounts object
account.securityCode	The card security code field (CSC) in the account object may be formatted wrong or incorrect		Check your JSON formatting and card security code field within accounts object.
accountID	Account ID in the formatting is wrong. AccountIDs are 22 characters long and are generated by the Create Account API		If it is a Create Account API, or Query Card API Request, check the unique AccountID listed in the path parameters. If it is a Create Transaction API Request, check the sourceAccountID or destinationAccountID in the request body parameters.
accounts.destination	The destinationAccount or destinationAccountID in the request is wrong. AccountIDs are 22 characters long and are generated by the Create Account API		Double check your JSON formatting and accounts object.
accounts.destinationAccount.bank.routingNumber	The routingNumber in the destinationAccount may be formatted wrong or incorrect	400	Check for the correct routingNumber in the API request
accounts.destinationAccount.card	The card object in the destinationAccount object may be formatted wrong or incorrect		Check your JSON formatting and the card object
accounts.destinationAccount.card.expirationDate	The card expiration date in the destinationAccount object may be formatted wrong or incorrect		Check your JSON formatting and the card object
accounts.destinationAccount.owner	The destinationAccount owner object may be formatted wrong or incorrect		Check your JSON formatting and the destination account owner object
accounts.destinationAccount.owner.address.city	The destinationAccount owner city field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner city field
accounts.destinationAccount.owner.address.country	The destinationAccount owner country field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner country field
accounts.destinationAccount.owner.address.line1	The destinationAccount owner address line 1 field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner address line 1 field
accounts.destinationAccount.owner.address.line2	The destinationAccount owner address line 2 field may be formatted wrong or incorrect	400	Check your JSON formatting and the destinationAccount owner address line 2 field
accounts.destinationAccount.owner.address.state	The destinationAccount owner state field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner state field
accounts.destinationAccount.owner.address.zipcode	The destinationAccount owner zipcode field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner zipcode field
accounts.destinationAccount.owner.name.first	The destinationAccount owner first name field may be formatted wrong or incorrect		Check your JSON formatting and the destinationAccount owner first name field
accounts.destinationAccount.owner.name.last	The destinationAccount owner last name field may be formatted wrong or incorrect		Check your JSON formatting and destinationAccount owner the last name field
accounts.destinationAccount.owner.phone.number	Phone number field formatting may be incorrect		Check your JSON formatting and the destinationAccount owner phone number field
accounts.source	The sourceAccount or SourceAccountID field formatting or value may be incorrect		Check your JSON formatting and the accounts source object
accounts.sourceAccount.bank.routingNumber	Account bank routing number field formatting may be incorrect	400	Check your JSON formatting and sourceAccount bank routing number field
accounts.sourceAccount.card	Source Account card field field be incorrect		Check your JSON formatting and the sourceAccount card field
accounts.sourceAccount.card.accountNumber	Source Account Card Account Number field may be incorrect		Check your JSON formatting and the sourceAccount owner card account number field
accounts.sourceAccount.card.expirationDate	Source Account Card Expiration date field may be incorrect		Check your JSON formatting and the sourceAccount owner card expiration date field
accounts.sourceAccount.card.securityCode	Source Account Card security code field may be incorrect		Check your JSON formatting and the sourceAccount owner card security code field
accounts.sourceAccount.owner.address.city	City field within the owner address object may be incorrect		Check your JSON formatting and the sourceAccount owner city field
accounts.sourceAccount.owner.address.line1	Line 1 address field within the account owner object may be incorrect		Check your JSON formatting and the sourceAccount owner address line 1 field
accounts.sourceAccount.owner.address.line2	Line 2 address field within the account owner object may be incorrect	400	Check your JSON formatting and the sourceAccount owner address line 2 field
accounts.sourceAccount.owner.address.state	State field within the account owner address object may be incorrect		Check your JSON formatting and the sourceAccount owner state field
accounts.sourceAccount.owner.address.zipcode	Zip code field within the account owner address object may be incorrect		Check your JSON formatting and the sourceAccount owner address zip code field
accounts.sourceAccount.owner.name	Account owner name object may be incorrect		Check your JSON formatting and the sourceAccount owner name object
accounts.sourceAccount.owner.name.first	Account owner first name field may be incorrect		Check your JSON formatting and the sourceAccount owner first name field
accounts.sourceAccount.owner.name.last	Account owner last name field may be incorrect		Check your JSON formatting and the sourceAccount owner last name field
accounts.sourceAccount.owner.phone.number	Account owner phone field may be incorrect		Check your JSON formatting and the sourceAccount owner phone field
ach	accountID payment instrument may not allow ACH (e.g. it may be a card) JSON formatting for ACH may also be off	400	Check your JSON formatting, the accountsID capabilities for ACH, and the achOptions and achEntryType fields
achEntryType	achEntryType field may be incorrect		Check your JSON formatting and the achEntryType field
achOptions	achOptions field may be incorrect		Check your JSON formatting and the achOptions field
amount	The amount may exceed the allowed amount per day, or is formatted incorrectly		Be sure to include double digits for each amount string Check your client limits with Retrieve ClientIf you need to increase your daily limits, refer to Adjusting Limits
Authorization	The authorization header may be missing, misspelled, or formatted wrong If too many headers are included (more than 8), an error may occur due to truncation	401	Check your authorization header, the amount of headers, spelling of your headers, or your bearer token
Authorization Bearer	Authorization bearer header may be misspelled or formatted wrong	401	Check your bearer token spelling or any bearer token typos
authorize	Error should occur when attempting an Auth and Capture payment with the query parameter ?authorize. JSON formatting may be incorrect	400	Check your JSON formatting and the query parameter ?authorize
Blocked Card	Card used to complete the payment is blocked		Check the card details using the Query Card API request
Blocked Country Push - 044	Country of the receiving account is blocked		Check the account details with Query Card API Check the response for any OFAC values
card	Card object may be formatted wrong or incorrect AccountID may also contain the card object and may be formatted wrong or incorrect		Check either the card object in the request or confirm the accountID field is correct
Card Data	Related to RSA encrypted card dataCard data field may be formatted wrong or incorrect		Check the card data field for the format and correct data string
Card Data Client	Client SSO Token does not match the Client ID		Check the SSOToken that has been used in the request
Card Network	Card network field in the card object may be formatted wrong or incorrect		Check your JSON formatting and the correct card network
Card Number	Card number field in the card object may be formatted wrong or incorrect		Check your JSON formatting, and the card number field
card.accountNumber	Account number field in the card object may be formatted wrong or incorrect	400	Check the accountNumber field within the card object
card.data	Related to RSA encrypted card dataCard data field may be formatted wrong or incorrect		Check the card data field for the format and correct data string
card.expirationDate	Expiration date field in the card object may be formatted wrong or incorrect		Check your JSON formatting and the card expirationDate field
card.keyID	keyID field in the card object may be formatted wrong or incorrect		Check your JSON formatting and the the card keyID field
card.mobilePay.cryptogram	Apple Pay request. The cryptogram field may be formatted wrong or incorrect		Check your JSON formatting and the mobilePay cryptogram field
card.mobilePay.eciIndicator	Apple Pay request. The eciIndicator field may be formatted wrong or incorrect		Check your JSON formatting and the mobilePay eciIdenicator field
card.mobilePay.transactionID	Apple Pay request. The transactionID field may be formatted wrong or incorrect		Check your JSON formatting and the the mobilePay transactionID field
card.mobilePay.type	Apple Pay request. The type field may be formatted wrong or incorrect	400	Check your JSON formatting and the the mobilePay type field
card.processor.token	The card processor token field may be formatted wrong or incorrect		Check your JSON formatting and the processor token field
card.securityCode	The card securityCode field may be formatted wrong or incorrect		Check your JSON formatting and the card securityCode field
card.token	The card token field may be formatted wrong or incorrect		Check your JSON formatting and the card token field
ClientID	22 character ClientID may be misspelled or incorrectly input		Check the ClientID that is linked in the endpoint Path Note: Do not expose your ClientID publicly
Content-type	The headers or JSON formatting may be wrong or incorrect		Check the content type header for a JSON value
corresponding.address.city	The corresponding city field may be formatted wrong or incorrect		Check your JSON formatting and the corresponding city field
corresponding.address.country	The corresponding country field may be formatted wrong or incorrect	400	Check your JSON formatting and the corresponding country field
corresponding.address.line	The corresponding address line field may be formatted wrong or incorrect		Check your JSON formatting and the corresponding address line field
corresponding.address.state	corresponding.address.state		Check your JSON formatting the corresponding state field
corresponding.address.zipcode	The corresponding zip code field may be formatted wrong or incorrect		Check your JSON formatting the corresponding zipcode field
corresponding.name.first	The corresponding first name field may be formatted wrong or incorrect		Check your JSON formatting and the corresponding first name field
corresponding.name.last	The corresponding last name field may be formatted wrong or incorrect		Check your JSON formatting and the corresponding last name field
corresponding.sourceOfFunds	The corresponding sourceOfFunds field may be formatted wrong or incorrect		Check your JSON formatting and the corresponding sourceOfFunds field
correspondingID	The correspondingID field may be formatted wrong or incorrect	400	Check your JSON formatting and the correspondingID field
CVV2	The securityCode field may not match the CVV2 on file with the issuer	400	Check the securityCode field for the value. Use Query Card API to confirm the CVV2 with the issuer
Destination Disabled	The destinationAccount, or destinationAccountID not be enabled	422	Check the destinationAccount or destinationAccountID through Query Card If you are using RTP then you can use Query Bank
DeviceBlob	Device Blob field and ID may be formatted wrong or incorrectDevice object is used for EMV payments, or Google Pay	400	Check your JSON formatting and the blob field
Duplicate	Identified accountIDs using the same PAN	409	Duplicate Card Check may be enabled. To learn more, refer to Create Account API Query Parameters.
Expiration Date	Expiration date field may be formatted wrong or incorrect	400	Check the expirationDate field for the correct format and valueShould be YYYYMM format
Expiration Date: 20
Expiration Date: 20-202
Expiration Date: 20-204
Expiration Date: 20-205
Expiration Date: 20-207
Expiration Date: 20-208
Expiration Date: 20-209
Expiration Date: 20-210
Expiration Date: 20-211
Expiration Date: 200329
Expiration Date: 20284
Expiration Date: 20293
Headers	Headers formatting is incorrect	400	Check the headers in your request for the correct format
IP Address	IP Address that has sent the request is not approved or whitelisted	401 or 403	Contact TabaPay Support or email help@tabapay.com to request any IP address to be whitelisted
JSON	JSON formatting is incorrect	400	Double check the JSON formatting
JSON NOT PACKED	JSON request has whitespace in between characters, the JSON is not compact		JSON request needs to be condensed or compact in every request body parameters
Key	They Key ID field may be formatted wrong or incorrect		Check your JSON formatting and the keyID field
Limits Lock	Client limits have been reached. The amount may exceed the allowed amount per day for push or pull		Check your client limits with Retrieve ClientIf you need to increase your daily limits, refer to Adjusting Limits
location.address.city	Location city field may be formatted wrong or incorrect		Check your JSON formatting and the location adress city field
location.address.country	Location country field may be formatted wrong or incorrect		Check your JSON formatting and the location address country field
location.address.state	Location state field may be formatted wrong or incorrect		Check your JSON formatting and the location address state field
location.address.zipcode	Location zipcode field may be formatted wrong or incorrect	400	Check your JSON formatting and the location address zipcode field
location.name	Location name field may be formatted wrong or incorrect		Check your JSON formatting and the location name field
memo	Memo field may be formatted wrong or incorrect		Check the memo name field formatting
name.first	First name field may be formatted wrong or incorrect		Check your JSON formatting and the First name field
name.last	Last name field may be formatted wrong or incorrect		Check your JSON formatting and the last name field
owner	Owner object may be formatted wrong or incorrect		Check your JSON formatting and the owner object fields
owner.address	Owner address object and fields may be formatted wrong or incorrect		Check your JSON formatting and the owner address fields
owner.address.city	Owner city field may be formatted wrong or incorrect	400	Check your JSON formatting and the owner address city field
owner.address.country	Owner country field may be formatted wrong or incorrect		Check your JSON formatting and the owner address country field
owner.address.line1	Owner address line 1 field may be formatted wrong or incorrect		Check your JSON formatting and the owner address line 1 field
owner.address.line2	Owner address line 2 field may be formatted wrong or incorrect		Check your JSON formatting and the owner address line 2
owner.address.state	Owner state field may be formatted wrong or incorrect		Check your JSON formatting and the owner address state field
owner.address.zipcode	Owner zipcode field may be formatted wrong or incorrect		Check your JSON formatting and the owner address zipcode field
owner.name	Owner name object may be formatted wrong or incorrect		Check your JSON formatting and the owner name object
owner.name.first	Owner first name field may be formatted wrong or incorrect	400	Check your JSON formatting and the owner first name field
owner.name.last	Owner last name field may be formatted wrong or incorrect		Check your JSON formatting and the owner last name field
owner.name.middle	Owner middle name may be formatted wrong or incorrect		Check your JSON formatting and the owner middle name field
owner.phone.countryCode	Phone countryCode field may be formatted wrong or incorrect		Check your JSON formatting and the phone countryCode field
owner.phone.number	Owner phone number field may be formatted wrong or incorrect		Check your JSON formatting and the owner phone number field
Permission	Feature or request may not be enabled	403	To request feature to be enabled, contact Contact TabaPay Support or email help@tabapay.com
pullOptions.3DSecure	3DSecure object may be formatted wrong or incorrect	400	Check your JSON formatting and the 3DSecure field
pullOptions.3DSecure.ECI	ECI field may be formatted wrong or incorrect		Check your JSON formatting and the ECI Indicator field
pullOptions.level3.taxRate	taxRate field may be formatted wrong or incorrect		Check your JSON formatting and the taxRate field
pullOptions.securityCode	Card securityCode field may be formatted wrong or incorrect		Check your JSON formatting and the securityCode field
referenceID	The required 1-15 character unique referenceID may be a duplicate of an already used referenceID		Try a new referenceID combination
routingNumber	routingNumber field may be formatted wrong or incorrect		Check your JSON formatting and the routingNumber field
Security Code	SecurityCode field may be formatted wrong or incorrect	400	Check your JSON formatting and the securityCode field
Settlement Account	Settlement Account ID may be incorrect	400	Check your JSON formatting and the accountID (sourceAccountID or destinationAccountID) where the settlement Account is linked for the correct value
Soft Descriptor	Soft Descriptor object may be formatted wrong or incorrect	400 or 403	If 400, check your JSON formatting and the softDescriptor object If 403, request to enable at help@tabapay.com
softDescriptor.address	Soft Descriptor address object may be formatted wrong or incorrect	400	Check your JSON formatting and the softDescriptor address field
softDescriptor.address.city	Soft Descriptor city field may be formatted wrong or incorrect		Check your JSON formatting and the softDescriptor city field
softDescriptor.address.county	Soft Descriptor county field may be formatted wrong or incorrect		Check your JSON formatting and the softDescriptor county field
softDescriptor.address.line1	Soft Descriptor address line 1 field may be formatted wrong or incorrect		Check your JSON formatting and the softDescriptor address line 1 field
softDescriptor.address.state	Soft Descriptor state field may be formatted wrong or incorrect		Check your JSON formatting and the softDescriptor state field
softDescriptor.address.zipcode	Soft Descriptor zipcode field may be formatted wrong or incorrect		Check your JSON formatting and the softDescriptor zipcode field
softDescriptor.name	Soft Descriptor name filed may be formatted wrong or incorrect	400	Check your JSON formatting and the softDescriptor name field
softDescriptor.phone.number	Soft Descriptor phone number field may be formatted wrong or incorrect	400	Check your JSON formatting and the softDescriptor phone number field
Source Disabled	The Source Account may be not enabled for push or pull	422	Check the Source Account capabilities with Query Card API or if for RTP use Query Bank API
SSOToken Expired	The SSOToken used in the request has surpassed it’s expirationSSOTokens expire after ~5 minutes	400	Generate a new token to use within 5 minutes
SubClientID	SubClientID ID in the path parameters is wrong		Check the SubClientID variable in the path parameters for the correct format and value
tagName	Visa+ TagName is not detected, or incorrect		Check your JSON formatting and the spelling of the name in the request
Token	The iFrame token, or bearer token is incorrect or misspelled	400 (iFrame) or 401 (bearer)	Check the spelling of the token field, bearer token header, and the valuesBearer tokens will be in the headers, all other tokens are in the request
Transaction Limit	The transaction amount exceeds the current client transaction amount limit	422	Check your client limits with Retrieve Client API. If you need to increase your daily limits, refer to Adjusting Limits
type	The transaction type value or field is incorrect, or does not match with accounts listed	400	Check your JSON formatting and the type field
URL	Depending on the API request the endpoint may have incorrect	404	Check the endpoint syntax, spelling, and version (e.g/v1/ or /v2/, etc.)
XB AFT	Cross-border account funding (AFT) not allowed for payments that originate in the US	400	Check your countryCode and destination account Review rules for Cross-border Transaction