Closed
Bug 845528
Opened 11 years ago
Closed 11 years ago
Prevent duplicate purchases (Bango)
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kumar, Assigned: keir)
References
Details
We'd like to prevent duplicate purchases. Currently, you can do this: - pay for an app - copy/paste the billing config URL, such as http://mozilla.test.bango.org/mozpayments/?bcid=220020 - pay for it again Can Bango prevent this since the billing config ID should be marked as "paid" somehow? Alternatively, we already pass in our externalTransactionId to the BillingConfigAPI. Would it be preferable for Bango to detect already-paid transaction IDs are stop duplicate payments that way?
Reporter | ||
Updated•11 years ago
|
Comment 1•11 years ago
|
||
Tom says this needs input from Keir.
Assignee | ||
Comment 2•11 years ago
|
||
Hi - back now! Quick question - what is the expected behaviour when the user hits a billing config id thats already been paid? Same as the first time (ie redirect to the success url)?
Reporter | ||
Comment 3•11 years ago
|
||
Hi Keir, welcome back! As discussed on a call, Bango will check for the externalTransactionId and either replay the transaction or throw an exception, whatever is the easier approach. We thought that replaying the transaction (success/error) would be easy enough. The crucial fix is to not let a customer pay twice.
Assignee | ||
Comment 4•11 years ago
|
||
(In reply to Kumar McMillan [:kumar] from comment #3) > As discussed on a call, Bango will check for the externalTransactionId and > either replay the transaction or throw an exception, whatever is the easier > approach. We thought that replaying the transaction (success/error) would be > easy enough. > > The crucial fix is to not let a customer pay twice. Just to confirm we'll check for a previous transactions on a billing configuration id or a externalTransactionId?
Reporter | ||
Comment 5•11 years ago
|
||
We use externalTransactionId in our session so if you could detect duplicates on that, it would be the easiest. This value will always be unique for new transactions.
Comment 6•11 years ago
|
||
in Bango test environment
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee: tom → keir
You need to log in
before you can comment on or make changes to this bug.
Description
•