Discover · Authorization

Discover Reason Code DA: Declined Authorization

Updated November 6, 2026 · Part of the Discover reason code guide

Discover reason code DA applies when the issuer declined authorization for a transaction but the merchant processed it anyway. Forced sales and captures tied to the wrong authorization are the usual causes. To win, show the transaction you settled was backed by a valid approval code for that card, amount and date.

What Discover reason code DA means

DA is an authorization code. The issuer declined the authorization request, but the transaction was settled anyway. Since the issuer explicitly refused the charge, it sends it back.

DA is usually raised by the issuer, not the cardholder. Cardholders often don’t know an authorization was declined at all.

Common causes

  • A sale forced through after a decline, for example by entering a manual or “voice” authorization code
  • Subscription billing logic that captures against a declined attempt instead of a fresh approval
  • A gateway that settled a transaction tied to a failed authorization because of a configuration error
  • Staff overriding a decline at the point of sale

Evidence that wins a DA dispute

  1. Approval for the settled transaction: the approval code, masked card number, amount and date of the authorization that backs the transaction you actually settled.
  2. Authorization history: if there were declines followed by an approval, the full sequence, showing which attempt was approved and that the settlement matches it.
  3. Matching amounts: proof that the settled amount doesn’t exceed the approved amount.

If you can’t produce an approval that matches the settled transaction, there is very little to argue.

How to prevent DA chargebacks

  • Never force a sale after a decline. Ask the customer for another payment method instead.
  • In subscription billing, make sure every capture references an approved authorization, and follow your processor’s guidance on how often and how many times to retry.
  • Remove manual authorization-code entry from staff permissions unless you truly need it.
  • Audit your gateway settings so declined authorizations can’t be captured.

Should you fight or accept?

Fight when the settled transaction is backed by a valid approval, for example a successful retry after an earlier decline, and the records show the link clearly.

Accept when the transaction was settled on a declined authorization. The issuer refused the charge, so the dispute is valid. Fix the process that let it through, because repeated DA disputes point to a systemic billing problem.

Frequently asked questions

What is Discover reason code DA?
Discover reason code DA, Declined Authorization, is an authorization chargeback raised when the issuer declined the authorization request, but the merchant still submitted the transaction for settlement.
How do I win a Discover DA chargeback?
Show the settled transaction was linked to an approved authorization: the approval code, card number (masked), amount and date. If a retry was approved after an earlier decline, show the approval belongs to the transaction you settled.
Can retrying a declined subscription payment cause DA chargebacks?
Retrying is normal, but each retry must get its own approval before you capture. Settling a charge against a declined attempt, or retrying too aggressively, can create DA disputes and network compliance issues. Follow your processor's retry guidance.

Related reason codes

Browse every Visa, Mastercard, Amex and Discover reason code →