Overview

When a MaxanetPay transaction fails to process successfully, MaxanetPay returns a numeric response code along with a short message explaining what went wrong. This article lists every MaxanetPay response code in use by Fullsteam and the FullsteamPay processing system, grouped by category, so you can quickly look up what a code means and decide what to do next — whether that means having the bidder contact their card issuer, correcting a data entry error on your end, or calling Fullsteam Payment Services for help.

Response codes fall into four broad categories: system and validation errors (something went wrong inside MaxanetPay or FullsteamPay), card decline responses (the card issuer rejected the transaction), communication errors (an issue reaching the processor or card network), and card-present signature capture errors (problems with in-person cloud terminal signatures).

How to read and respond to a MaxanetPay response code

Most response codes that start with a 1 (1020, 1021, 1024, etc.) are coming directly from the card issuer and typically mean the bidder needs to contact their bank, try a different card, or correct information like the expiration date. Response codes in the 1, 10, 300, 400, and 2000 ranges usually indicate a system, configuration, or communication issue that Fullsteam needs to investigate on their end. Signature capture errors in the 3100 range apply only to in-person cloud terminal transactions.

System and validation response codes

Code	Name	What it means
999	Unknown	An unknown error has occurred. Retry the transaction; if it continues, contact Fullsteam Payment Services.
1	System Error	An error within the FullsteamPay system prevented the request from being processed. Try again — if the error continues, contact Fullsteam.
10	Validation Error	The request did not pass validation and could not be processed. Usually indicates a data-format problem in the submitted request.
20	Transaction Not Found	The transaction referenced by the request was not found in the FullsteamPay system.
21	Resource Not Found	The resource referenced by the request (customer, merchant, token, etc.) was not found.
22	Duplicate RequestId	The RequestId provided in the request has already been used for the same merchant. FullsteamPay prevents duplicate submissions with the same ID.
150	Reversal Options Not Available	The reversal option requested cannot be performed on the transaction provided — for example, trying to void a transaction that has already settled.
300	Configuration Error	There is a configuration error within the FullsteamPay system. Contact Fullsteam Payment Services.
400	Communication Error	A communication error with an external resource caused the processing of the request to fail. Retry; escalate to Fullsteam if it persists.
999 (auth)	Authentication Failure	The credentials provided are invalid or the user does not have permission for the action requested.

Card decline response codes (from the card issuer)

These codes come from the card issuing bank (Visa, Mastercard, Amex, Discover, etc.) via the processor. They typically mean the bidder should try a different card, correct card information, or contact their card issuer directly. The merchant usually cannot fix these.

Code	Name	What it means and what to do
1007	Processor DCC Requested	The transaction is being attempted in a different currency than the cardholder's card supports by default. Dynamic Currency Conversion was requested.
1020	Processor Decline	The card issuer declined the transaction without giving a specific reason. The cardholder should call their card issuer to ask why, or try a different card.
1021	Expired Card	The card issuer declined because the card is expired or the expiration date provided is invalid. Ask the bidder to update the expiration date or use a current card.
1023	Processor Duplicate	The processor identified the transaction as a duplicate by its own rules. The processor considers a duplicate to be a transaction for the same amount on the same card for the same merchant within the same batch, within 25 transactions of the matching transaction. Wait, change the amount, or contact Fullsteam to disable duplicate detection for a specific case.
1024	Processor Pickup Card	The card issuer has decided to decline the transaction and has requested that the merchant pick up the card from the cardholder. Do not attempt the transaction again on the same card.
1025	Processor Referral Call Issuer	The card issuer has requested that the cardholder call the card issuer to discuss the transaction and verbally authorize approval. Ask the bidder to call their card's customer service number.
1030	Processor Balance Not Available	The card issuer declined because the balance is not available on the card account to support the transaction. The bidder will need to use a different card or top up their account.
1090	Processor Undefined Decline or Error	The card issuer declined for an undefined reason, or some error occurred during the card issuer's processing.
1101	Processor Invalid Data	The processor considers the request that FullsteamPay sent to be invalid. Usually the invalid information will be described in the response details. If correctable on the merchant side, correct and try again; otherwise contact Fullsteam.
1102	Processor Invalid Account	Something is incorrect about the merchant configuration at Fullsteam or at the processor. Contact Fullsteam Payment Services.
1103	Processor Invalid Request	The processor rejected the request as invalid. Usually the response message inside the response details indicates the specific error.
1120	Processor Out of Balance	This should not occur in normal MaxanetPay use — it only occurs on merchant-initiated batch closes, which are not currently supported.

