重复请求防护 是什么意思
如果付款时断线而你又点了一次，具备这项保护的系统会认出这是同一笔请求，不会签发两份配置文件。所以在不确定是否成功时，重试原来那个按钮，比重开一个结账页面更稳妥。
| What actually happened | What you saw | Result without protection | Result with protection |
|---|---|---|---|
- 1
- 2
- 3
- 4
- 5
| What you do | How the system reads it | What follows |
|---|---|---|
优点
缺点
常见问题
Is it really safe to press the pay button twice?+
It is clearly safer than opening a fresh checkout, because a second request from the same screen carries the same identity and is matched to the original intention rather than creating a new one. What is not safe is closing the window and running the whole purchase again, since that reads as a new intention. When unsure, refresh the same page first and check your order history next.
If a card payment fails and I switch methods, will that duplicate?+
It can. A card attempt that looks failed is sometimes an authorisation that completes later. Before switching methods, open your banking app to see whether an amount is held, and check your order history for a new order. If two amounts do appear, send both order numbers together; that is much faster than waiting for the statement.
Will the system notice a duplicate and cancel it for me?+
No, it does not cancel anything automatically, because two purchases in quick succession is normal behaviour for somebody buying for a family or covering two legs of a trip. Guessing your intention risks deleting an order you meant. What the system can do is avoid repeating one request; confirming which order you want has to come from you.
I received two QR codes. Should I install both?+
Do not install both. Pick the one that matches your itinerary, install only that, and leave the other untouched, because a profile that has been installed and used may count as consumed and is much harder to unwind. Then send both order numbers, saying which one you are using. Cancellation terms vary by plan, so we need to look at the actual orders before answering.
If the connection drops mid-payment and I do nothing, what happens?+
There are two possibilities. The request may never have arrived, in which case nothing happened and nothing was charged. Or it arrived and ran to completion, meaning you have a successful order you never saw confirmed. The way to tell them apart is to open your order history and check your email, not to infer anything from the screen that vanished.
Does duplicate protection apply to top-ups as well?+
The same principle applies: resending one request from the same screen should not add the allowance twice. But opening a new top-up page and completing it is still a separate transaction. What makes top-ups more confusing is that the figure shown on the handset can lag behind the network's, so people assume it failed and buy another. Check the order history first, every time.