Decision Explorer

—

The payment attempt for order_TYU1KxLy0t3ORx failed due to a gateway BAD_REQUEST_ERROR with unknown reason. The customer has a history of both successful and failed payments of the same amount on the same day, indicating a transient or card‑specific issue rather than a systemic problem.

—

The payment for order_TYTo6fkDdClzgE failed due to a gateway error (BAD_REQUEST_ERROR) during authorization, likely a card decline or temporary issue. The customer has a history of mixed success with similar payments, indicating the card may be problematic.

The payment for order_TYTRFNKSbpvSX1 failed due to a BAD_REQUEST_ERROR with unknown reason, similar to recent failures on this customer's other attempted orders. The customer's card appears to be declined intermittently, while other cards have succeeded. Recommend prompting the customer to retry using a recovery link, possibly with an alternative payment method.

—

Payment authorization failed due to transient gateway error; customer has successful captures on other orders, so retry is viable.

—

—

—

—

—

The payment for order_TY7ZJFtR61VKrm failed due to an unknown gateway error (BAD_REQUEST_ERROR). Similar failures occurred for other 29900 INR orders, suggesting intermittent card or gateway issues rather than a systemic problem.

Single payment attempt failed with a generic BAD_REQUEST_ERROR; no recurring issues in customer's payment history.

Payment attempt failed due to unknown gateway error; order remains unclaimed.

The payment attempts for order rcpt_00493 failed due to insufficient funds in the customer's account. No successful capture exists yet.

All payment attempts for case 488 have failed due to insufficient funds in the customer's account.

All three UPI payment attempts for order ntOF1EKcIEFqcL failed due to gateway timeouts, indicating a transient processing issue rather than customer error. No authorization exists, so payment cannot be captured.

The payment for order HTAfTy7lMFxGzx failed due to a gateway timeout (transient error). Customer has successfully completed subsequent payments, indicating ability to pay.

The payment failed due to a transient gateway timeout, not due to customer error or fraud. The customer has a strong history of successful payments.

Payment was authorized but not captured; order remains in attempted state.

All payment attempts failed due to insufficient funds; no authorized amount exists to capture.

All payment attempts for order order_WiJVdumuc58BS2 have failed due to insufficient funds in the customer's account.

Payment failed due to insufficient funds in the customer's UPI account.

Payment failed due to temporary issuing bank unavailability (GATEWAY_ERROR). No authorization exists to capture.

All payment attempts for order 505 failed due to repeated gateway timeout errors, indicating a technical issue with the payment gateway rather than customer error.

The payment attempt for order_xs6iGx2DvCgOVJ failed due to an issuing bank unavailability (GATEWAY_ERROR). No other attempts have been made, and the customer successfully paid another order later via UPI, indicating the issue is temporary and specific to the card used.

The payment for order_fcd81gFZayixxe failed due to a gateway timeout, not a customer card issue.

The order was initially declined due to a gateway timeout, but the payment was later successfully captured, and the order status is paid.

Both payment attempts failed due to customer not completing OTP authentication (otp_not_entered). No successful capture exists.

The payment for order DpDOshCoiD7Vkz failed due to issuer bank unavailability, a transient gateway error, not a customer fault.

The payment for order rcpt_00385 failed because the customer's card used for the EMI payment has expired.

The sole payment attempt for order rcpt_00395 failed due to a gateway error (issuer bank unavailable). No successful payment exists.

The payment for order order_19hl9S6jbyKBIo failed due to a temporary issuer (bank) unavailability (GATEWAY_ERROR). The customer has a strong history of successful payments via multiple methods, indicating the issue is likely transient.

Payment was authorized but not captured; order remains in attempted status.

The payment failed because the customer's card is blocked by the issuing bank. A recovery link should be sent to allow the customer to complete the transaction using an alternative payment method (like UPI or another card).

The customer failed to complete payment authentication because the OTP was not entered in time.

