Closed
Bug 887996
Opened 12 years ago
Closed 12 years ago
Inform user when Bango purchase POST gets aborted
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: kumar, Assigned: keir)
Details
STR
- open Marketplace dev
- search for :paid
- purchase an app
- create/confirm PIN
- confirm mobile number via SMS (if necessary)
- on purchase confirmation page, get ready to click buy
- make a phone call to the device you are using to pay from
- *before* the phone call is received, click the final buy button on Bango's page so that when the request begins the phone call interrupts it
Expected: in the scenario that the POST is aborted, Bango should show a message saying "you have not been charged, try again"
Actual: you see the same purchase confirmation page but there is no user message
Note how this is one of many scenarios. This bug is only for when the POST does *not* go through. Bango should be able to detect this by checking if the request was aborted via Ajax.
If the POST does go through, we can handle that scenario ok with package-configured event notices (see bug 865612)
| Reporter | ||
Updated•12 years ago
|
Assignee: nobody → keir
Priority: -- → P3
| Reporter | ||
Comment 1•12 years ago
|
||
Note that Bango's work on bug 845528 should prevent duplicate payments, we just want to inform the user better.
Updated•12 years ago
|
Version: 1.0 → 1.3
Updated•12 years ago
|
Version: 1.3 → 1.4
This cannot be implemented because once a POST is fired to charge the user we have no way to stop and guarantee that the user has not been charged.
| Reporter | ||
Comment 3•12 years ago
|
||
Ah, yes, in re-reading the bug I think you are correct. Even if you catch the XHR abort event it wouldn't be very meaningful.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•