Skip to main content
All CollectionsMaxanetPay
MaxanetPay Response Codes for declined payments
MaxanetPay Response Codes for declined payments

reference guide for common response codes for failed/declined transactions

Dan avatar
Written by Dan
Updated over a week ago

If you process a transaction and receive an error code, you can reference that code in the below list for a more detailed explanation

  • 999 – Unknown – an unknown error has occurred

  • 1 – System Error – an error within the FullsteamPay system has
    occurred that prevented the successful processing of the request. Try
    again and if the error continues please contact Fullsteam.

  • 10 – Validation Error – the request did not pass validation and could not
    be processed.

  • 20 – Transaction Not Found – the transaction referenced by the request
    was not found

  • 21 – Resource Not Found – the resource referenced by the request was
    not found

  • 22 – Duplicate RequestId – the RequestId provided in the request has
    already been used for the merchant.

  • 150 – Reversal Options Not Available – the reversal option requested
    cannot be performed on the transaction provided

  • 300 – Configuration Error – there is a configuration error within the
    FullsteamPay system. Please contact Fullsteam.

  • 400 – Communication Error – there has been a communication error
    with an external resource that caused the processing of the request to
    fail

  • 999 – Authentication Failure – the credentials provided are invalid or
    user does not have permission for action requested

  • 1007 – ProcessorDCCRequested – Fullsteam received a DCC Requested
    response from the processor. The transaction is being attempted in a
    different currency than the card holder card supports by default.

  • 1020 – ProcessorDecline – Fullsteam received a Decline response from
    the processor. This means the card issuer has declined to process the
    transaction without a specific reason provided. Card holder may call
    the card issuer for more information.

  • 1021 – Expired Card – Fullsteam received an Expired Card response
    from the processor. This means the card issuer has declined the
    transaction because the card is expired, or the expiration date
    provided is invalid.

  • 1023 – Processor Duplicate – Fullsteam received a Duplicate response
    from the processor. This means the processor has determined the
    transaction is a duplicate by their rules and the API request to
    Fullsteam did not disable duplicate detection. Currently, the
    processor defines a duplicate as 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.

  • 1024 – Processor Pickup Card – Fullsteam received a Pickup Card
    response from the processor. This means the card issuer has decided
    to decline the transaction and has requested that the merchant pick up
    the card from the card holder.

  • 1025 – Processor Referral Call Issuer – Fullsteam received a Call Issuer
    response from the processor. This means the card issuer has requested that the card holder call the card issuer to discuss the transaction and to verbally authorize the approval of the transaction.

  • 1030 – Processor Balance Not Available – Fullsteam received a Balance
    Not Available response the processor. This means the card issuer has
    declined the transaction because the balance is not available on the
    card account to support the transaction.

  • 1090 – Processor Undefined Decline or Error – Fullsteam received an
    Undefined Decline or Error response from the processor. This means
    the card issuer has declined the transaction for an undefined reason or
    some error occurred during the card issuers processing of the
    transaction.

  • 1101 – Processor Invalid Data – Fullsteam received an Invalid Data
    response from the processor. This means the processor considers the
    request that Fullsteam sent invalid. Usually the invalid information will
    be described in the response to the FullsteamPay API call. If the invalid
    information can be corrected on the integrator side, please correct and
    try again. If not, please contact Fullsteam.

  • 1102 – Processor Invalid Account – Fullsteam received an Invalid
    Account response from the processor. This means something is
    incorrect about the merchant configuration at Fullsteam or at the
    processor. Please contact Fullsteam.

  • 1103 – Processor Invalid Request – Fullsteam received an Invalid
    Request response from the processor. Usually the response message
    inside the response details will indicate the error. If integrator can
    correct, please do so and try again. If not, please contact Fullsteam.

  • 1120 – Processor Out of Balance – Fullsteam received an Out of
    Balance response from the processor. This should not occur because
    this error only occurs on merchant-initiated batch closes which are not
    currently supported.

  • 2001 – Processor Communication Error – Fullsteam received a
    Communication Error from the processor. This means the processor
    experienced an error trying to communicate with the card issuer and
    the transaction request cannot be processed. It is possible that the
    card holder will see an open authorization if they view their card
    statement online after this error. However, the transaction has been
    voided and will not settle.

  • 2002 – Processor Host Error – Fullsteam received a Host Error from the
    processor. This means the card issuer experienced an error trying to
    process the transaction request. It is possible that the card holder will
    see an open authorization if they view their card statement online after
    this error. However, the transaction has been voided and will not
    settle.

  • 2009 – Processor Error – Fullsteam received an Error response from the
    Processor. This means the processor or the card issuer experienced an
    error attempting to process the request and the transaction request
    was not processed.

  • 3101 – Signature Cancelled by User – the customer cancelled a
    contract signature process on the cloud terminal

  • 3102 – Signature Not Supported by Terminal – the terminal Id provided
    is not a terminal 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

Did this answer your question?