Getting started

Amazon Pay not working at checkout: causes and a safe way to retry

Amazon Pay not working at checkout? Separate balance, UPI and card problems, avoid paying twice and check your statement before you retry an order.

Editorial illustration for Amazon Pay not working at checkout: causes and a safe way to retry

When Amazon Pay will not work at checkout, the cause is usually the payment source behind it, not the button itself: a balance that is short, a UPI or card step that timed out, or a bank that declined the request. Before you retry, check whether any money left your account, so you do not pay twice for the same order.

What are you trying to pay with?

Name the source, because each fails in a different way. A stored balance can be too low for the order. A UPI payment depends on your bank and your phone's connection. A card payment may need an extra approval step that did not complete. The seller's own help page explains the options available to you; we will not describe their menus.

SourceTypical failureFirst check
Stored balanceBalance lower than the order totalCompare the balance with the total
UPITimeout or bank busyYour bank app for a debit or pending entry
CardApproval step not completedSMS or app prompt from the issuer, and card limits
Mixed paymentOne part succeeded, one failedBoth the order status and the statement

Is my order placed or not?

Do not trust the checkout screen alone. Open the order list in your own account and see if the order exists, then open your bank statement for a matching debit. Four combinations are possible: order and debit, order and no debit yet, debit and no order, or neither. Only the third needs a refund request, and it often resolves on its own within the time the seller states.

A worked example with made-up numbers

Say an order is ₹2,499. You use ₹500 from a stored balance and ₹1,999 by UPI. The screen freezes after you approve the UPI request. Your bank shows a ₹1,999 debit, but the order list shows nothing. Total at stake: ₹1,999 for the UPI part, plus whether the ₹500 was also taken. Check the balance entry too. Write down the time, both amounts and the references, and wait for the stated reversal period before you place the order again.

What should I never do?

  • Tap pay again and again, which can create several debits.
  • Follow a link from a caller or message offering to fix the payment.
  • Read out a one-time code to anyone.
  • Delete the app before you have saved the order and payment references.

How do I keep a record of failed payments?

Keep a short log with date, amount, source and outcome. When you import your statement into SpendixAI, a debit that lacks an order stands out, and the Possible duplicate charges report lists the same amount to the same merchant within two days. You then match the statement against your order list yourself.

How do I avoid the problem next time?

  • Keep a payment method with a healthy balance or limit ready as a backup.
  • Check that your phone has a stable connection before you start a payment.
  • Do not switch apps midway through an approval.
  • Save the order confirmation as soon as it appears.

For large orders, say above ₹10,000, consider doing the payment on a steady Wi-Fi connection and checking your bank immediately afterwards, so any problem is caught the same day.

When do I contact support?

Contact the seller if a debit has no order after the period they mention, and contact your bank if the seller says they never received it. Quote the dates, amounts and references, ask for a complaint number, and keep screenshots until the credit appears on your statement.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports