> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuroncx.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment failed

> Understand payment order statuses in the Transactions Console and learn how to investigate failed payments.

The Transactions Console tracks the payment state of every order raised against a lead. This page covers the `PY_FAILED` status — what it means, how to find affected leads, and how to investigate the exact reason for a payment failure.

## PY\_FAILED

`PY_FAILED` is an order status that flags leads where a payment was initiated but did not complete. Common reasons include an invalid card number, an expired card, or a gateway-level rejection.

### Step 1 — Filter by PY\_FAILED in the Transactions Console

**Dashboard → Transactions → Orders filter → PY\_FAILED → Apply Filter**

1. Go to **Transactions** from the left navigation.
2. In the filter bar, click **5 Orders** to expand the order status options.
3. Select **PY\_FAILED**, then click **Apply Filter**.
4. The console now shows only leads where a payment attempt has failed.

***

### Step 2 — Investigate the failure

There are two ways to check why a payment failed for a specific lead.

#### Method 1 — Orders tab

1. Click the **expand icon (⤢)** to the left of the lead name to open the Lead Detail View.
2. Click the **Orders** tab at the top of the detail panel.
3. Under **Payment for Order #XXXXXX**, expand the **FAILED** entry.
4. The **Fail Reason** field shows the exact error returned by the payment gateway.

![Method 1](https://mintcdn.com/neuroncx/eH1ugRouNCsWV9NB/images/method-1.png?fit=max\&auto=format\&n=eH1ugRouNCsWV9NB\&q=85\&s=7af6b0c7375d59826dd702aaa4aa2711)

#### Method 2 — Activity Log

1. Click the **arrow (→)** to the right of the lead name in the Transactions Console.
2. This opens the Activity panel.
3. Click the **Activity Type** dropdown and select **Payments**.
4. The log shows the complete payment sequence in chronological order: `INITIATED` → `LINKGENERATED` → `FAILED`, with the failure reason and gateway details inline.

> [!NOTE]
>
> The Activity Log also captures any discount adjustments applied before the payment attempt, and the exact gateway used (e.g. Razorpay). This is useful context when escalating a payment issue to your finance or tech team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.