ECP Status declined: Declined
Transaction was declined by the schemes or risk management.
What it means
The ECP declined status indicates that a transaction authorization was rejected either by the payment card schemes or by a risk management system. This status represents an unsuccessful transaction where authorization was not granted by downstream processing networks or security filters.
Classification & retryability
Do not retry immediately without evaluating the source of the decline. If the decline originated from an automated risk system, verify order legitimacy first. If rejected by the card scheme, request an alternative payment method or prompt the customer to verify details before re-attempting.
Common causes
- The card scheme or issuing bank rejected the authorization request due to security controls, limits, or account restrictions.
- An internal or gateway-level risk management rule flagged the transaction as high risk or potentially fraudulent.
- Card verification parameters, such as CVV or address details, failed scheme-level validation checks.
How to resolve it
Examine transaction telemetry and response sub-codes to determine whether the rejection was triggered by risk filters or by the card scheme. If risk controls blocked the transaction, evaluate the risk score and rule criteria. If the scheme rejected the request, guide the customer to use an alternative card or contact their issuer.
For merchants
Review risk scoring logs to confirm whether the decline was caused by overly strict fraud rules, and adjust threshold parameters if false positives occur. For scheme rejections, present clear messaging at checkout prompting the customer to select another payment method.
For customers
Verify that all card details and billing addresses were entered correctly, contact the card issuer to authorize the transaction, or provide an alternative payment method.