Error reasons

When a payment isn't successful, the API still responds with HTTP status 200 OK or 201 Created, but the transaction status is error. When the card issuer or the card network declines a card payment, the payment_method_details of the transaction tell you why:

• elavon_response_code: the response code, three digits. See Response codes.
• elavon_advice_code: the merchant advice code, two digits. It tells you whether and when you can try again. See Merchant advice codes.

The reason of the transaction is Denied at Elavon. Base your logic on the codes, not on the reason.

{
  "status": "error",
  "transactions": [
    {
      "status": "error",
      "payment_method": "credit-card",
      "payment_method_brand": "mastercard",
      "reason": "Denied at Elavon",
      "payment_method_details": {
        "elavon_response_code": "173",
        "elavon_advice_code": "02"
      }
    }
  ]
}

The response is shortened. In this example, the issuer declined the payment for its own policy (173) and advises to try again later (02).

Soft declinesCopy Anchor Link

With a soft decline, the issuer doesn't refuse the payment, but asks for strong customer authentication first: response code 144, or 148 to 150 when an exemption from strong customer authentication can't be used. The transaction then also has a soft_declined event. Retry the payment with 3-D Secure.

Response codesCopy Anchor Link

elavon_response_code holds one of these codes.

Merchant advice codesCopy Anchor Link

elavon_advice_code tells you whether and when you can try the payment again. Don't retry a payment with code 03 or 21. With codes 24 to 30, wait at least the time of the code before you retry.