Errors and Error Handling

Error Message	Status	Description
Failed to process transaction	500	You have attempted to process a credit card transaction using a `cardToken` that is not associated with the API token, Helcim account, or `customerCode` that you have passed in your request. Check your Customer section in your Helcim account to confirm that the `cardToken` is correct before attempting your request again. Helcim developer test accounts are unable to process test ACH transactions and this error will be returned if attempted.
Not allowed to send full card number	401	You have attempted to process a transaction using a full card number and are not approved to do so. Utilize HelcimPay.js or Helcim.js to tokenize card details and send a `cardToken` in the `cardData` object instead of the card details.
Missing required cardData	400	When a request is sent to the Payment API and a required `card` or `cardToken` object is missing, the API will respond with a "Missing required data" error object. Please note that if neither potential `cardData` object is provided, the API will respond to indicate that the `cardNumber`, `cardExpiry`, and `cardCVV` are missing, even if not approved for full card numbers. Please send either a `card` object or `cardToken` to resolve this error based on your accounts approval for sending full card numbers.
Missing required data	400	The Helcim API will respond with a "Missing required data" error when a data object required for your request is missed. In addition to `cardData` as outlined above, this error can be triggered by a range of required data objects being missing from your request. The errors object will outline what data object is missing.
Missing idempotency key	400	You have attempted to process a transaction without sending a valid idempotency key with your request. Generate a new `idempotency-key` and send this in the header of your request before attempting your request again. Go to our article on Idempotency keys for more information on how to generate these.
Failed to retrieve card transaction	400	When attempting to capture, refund, or reverse a transaction, the Helcim API will return a "Failed to retrieve card transaction" error, if the `transactionId` does not match any transaction in your Helcim account. Check your `transactionId` is correct through your Helcim account, or the Card Transaction API before attempting your request again.
Disabled achSetting	401	If you attempt to send a request to the Process Withdraw Transaction endpoint and your account does not have ACH Bank Payments enabled, the API will return an error response of Disabled achSetting. To resolve this error, log into your Helcim account and go to Settings, then ACH Bank Payment Settings, in order to toggle on "Enable ACH Bank Payments" for your Helcim account. Please note that some accounts are restricted from processing through ACH entirely and you should review our Acceptable Use Policy if this setting is not available for you.