Error Message | System Logic | What It Means | What To Do |
Invalid Card# or Release#. Please try again or contact AEG Support | The backend validation routine failed to match the submitted card or release number against the database records. The input did not pass validation, or the record was not found in the payment authorization table. | The card or release number you entered is wrong or not recognized. | Double-check the card/release number. If correct, contact AEG Support. |
This Fuel Authorization is no longer valid. Please try again or contact AEG Support | The fuel authorization token provided is expired, revoked, or has already been marked as “used” in the authorization table. The backend rejected the token during transaction validation. | The fuel authorization you’re using isn’t valid anymore. | Request a new fuel authorization or contact AEG Support. |
Processor allows one fuel ticket per transaction | The transaction object failed a business rule check: the backend enforces a constraint that only one fuel line item is allowed per transaction record. Multiple fuel lines trigger a validation error. | You can only process one fuel ticket at a time. | Submit each fuel ticket as a separate transaction. |
Please contact X-1 Support | The backend attempted to access a nullable object property (e.g., a required field was null). This triggered a NullReferenceException in the application logic. | Something went wrong in the system. | Contact X-1 Support for help. |
Call AEG Customer Svc. 1-305-913-5254. Unable to find merchant fueler. | The merchant fueler ID provided in the transaction does not exist in the merchant_fueler table, or the lookup query returned zero results. | The system can’t find the merchant fueler. | Call AEG Customer Service for assistance. |
Duplicate Invoice#. Try with a new transaction | The invoice number submitted matches an existing record in the invoices table with a status of “completed” or “pending.” The backend enforces uniqueness for invoice numbers. | You’re trying to use an invoice number that’s already been used. | Use a new, unique invoice number for your transaction. |
Tail number not associated with payment method. Try a different payment method | The backend cross-references the tail number against the payment method mapping table. If no association exists, the transaction fails validation. | The tail number isn’t set up for this payment method. | Try a different payment method or contact support to link the tail number. |
Input string was not in a correct format. | The backend parser encountered a type mismatch (e.g., string instead of integer, or invalid date format) when deserializing the input payload. | Some information entered is in the wrong format. | Review all fields for typos or incorrect formats and try again. |
Fuel Release Invalid for this Merchant location. Please try again or contact AEG Support | The fuel release code provided does not match any valid release codes for the merchant’s location in the fuel_release table. The backend enforces location-based release validation. | The fuel release isn’t valid for this location. | Check the merchant location and fuel release code, or contact AEG Support. |
Call AEG Customer Svc. 1-305-913-5254. Authorization has not been granted | The backend authorization workflow returned a negative status code (e.g., -2) after checking transaction eligibility, limits, or account status. | The payment wasn’t authorized. | Call AEG Customer Service for help. |
An error has occurred trying to get the invoice number. Please contact AEG Support | The backend failed to retrieve the invoice number due to a database query error, missing record, or timeout in the invoice lookup service. | The system couldn’t get the invoice number. | Contact AEG Support for assistance. |
Card Expired. | The backend compared the card’s expiration date to the current system date and found it to be in the past. The transaction was rejected by the card validation logic. | The card you’re using is expired. | Use a valid, non-expired card. |
A value on this transaction does not meet processor requirements. Please contact X-1 Support | One or more fields in the transaction payload failed backend validation (e.g., integer overflow, out-of-range value, or failed type conversion). | Some information entered isn’t allowed by the system. | Review transaction details for errors or contact X-1 Support. |
Merchant is not active. Please contact X-1 Support | The merchant record in the merchants table has a status of “inactive” or “disabled.” The backend blocks transactions for inactive merchants. | The merchant account isn’t active. | Contact X-1 Support to reactivate or resolve the issue. |
Call AEG Customer Svc. 1-305-913-5254. You must have at least one billing primary email notification setup if you choose to use auto ar email notifications. | The backend checked for a billing primary email in the user profile or notification settings table and did not find one. Auto AR notifications require this field to be populated. | You need a billing email set up for notifications. | Set up a billing primary email or call AEG Customer Service. |
Product/Service (Id: 61 Code :8) missing mapping. Please contact X-1 Support | The backend attempted to map the product/service ID to a payment method but found no corresponding entry in the product_service_mapping table. | The product or service isn’t set up in the system. | Contact X-1 Support to add or correct the mapping. |
Processor does not allow invoices dated in the future. Please use current date | The backend compared the invoice date to the current system date and rejected the transaction because the date was in the future. | You can’t use a future date for invoices. | Use today’s date or an earlier date for your invoice. |
Processor does not allow multiple tail numbers per transaction | The backend enforces a constraint that all detail lines in a transaction must reference the same tail number. Multiple tail numbers trigger a validation error. | You can only use one tail number per transaction. | Make sure all details use the same tail number. |
Payment method used is inactive. Please contact X-1 Support | The payment method record in the payment_methods table has a status of “inactive.” The backend blocks transactions using inactive payment methods. | The payment method isn’t active. | Use a different payment method or contact X-1 Support. |
Tips for Successful Transactions
Double-check all card and billing details before submitting.
Use active cards with sufficient funds.
If you see a processor outage, wait and retry.
For product/service errors, verify selections with support.
Keep support contact information handy for persistent issues.