Get started Sign in — website account Sign in — online store account
  1. Online store builder
  2. Troubleshooting
  3. Payment gateway errors

Payment gateway errors

Customers' online payments failing, paid orders stuck on Pending, keys refused, test badges on live checkout — causes and fixes for every gateway.

Updated 2 min read Markdown

"The payment could not be started. Please try another method."#

The gateway refused to open a payment. Almost always the keys:

  • The keys are wrong, incomplete, or have a space at the start or end. Paste them again.
  • Environment does not match the keys: test keys with Live, or live keys with Test / sandbox.
  • The gateway has not activated your live account yet, or has suspended it — check your gateway dashboard.
  • Paytm: Website is still WEBSTAGING with live keys.
  • PayU: the salt is not the v1 salt matching the key.
  • CCAvenue: the working key was generated for a different domain, or regenerated since you saved it.

Switch the method to Admins only, fix the keys, and test again.

"That payment method is no longer available." / "That payment method is not available."#

The method was switched off or removed while the customer was checking out, or its rules no longer allow this order. Ask them to choose another method.

The customer paid, but your store never heard about it — usually because they closed the window before returning to your store.

  • Add the webhook in your gateway's dashboard (Razorpay, PhonePe, Cashfree, Stripe, PayPal): copy the Webhook / callback URL from the method in your admin, and enter the matching secret. See the guide for your gateway.
  • Check the payment in the gateway's dashboard. If it is captured, set the order to Confirmed by hand; note that its payment status stays Pending.

A "Test" badge on checkout#

The method's Environment is Test / sandbox. Customers paying with real cards will fail. Switch to Live with live keys.

Customers see a gateway error page#

The message on the gateway's page is the gateway's own — card declined, bank server down, transaction limit exceeded. These are between the customer and their bank; suggest another card, UPI, or another method.

"Fill in every required credential before switching this on."#

Some required keys are empty. Each gateway's required fields are marked with *****.

Refund failed#

Gateway refund failed; recorded as a manual refund for you to settle. — the gateway refused the refund (for example, too long after the payment, or insufficient balance). Pay the customer yourself and record the UTR. See Refunds and store credit.

Was this page helpful?

Something is missing — tell us