The payment failed because the OTP was not entered in time (OTP timeout) during both attempts.

The payment failed due to a transient gateway timeout (GATEWAY_ERROR) during authorization. Since there are no other payment attempts, sending a recovery link is recommended to allow the customer to retry.

The payment failed because the customer did not enter the OTP in time (otp_not_entered during payment authentication). Since the customer has a good payment history and no other payment was captured or attempted for this order, a recovery link should be sent.

Payment failed due to insufficient funds in the customer's account during a UPI transaction.

The payment failed due to a gateway timeout on a Netbanking transaction. No other payment attempts have been made for this order.

The payment failed because the card used by the customer had expired. Since this is a customer-side issue, sending a recovery link to allow them to complete the payment with an active card or alternative payment method (like UPI) is the best action.

The payment failed because the customer's card had expired. The order remains unpaid, and since the customer has successfully paid other orders using alternative payment methods (wallet and netbanking), sending a recovery link is the best action.

The last payment attempt failed due to a transient gateway timeout during netbanking authorization. Sending a recovery link is recommended to allow the customer to retry the payment.

The payment attempt failed due to a gateway timeout during UPI payment authorization.

Payment failed because the card used by the customer has expired.

The order has been successfully paid and the payment captured.

The payment failed due to a gateway timeout during the card authorization step. Since the customer is active and has successfully completed other orders, we should send a recovery link to help them complete this unpaid order.

The card payment attempt failed due to a gateway timeout. This is a recurring pattern for this customer who typically retries and successfully completes payments using alternative attempts.

The payment attempts for case 582 (order order_kwLzHMYlr5NUeK) failed due to customer-side 'insufficient funds' on both card and UPI. No successful payment has been recorded for this order, though the customer has a history of successful purchases.

The payment attempt (pay_lq1K8MZXOg94Kn) for the order (order_8HV0G9mig3qMST) was successfully authorized on 2026-05-18T15:15:00.000Z but has not yet been captured.

The payment failed because the customer did not enter the OTP in time during the payment authentication step for both attempts.

—

Payment failed due to insufficient funds in the customer's account; pattern repeats across multiple orders.

The payment was authorized but not captured; the capture window has expired.

The order was initially failed via netbanking due to a gateway timeout, but a subsequent card payment was successfully captured, and the order status is 'paid'. No further recovery is needed.

Payment failed due to insufficient funds in the customer's account.

Both payment attempts for case 568 failed due to customer not completing OTP authentication, indicating a customer‑side issue rather than a technical error.

Payment attempt failed due to insufficient funds; no authorized amount to capture.

All payment attempts for order rcpt_00073 failed due to repeated gateway timeout errors, indicating a persistent processing issue rather than insufficient funds or card decline.

Both payment attempts for case 565 failed due to the customer not completing OTP authentication, leaving the order unpaid.

Both payment attempts for case 564 failed due to the customer not completing OTP authentication, resulting in no successful authorization.

The payment failed due to the customer not completing OTP authentication. The customer also has a history of card blocks on previous attempts, indicating the current card may be problematic.

The payment failed due to the issuing bank's risk checks blocking the UPI transaction. The customer has a history of successful payments via card and UPI, and no fraud indicators.

Both payment attempts for order 299.00 INR failed due to insufficient funds in the customer's UPI account. No authorization was obtained, so capture is not possible. The customer later completed a payment successfully, indicating funds are now available.

All payment attempts for case 560 have failed due to insufficient funds; no successful authorization exists.

Both recent payment attempts for order rcpt_00136 failed due to bank risk checks blocking the transaction. The customer's account is otherwise healthy with successful prior and subsequent payments via different methods, indicating the issue is method‑specific or a temporary risk flag.

Payment failed due to customer's card being blocked by issuing bank.

Payment failed due to a gateway timeout; no authorization captured, but customer has a good payment history.