Communication error response codes

Code	Name	What it means
2001	Processor Communication Error	The processor experienced an error trying to communicate with the card issuer. The transaction has been voided and will not settle, but the cardholder may briefly see an open authorization on their card statement.
2002	Processor Host Error	The card issuer experienced an error trying to process the transaction. The transaction has been voided and will not settle, but the cardholder may briefly see an open authorization.
2009	Processor Error	The processor or card issuer experienced a general error attempting to process the request. The transaction was not processed.

Card-present signature capture response codes

These 3100-series codes only apply to in-person cloud terminal transactions where a contract signature is captured on the terminal.

Code	Name	What it means
3101	Signature Cancelled by User	The customer cancelled the contract signature process on the cloud terminal.
3102	Signature Not Supported by Terminal	The terminal ID provided is not a model that supports contract signature capture.
3103	Signature Terminal Error	An error occurred on the terminal when attempting a contract signature capture.
3199	Signature Unknown Error	An unknown error occurred when attempting a contract signature capture.

Common questions about MaxanetPay response codes

What should I tell a bidder when their card is declined with code 1020?

Code 1020 means the bidder's card issuer declined the transaction without giving a specific reason. Ask the bidder to call the customer service number on the back of their card and ask their bank why the transaction was blocked, or ask them to try a different card. You, the merchant, cannot override this decline from the Maxanet side.

The bidder's card is showing as expired (code 1021) but they say it's not — what now?

Code 1021 means the card issuer reported the card as expired, or the expiration date entered did not match the card issuer's records. Ask the bidder to double-check the expiration date on the physical card and re-enter it. If the card truly is not expired, they may need to call their card issuer to investigate.

I got a duplicate transaction error (code 1023) — did the bidder get charged twice?

No. Code 1023 means FullsteamPay blocked a potential duplicate before it was charged. The duplicate-detection rule triggers when the same amount is submitted on the same card for the same merchant within the same batch, within 25 transactions of the matching transaction. If you genuinely need to process the second transaction (for example, the bidder intentionally bought two of the same item), wait for the first transaction to leave the 25-transaction window, or contact Fullsteam for help disabling duplicate detection for the specific case.

A transaction shows as open authorization on a bidder's card even though I got an error (2001 or 2002) — will the bidder be charged?

No. When MaxanetPay returns codes 2001 or 2002 (Processor Communication Error or Processor Host Error), the transaction has been voided on the Fullsteam side and will not settle. The bidder may temporarily see an open authorization on their card statement, but it will drop off automatically within a few business days without actually being charged.

What is code 1024 (Pickup Card) and is it serious?

Code 1024 is a strong signal from the card issuer to physically retain the card because the issuer believes it may be lost, stolen, or fraudulent. Do not attempt to process the transaction again on the same card. For online bidders, you cannot physically retain the card — simply decline to process that card and ask the bidder for an alternative payment method.

Who do I contact for codes 1, 10, 300, or 999?

These are system and configuration codes on the FullsteamPay side. Retry the transaction once; if the error continues, contact Fullsteam Payment Services at 334-329-6775 (option 4, then option 2) or email payments.support@fullsteam.com with the exact code number and approximate time of the failure so they can investigate logs.

MaxanetPay response codes reference guide for declined or failed transactions