Closed Bug 916191 Opened 12 years ago Closed 9 years ago

Provide detailed postback failure reason to developer

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Product:
Marketplace Graveyard
Component:
Payments/Refunds
Version:
Avenir
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: kumar, Unassigned)

Details

WebPay sends postback failures to Marketplace via this API call: https://github.com/mozilla/webpay/blob/f80b61db00572925d79241055a06c9b59e241092/webpay/pay/utils.py#L113-L115 Let's add in a reason so that the API captures why the postback failed. As of bug 838885 we'll have a couple different types of failures: * postback didn't respond with transaction ID * connection failure * bad status: 500, 404, etc This diagnostic info will help the developer fix the issue faster.
We have to be careful not allow any security issues there, like we've had in the validator in the past.
Priority: -- → P4
Priority: P4 → P2
Based on the recently announced future plans for the Marketplace to remove payments, closing these bugs.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.