This article provides information on General Error transaction status in Authorize.net and how to address it.

What is a general error transaction?

A general error transaction indicates that a transaction could not be processed successfully due to an unspecified error. This error can occur for various reasons, ranging from technical issues to problems with the transaction information and details.

Common Causes of General Error Transactions:

• Technical Issues: Problems with the payment gateway, such as server downtime or connectivity issues.
• Invalid Transaction Details: Errors in the transaction details, such as incorrect payment information or missing required fields.
• Merchant Configuration Issues: Incorrect settings or configuration of the processing configuration or merchant account seutp.
• Recurring Billing:
  • Credit Card:
    • Expired Credit Cards: The credit card on file for the subscription has expired.
    • Processing Error: The payment processor returned an error. This can happen if a card type is not supported, or if a merchant tries to submit a $0 authorization request as part of an ARB subscription to a processor that does not support $0 authorizations.
    • Test Mode: The account was in Test Mode at the time of the scheduled payment.
  • eCheck:
    • eCheck Service Status: eCheck has been disabled on the account or the specific eCheck type has been disabled on the account.
    • Monthly Processing Limit Reached: The merchant has reached their monthly processing limit.
    • Returned eCheck (ACH) transaction: A Return was received for this customer on a previous transaction.
    • Notice of Change (NOC): A Notice of Change was received for this customer on a previous transaction.
    • Test Mode: The account was in Test Mode at the time of the scheduled payment.
  • Trial Amount: Trial amount set to $0.00
  • Other Note: ARB subscriptions will not be suspended and will not automatically terminate unless a failure occurs on the first transaction attempt or a failure occurs on the first transaction attempt after a subscription update.

Solution:

1. Check Error Code and Message: Authorize.net provides specific error codes and messages that can help identify the issue. Review the error code and message associated with the transaction in the Merchant Interface.
2. Review Transaction Details: Ensure that all transaction details are accurate and complete. Check for any missing or incorrect information.
3. Verify Account Configuration: Ensure that your Merchant Account is enabled and configured correctly and provided the correct processor configuration to Authorize.net for your account.
4. Contact Support: If the error persists and you cannot determine the cause, contact Authorize.net Client Services for further assistance. Provide support with the transaction details and error code for a more accurate diagnosis.