The payment for order_ZZgMMiApDXxSNd failed due to insufficient funds. The customer subsequently completed a smaller purchase, indicating they now have sufficient balance. A recovery link to retry the payment is appropriate.

Payment for order order_xnzEEI9OI0VfBP was successfully captured on the second attempt; the order is already marked as paid.

Payment failed because the customer did not complete OTP verification during card authentication.

The latest payment attempt for order rcpt_00195 failed due to insufficient funds in the customer's bank account. The customer has a pattern of recent payment failures (insufficient funds, card issues, OTP timeout), indicating they may not have sufficient balance or are encountering payment method problems.

Payment failed because the customer's saved card had expired, causing the only attempted authorization to be rejected.

Payment failed due to customer not completing OTP verification.

The single payment attempt for order rcpt_00092 (₹4,999) failed due to a risk block from the issuing bank during authorization.

Payment failed because the customer did not complete OTP verification.

Payment already captured; no recovery needed.

Payment failed due to issuing bank being unavailable; customer has a strong history of successful payments.

Payment failed because the customer's card is blocked by their issuing bank; the card cannot be authorized for this order.

—

The payment for order BOJJ44hg1mvdef failed due to a transient gateway timeout, not a customer-side issue.

The payment attempt failed due to a risk block from the issuing bank on the UPI transaction. The customer has a history of successful payments using other methods (netbanking, card) and similar amounts, indicating the issue is specific to this UPI attempt.

Payment failed due to a gateway timeout during authorization; no capture was made.

The payment for order rcpt_00125 failed due to a gateway timeout, not a customer or card issue. The customer has a clean payment history and previous similar gateway timeout was resolved by a retry.

Payment failed due to customer not entering OTP during authentication

The payment for order rcpt_00297 failed because the issuing bank blocked the transaction during risk checks.

Payment failed because the customer did not complete OTP verification during card authentication.

The payment for order rcpt_00090 failed because the customer did not complete the OTP authentication step.

The payment attempt failed due to a risk block by the issuing bank on the UPI transaction. The customer has a clean payment history with successful transactions on other methods, indicating no fraud risk.

The payment attempt for order rcpt_00475 failed due to insufficient funds on the customer's card. The customer has a history of successful payments via other methods, indicating they can complete the purchase.

The payment for order rcpt_00431 (₹4,999) failed because the customer did not complete the OTP authentication step.

The payment failed because the customer's card is blocked by the issuing bank, and no successful authorization exists for this order.

—

—

The customer's EMI payment attempts failed repeatedly because the card they used is blocked by the issuing bank. However, the customer remains active and has successfully completed other recent payments using a different card and UPI.

The single payment attempt failed due to a gateway timeout. The customer has since completed other purchases successfully, showing they are active and reliable, so sending a recovery link is recommended.

The customer's UPI payments failed repeatedly due to insufficient funds. Since they have a history of successful purchases using Netbanking, sending a recovery link will allow them to choose a different payment method.

The payment failed because the OTP was not entered in time by the customer during payment authentication. Since the customer is still active and has since completed other orders, sending a recovery link to complete this high-value payment is recommended.

The payment attempt for recovery case 535 (order_DDQo6XmrO1NMVi) is in an 'authorized' state but has not been captured. We can safely capture this payment to complete the order.

The customer's payment failed because they did not enter the OTP in time during card authentication. Since they are a returning customer with multiple successful previous orders, sending a recovery link is the best next step to let them retry.

The payment failed due to insufficient funds in the customer's account during a netbanking payment attempt.

All payment attempts for the order failed due to insufficient funds in the customer's account.

The customer's payment attempt failed because the card used had expired. The order remains unpaid with no other attempts.

The customer's payments for order order_BlYPvXQrZmpzof failed 5 times due to insufficient funds on their card. They have since made other successful payments using Netbanking, EMI, and UPI, indicating they have alternative payment methods available.

