# gateway.fraud.security_violation

> For the complete machine-readable documentation index, see [llms.txt](https://apidocs.chargebee.com/llms.txt).


**gateway**

The payment was declined due to a security violation detected by the payment gateway or processor. This happens when there is unauthorized system access, use of compromised API credentials, non-compliance with security policies, or suspicious payment method activity.

## Recommended Customer Message

We are unable to complete your request due to a technical issue. For assistance, please contact our support team.

## Root Cause[](#root-cause)

-   **Unauthorized system access detected:** Unusual login attempts, IP anomalies, or compromised credentials suggest a security breach.
-   **Compromised API keys or tokens:** Insecure or leaked authentication credentials were detected during the transaction attempt.
-   **Security policy violation:** Non-compliance with required encryption standards, tokenization, or API security guidelines triggered the violation.
-   **Fraudulent payment method detected:** The bank or payment processor identified inconsistencies or suspicious details in the payment method.

## Troubleshooting and Solutions[](#troubleshooting-and-solutions)

-   Review and rotate your API keys, tokens, and payment gateway credentials if a compromise is suspected.
-   Immediately suspend or lock affected accounts and payment processing until the issue is investigated.
-   Notify internal security teams to analyze logs, trace unauthorized access, and assess potential data breaches.
-   Collaborate with your payment gateway provider to identify and resolve any vulnerabilities and ensure compliance with security protocols.
-   Advise the customer to change their account passwords and enable additional security measures, such as multi-factor authentication.