849912 - KeyError: amount. Webpay error for successful Bango purchase

Status: RESOLVED FIXED

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

Description

[Kumar McMillan [:kumar]]

HttpServerError: Server Error 500: https://payments.allizom.org/bango/notification/
Content: {"error_code": "KeyError", "error_data": {}, "error_message": "'amount'"}

More info: http://sentry.dmz.phx1.mozilla.com/amo-ops/marketplace-stage-webpay/group/11855/

Jorge found this while testing. The URL was:

https://marketplace.allizom.org/mozpay/bango/success?ResponseCode=OK&ResponseMessage=Success&BangoUserId=1567997845&MerchantTransactionId=webpay%3acf79057a-dc3e-4237-a48b-3597643b9af4&BangoTransactionId=1122772065&TransactionMethods=ESP_MOVISTAR%2cTelefonica+Spain%2cTESTPAY%2cTest+Pay&BillingConfigurationId=5195690&MozSignature=2928d4a2b937c1a5c0dbaf10354926c2da6f02460a9a5df63abe1fbc0287e1cd&Currency=EUR&Network=ESP_MOVISTAR&Price=0%2c79&P=

Comment 1

[Kumar McMillan [:kumar]]

Actually, this happened because our stage servers were out of sync but we fixed that in bug 846930

Jorge, can you try testing it again?

This specific error was fixed a while ago in this revision but the code had not been deployed. https://github.com/mozilla/solitude/commit/570c8fc4

Comment 2

[Jorge Vila]

Hi Kumar,

we have being with Fernando testing with "Private Yatch" and the error was always that there was a Payment Failure.

Will try again on Monday.

Can you tell us how to get the info from HTTP identity logs?
Best

Comment 3

[Kumar McMillan [:kumar]]

Hmm, maybe this is something specific to MobileID again. I don't see any errors in our logs.

I run `ezboot http` to capture HTTP logs on device: https://github.com/kumar303/ezboot

This starts up B2G with some env vars then pulls down the log file afterward:
https://github.com/kumar303/ezboot/blob/master/ezboot/__init__.py#L200-L202

More docs are here: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging#Firefox_OS_phones

If you can produce the logs I'd like to take a look.

Comment 4

[Kumar McMillan [:kumar]]

I haven't seen this specific error in our logs for more than 60 days and it didn't come up during the test week so I think we are receiving the right query string from Bango now.