The payment attempt for order_XdMIuOgKIDdfMr failed due to a UPI gateway timeout during the authorization step. No other payment attempts were made, and the order remains unpaid.

The payment for this order is authorized but has not yet been captured.

Both payment attempts for the order failed because the customer did not enter the OTP within the required time limit (OTP timeout).

The payment failed because the customer did not enter the OTP in time during both the card and netbanking payment authentication attempts. The order remains unpaid.

The customer's payment for order_QsgY67vun26VzS failed due to insufficient funds, but they successfully placed and paid for a duplicate order of the exact same amount (order_yzyA3x5LN2KnYm) the next day.

The payment has already been successfully recovered and captured via UPI.

Payment failed because the customer's card was expired.

The customer failed to complete the payment for order_mSYYQLwd0zKlM9 because the OTP was not entered in time. They subsequently created a new order, order_DpRLPGjPT9yEQK, for the same amount (INR 299) two days later and successfully completed the payment. Recovery should be stopped as this is a duplicate order.

The payment for high-value order order_QjL6fOXUGYlJUD failed because the customer's card was blocked by the issuing bank. The customer is active and has successfully completed other purchases before and after this attempt using UPI and other methods.

The payment failed due to a gateway timeout on the only attempt. The customer has subsequently placed other orders, but this specific 599 INR order remains unpaid.

The payment failed due to insufficient funds in the customer's account during a UPI transaction. Sending a recovery link will allow the customer to retry the payment using another method or after adding funds to their account.

Payment failed because the customer did not complete the authentication step (OTP not entered in time).

Payment failed due to an expired card. This card was also used in a later order, which failed with the same error.

The payment for order_LzKcwcg7tzIiAx failed due to a gateway timeout during the payment authorization step.

Payment failed due to gateway timeout during UPI payment authorization. No authorized transaction exists to capture.

The customer initiated an order for INR 599.00, but the sole payment attempt failed because the OTP was not entered in time during the authentication step. No authorized payment exists to capture.

—

Payment failed due to temporary issuer unavailability (gateway error).

Payment failed due to temporary issuing bank unavailability; no authorization exists to capture.

Payment failed due to the issuing bank being unavailable (GATEWAY_ERROR). This issue has occurred on multiple recent attempts, indicating a likely temporary bank outage or problem with the customer's card.

Payment failed due to issuing bank being unavailable (gateway error) for the latest attempt.

Payment failed because the customer's card on file has expired.

The payment for order rcpt_00284 failed because the customer's card is blocked by the issuing bank, making a capture impossible.

The payment for order 0bmOauoqgA858z failed because the customer did not complete the OTP verification, a customer‑side error. The customer has a history of successful payments, indicating the issue is not systemic.

Payment attempts for order rcpt_00313 failed due to insufficient funds in the customer's account.

Payment failed due to insufficient funds in the customer's UPI account; no authorization exists to capture.

Both payment attempts for case 460 failed due to insufficient funds in the customer's account.

The payment for order rcpt_00448 was authorized via UPI on 2026-03-26 but was never captured; the authorization window has likely expired, so capture is not possible.

All payment attempts for order rcpt_00091 (₹599.00) have failed due to insufficient funds in the customer's account.

The sole payment attempt for order rcpt_00317 failed due to a gateway timeout (GATEWAY_ERROR). No other attempts or successful payments exist for this customer.

Payment attempt for order rcpt_00087 failed due to a gateway timeout, resulting in no authorization and no captured funds.

Payment was successfully captured via UPI on 2026-05-29 after an initial card OTP failure.

Payment attempts failed due to insufficient funds in the customer's bank account.

The payment attempt failed due to a gateway timeout, indicating a transient processing issue rather than a customer or card problem.

Both payment attempts for order rcpt_00302 failed due to insufficient funds in the customer's account.

The payment for order_JUj7Gia1OjsVnz failed due to a gateway timeout during authorization. The customer has a history of successful payments after similar gateway errors, indicating the issue is transient and not due to insufficient funds or customer error.

