Decline codes

When a card payment is declined, the transaction comes back with status: "Declined". The decline code and description come nested inside the response object, not as top-level fields:

• responseCode and responseText: the general decline code and description. Always present.
• processorError and processorMessage: appear when the decline comes directly from the processor (for example, insufficient funds).
• rules[]: appears instead of processorError/processorMessage when the decline comes from a validation rule (for example, a 3DS authentication failure), as an array of {code, message} objects.

This page is the catalog of the decline codes returned by the card processor.

Example: insufficient-funds decline

{
  "status": "Declined",
  "transaction_status": "Declined",
  "response": {
    "responseCode": "021",
    "responseText": "Tarjeta sin fondos",
    "processorError": "K006",
    "processorMessage": "Transacción declinada.",
    "transactionStatus": "DECLINED"
  }
}

Example: validation-rule decline

{
  "status": "Declined",
  "transaction_status": "Declined",
  "response": {
    "responseCode": "K322",
    "responseText": "Transacción rechazada.",
    "rules": [
      { "code": "K325", "message": "Autenticación fallida - Error de autenticación" }
    ],
    "transactionStatus": "DECLINED"
  }
}

Soft vs hard declines

Every code has a type that determines whether retrying makes sense:

Numeric codes

2- and 3-digit codes:

Alphanumeric codes

K codes

Next steps