Do not debug in the queue
Step aside first. Payment errors become harder when the traveler feels watched, tired, or rushed.
Payment decision tree
Use this when a wallet, QR code, card, mini-program, or network layer fails at the exact moment you need to pay. The goal is not to explain every error; it is to choose the next calm move.
Quick answer
Step aside, identify the payment flow, change one layer at a time, and stop repeating the same failed action. Try a different QR mode, stable mobile data, a second wallet or card, then a human fallback such as cash, staffed counter, larger merchant card terminal, hotel desk, or support contact.
Read the full payment guideApplies to
Foreign visitors using Alipay, Weixin Pay, QR menus, taxis, metro counters, attraction tickets, Didi, mini-programs, foreign-issued cards, hotel Wi-Fi, VPN, and mobile data in mainland China.
Check boundary
Wallet screens, supported foreign cards, transaction limits, identity prompts, and merchant acceptance can change. Use this as a fallback sequence, then confirm live rules in the official wallet or with the merchant.
Review date: 2026-05-23
Interactive tool
Rules
The first win is to reduce pressure. Once the current purchase is handled, solve the wallet problem away from the counter.
Step aside first. Payment errors become harder when the traveler feels watched, tired, or rushed.
Try a different QR mode, then network, then wallet or card. Repeating the same attempt is usually noise.
A personal transfer QR is not the same as a shop checkout QR. Ask for a merchant QR or staffed checkout.
Cash, a larger merchant card terminal, a ticket counter, taxi queue, hotel desk, or support contact can rescue the moment.
Quick answers
Short answers for the exact moments where travelers usually lose time.
Step aside, then switch payment mode before changing everything else. If you scanned a QR, try showing your payment code; if the cashier scanned you, ask for the merchant QR. Then check mobile data, wallet choice, card choice, and cash or staffed-counter fallback.
Yes. The decision tree is built around the payment situation rather than one brand. It can help with Alipay, Weixin Pay, merchant QR codes, cashier scan flows, in-app payments, network failures, and foreign-card risk checks.
Merchant QR checkout and personal transfer QR are different flows. Foreign-card wallet paths are more likely to work in merchant checkout contexts, while personal transfer codes may be unsupported or blocked for visitors.
No. One calm retry after changing a layer is reasonable, but repeated attempts can waste time or trigger more risk checks. Switch wallet, card, network, staffed counter, cash, hotel help, or a different purchase path.
Understand merchant QR, personal QR, bank checks, network problems, and wallet fallback.
Open guidePayment failures often hide a data, VPN, Wi-Fi, or SMS problem.
Check phone setupSave the wallet, card, cash, hotel, and first-night fallback stack before boarding.
Save checklistNext move
Read enough to make the decision smaller, then open the checklist, search a specific question, choose a setup tool, or share the page with the person planning with you.
Use the checklist when the question has shifted from research to preparation.
Search by the actual problem: Alipay, eSIM, transit visa, first transfer, vegetarian food, or a city name.
Open recommendations when the task is clear enough for a short list to be useful.