Customer failed to complete OTP authentication on both payment attempts, resulting in payment failures.

Transient gateway timeout caused payment failure; payment not captured

Both payment attempts failed due to insufficient funds in the customer's UPI account; no successful authorization exists.

Payment failed due to insufficient funds in the customer's wallet.

Payment failed due to a gateway timeout during authorization; no customer fault detected.

Payment failed due to customer not completing OTP authentication on a card payment.

The payment attempt for order order_sOmDgggz4yvc5J failed due to insufficient funds in the customer's account.

All payment attempts for case 440 failed due to customer not completing OTP authentication; no authorized payment exists.

The payment failed due to a gateway timeout during authorization, indicating a transient processing issue rather than customer error.

Payment failed because the customer's card on file is expired.

All payment attempts for case 437 failed due to insufficient funds in the customer's account.

Both payment attempts for order 9Y8j8hqZnBLxrx failed because the customer did not enter the OTP in time, resulting in no successful capture.

Payment failed due to card being blocked by the issuing bank.

All payment attempts for case 434 failed due to insufficient funds in the customer's account.

Payment failed because the customer's card is blocked by the issuing bank.

The payment attempt for order rcpt_00164 failed due to a gateway timeout during UPI authorization. No authorization was obtained, so the payment cannot be captured.

The payment failed due to a bank risk block on the UPI attempt. Customer has a history of successful payments, including the same amount via card, indicating sufficient funds and no systemic issue.

Payment failed due to transient gateway timeout; customer not at fault.

The payment failed twice due to the customer not entering the OTP during authentication. The customer has a history of successful payments, indicating the issue is not with the card or gateway.

The payment for order 4999.00 INR failed due to a gateway timeout during authorization, not a customer-side issue. The customer’s card works on other orders, indicating a transient processing problem.

The payment for order_6Stjq0MtcoDMVR was successfully authorized but not yet captured.

Payment failed due to gateway timeout errors; no authorization was obtained, and the order remains in attempted state.

The payment for order_xTHQDKlQulQhMM failed because the customer's card has expired. The customer has a history of successful payments but recent attempts on other orders also failed due to card problems (expired, blocked, insufficient funds), indicating the need for a new payment method.

Both payment attempts for the order failed because the customer did not complete the OTP authentication step.

Payment attempts failed due to insufficient funds in customer's account.

Payment failures for both recent attempts are due to insufficient funds in the customer's account.

All payment attempts for order rcpt_00216 failed due to insufficient funds in the customer's UPI account.

The order was initially attempted with a wallet payment that failed due to a gateway timeout, but a subsequent EMI payment was successfully captured, resulting in the order being paid.

Payment failed due to a gateway timeout during authorization; the customer's card was not charged.

Both payment attempts failed due to customer not completing OTP verification.

Payment failed due to insufficient funds; customer can retry once funds are available

Payment failed due to insufficient funds in the customer's account.

The payment for order_uzYr9TqxOlVG0Q failed due to a transient gateway timeout, not due to customer-side issues.

The payment failed due to an expired card, a customer-side issue. The customer has demonstrated ability to pay using another method (UPI) on a subsequent order.

Both payment attempts for order rcpt_00456 failed due to the customer not entering the OTP in time, a customer‑side error.

The payment failed due to the customer not completing OTP authentication, a customer‑side issue, and the customer has a history of successful captures on other orders.

The payment for order_ZMws2rHsBJTjT2 failed due to a gateway timeout (GATEWAY_ERROR). The customer's payment method has successfully processed other transactions, indicating the issue is likely a transient gateway problem.

Payment failed because the customer did not complete OTP verification, a customer‑side error.

Customer failed to complete OTP verification on two payment attempts, causing payment to remain uncollected.

Customer failed to complete OTP verification for both payment attempts, resulting in payment failures.

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—

—