Skip to main content

CourtPay: Payment Declines and Retry Compatibility

Understand Why Payments Are Declined and When a Transaction Can Be Reattempted

Written by Mari Bern

Introduction

Feature Summary: Why issuing banks decline transactions, why decline reasons are often vague, and how to use the response code to decide whether a transaction can be reattempted.

Use Cases:

  • Why issuing banks decline transactions

  • Why decline reasons are often vague

  • How to use the response code to decide whether a transaction can be reattempted


Part 1: Why Issuers Decline

There are three primary reasons an issuing bank declines a transaction.

1. No funds available. The account does not have enough money or credit to cover the charge. This is most common with prepaid and debit cards that run out of funds, but it also happens on credit cards when the cardholder reaches their credit limit.

2. Outdated or inaccurate credentials. The card details on file no longer match what the issuer has on record. Most of these declines occur on subscriptions and recurring payments: a customer subscribes with a valid card, authorizes ongoing charges without re-entering payment information (called "card on file"), and the card expires some time later. This can also happen on a first charge if the customer accidentally enters the wrong CVC.

3. Suspicion of fraud. The issuer believes the account owner may not be the one making the transaction, or it detects suspect behavior such as an incorrect CVC being submitted at checkout.

The Generic Decline Problem

A large percentage of declines come back as do not honor, generic decline, or transaction not allowed. These codes carry no specific information about why the charge was not authorized.

This is frustrating for merchants. Customers who experience a declined payment will often give up rather than try another payment method, which means lost sales and potentially additional sales for competitors.

Why Issuers Withhold Detail

Reason

Explanation

Technology

The issuing bank's systems may not be configured to return detailed information about declined authorization requests.

Policy

The issuer may decide there is not enough benefit in returning detailed information, so it defaults to generic declines.

Fraud

If the issuer suspects fraud, returning a decline code that indicates fraud could tip off the fraudulent actor.


Find a Declined Payment

Declined payments appear on the Transactions tab in CourtPay with a Failed status.

  1. Select the CourtPay tab, then select Transactions.

  2. Click Status, select Failed, then click Apply.

  3. Click a payment to view its details, including the decline reason. [Confirm: what the payment details show for a declined payment, such as the Stripe decline code or a message]

To export payments, including the decline reason:

  1. On the Transactions tab, click Export.
    ​

  2. In the Export payments window, select a Date range: Today, Current month, Last 7 days, Last month, All, or Custom. If you select Custom, enter a start and end date.

  3. Under Columns, select one of the following:

    • Default (23) - The standard set of columns, including Decline Reason.

    • All (83) - Every available column.

    • Custom - Select the columns you want from the list.

  4. Click Export.

Tip: When exporting declined payments with Custom, include Decline Reason, Seller Message, and Status. For address or security code declines, also include Card AVS Line1 Status, Card AVS Zip Status, and Card CVC Status.


Part 2: Decline Codes and Retry Compatibility

Decline responses fall into four categories based on whether the issuer is likely to approve the transaction on a subsequent attempt.

Category 1: Issuer Will Never Approve

Retry compatibility: Reattempt not allowed. These response codes indicate a permanent or non-recoverable condition. The transaction should not be retried using the same payment details.

Code

Response

04

Pick-up card

07

Pick-up card

41

Pick-up card

43

Stolen card

12

Invalid transaction

14

Invalid account number

15

No such issuer

78

No account

46

Closed account

57

Transaction not permitted

R0

Stop payment order

R1

Revocation of authorization order

Recommended handling: Do not automatically reattempt transactions that receive a Category 1 response. The customer should generally provide a different payment method or resolve the issue with their card issuer before another transaction is attempted.

Category 2: Issuer Cannot Approve at This Time

Retry compatibility: Reattempt allowed. These responses indicate that the issuer is unable to approve the transaction at the moment, but the condition may be temporary.

Code

Response

03

Invalid merchant

51

Insufficient funds

59

Suspected fraud

61

Exceeds withdrawal amount limits

62

Restricted card

65

Exceeds withdrawal frequency

96

System malfunction

N3

Cash service not available

Recommended handling: A future reattempt is permitted. Depending on the decline reason, it may be appropriate to wait before retrying or have the customer contact their issuer. For example, an insufficient-funds response may succeed later after funds become available, while a system malfunction may resolve once the issuer or payment network recovers.

Category 3: Issuer Cannot Approve with These Details

Retry compatibility: Revalidate data prior to reattempt. These responses indicate that the transaction contains payment information that must be reviewed or corrected before it is submitted again.

Code

Response

54

Expired card

55

Incorrect PIN

82

Negative CVV results

N7

Decline for CVV2 failure

Do not immediately retry the same transaction with unchanged information. First, confirm or update the applicable payment details, which may include:

  • Card expiration date

  • PIN

  • CVV / CVV2 security code

  • Updated card information

Recommended handling: Once the payment information has been corrected or revalidated, the transaction may be attempted again.

Category 4: Generic Response Codes

Retry compatibility: Reattempt allowed.

Code

Response

05

Do not honor

Recommended handling: The 05 (Do not honor) response is a generic issuer decline and does not identify a specific reason for the rejection. A reattempt is allowed, although repeated attempts should be handled carefully. If the transaction continues to decline, the customer may need to contact their card issuer or provide another payment method.


Quick Retry Reference

Category

Meaning

Retry Guidance

Category 1

Issuer will never approve

Do not reattempt

Category 2

Issuer cannot approve at this time

Reattempt allowed

Category 3

Issuer cannot approve with the submitted details

Revalidate payment data before reattempting

Category 4

Generic response

Reattempt allowed

Key Takeaways

Before retrying a declined payment, use the response code to determine the appropriate action.

  • Category 1: Stop retry attempts and request another payment method or issuer resolution.

  • Category 2: The condition may be temporary, so a later retry is permitted.

  • Category 3: Correct or confirm the payment information before submitting the transaction again.

  • Category 4: A retry is permitted, but repeated declines may require customer or issuer intervention.

Note: A generic code does not mean the reason is unknown to the issuer. It means the issuer chose not to share it. The cardholder's issuing bank is the only party that can explain a specific decline. Neither the merchant nor the processor has visibility beyond the returned code.

Did this answer your question?