Pause and identify the failure pattern
Do not keep tapping retry without context. A payment can fail for different reasons, and repeated attempts can make it harder to explain the problem to a cashier, bank, hotel, or support desk.
- Note the exact message, the amount, the merchant name, the time, and which card was selected.
- Check whether money actually left the card or appears in Alipay before trying again.
- Ask whether the cashier expects to scan your payment code or wants you to scan the merchant code.
- Move out of the queue or ask staff to hold the order if troubleshooting will take more than a minute.
- If you see a duplicate, pending, or unclear transaction, save the screen before leaving the merchant.
Check network and app state first
Connection problems look like payment problems when the app cannot refresh a QR code, verify the card, or return a confirmation page. Clear this layer before changing cards or identity details.
- Switch between mobile data and Wi-Fi, then reopen the live Alipay payment flow.
- Avoid weak captive Wi-Fi networks if the app cannot reach the confirmation page.
- Confirm your phone clock and region settings are not obviously wrong after a long flight.
- Make sure you can receive bank or Alipay verification messages if the payment triggers a security check.
- If the app is unstable, use a staffed fallback first and update or reinstall only when you are not blocking a purchase.
Confirm the QR direction and payment object
China payment counters may use either flow: the merchant scans your live payment code, or you scan the merchant QR code and approve the amount. The wrong flow can look like a failed account.
- If the cashier has a scanner, open your live payment code and let them scan it.
- If the merchant has a table, wall, receipt, or counter QR code, scan it and confirm the merchant name before paying.
- Do not use old screenshots of payment codes; use the live app flow.
- Confirm you are scanning the payment QR, not a menu, coupon, social account, or mini program entry point.
- If the merchant supports another local wallet better, switch to a staffed card or cash fallback instead of improvising under pressure.
Test amount, merchant, and category limits
Some failures are tied to the amount, merchant setup, product category, deposit, refund path, or ticketing workflow. Isolate that before assuming your Alipay account is broken.
- Ask the merchant to retry a smaller amount if the purchase can be split.
- Try a low-value staffed purchase at another merchant nearby to compare.
- For hotels, rentals, deposits, rail, attractions, and ticket platforms, keep a physical card or staffed counter option ready.
- Do not use the first successful payment as proof that every reservation, mini program, or deposit flow will work.
- If a merchant asks for a different payment channel, confirm the amount and record before paying again.
Check card issuer and bank security prompts
Your card issuer can block a transaction even when Alipay and the merchant are working. This is common around first overseas mobile-wallet transactions, unusual merchant categories, or higher amounts.
- Try a second linked card if you have one.
- Open your bank app or messages and look for fraud, travel, 3-D Secure, or card-control prompts.
- Confirm the card is enabled for overseas, online, contactless, and wallet-style transactions where your bank exposes those controls.
- If the card was just added, test a small staffed payment before using it for a time-sensitive booking.
- If the bank declines the payment, contact the card issuer; the merchant may not be able to fix it locally.
Check identity, phone, and account friction
Identity and phone issues often appear after the first setup step: a higher-risk payment, a new device, a new card, or a reservation flow can ask for more verification.
- Keep your passport name, phone number, and cardholder details consistent where forms request identity information.
- If a prompt asks for verification, do not guess repeatedly; check whether it needs SMS, passport details, bank authentication, or app security.
- Avoid changing phones, phone numbers, or cards during the middle of a payment problem unless you have no other option.
- For attraction, rail, hotel, and event flows, confirm whether the problem is payment or the separate real-name reservation step.
- If the app asks you to contact support, save the error screen, transaction attempt, merchant name, and time.
Use a fallback before the trip gets stuck
Troubleshooting is useful only while it protects the trip. If a payment problem is blocking transport, food, check-in, or an entry window, move to the lowest-friction fallback and debug later.
- Use cash where accepted, especially for small purchases or short taxi situations.
- Use a physical card at hotels, larger stores, airport counters, and staffed ticket offices where supported.
- Ask hotel staff, airport staff, or a staffed attraction counter for the most reliable payment route.
- Switch to another merchant, another ticket channel, or another transport option if the first flow is fragile.
- Keep the failed-payment details so you can compare later without delaying the current task.
Protect refunds, duplicates, and disputes
Payment recovery depends on evidence. The most useful record is usually the in-app transaction or failed-attempt context, not a vague card statement line days later.
- Save successful transactions, failed screens, pending records, merchant names, amounts, and times.
- Keep paper receipts, ticket confirmations, order pages, and reservation IDs until the service is complete.
- If you think you paid twice, ask staff to check before leaving and avoid a third attempt until the record is clear.
- For refunds, keep the original payment route visible; refunds often need to follow the original channel.
- If you must leave, write down the merchant location and staff context while it is fresh.