1038398 - User is stuck at 'Payment Complete!' screen after which it fails with NOTICE_ERROR / TRANS_CONFIG_FAILED

Status: RESOLVED FIXED

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

Description

[krupa raj[:krupa]]

Attachment: verbose logging for notice_error.txt

Connectivity: wifi
SIM used: movistar Spain 
Gaia/device: 1.3/hamachi

steps to reproduce:
1. Launch pure-packaged stage app 
2. Search for :paid
3. Start the purchase of a paid app
4. Enter PIN
5. Confirm Purchase


expected behavior:
purchase is successful and the app install is triggered.

actual behavior:
User is stuck at 'Payment Complete!' screen after which it fails with NOTICE_ERROR

07-14 13:33:52.959 E/GeckoConsole(  135): Content JS LOG at https://marketplace-cdn.allizom.org/mozpay/media/js/pay-min.js?build=4653767-53bee440:5 in y: [pay] starting transaction: /mozpay/configure-transaction
07-14 13:33:53.499 E/GeckoConsole(  135): Content JS LOG at https://marketplace-cdn.allizom.org/mozpay/media/js/pay-min.js?build=4653767-53bee440:5 in y/<: [pay] Transaction config failed. Status returned: 400
07-14 13:33:53.499 E/GeckoConsole(  135): Content JS LOG at https://marketplace-cdn.allizom.org/mozpay/media/js/pay-min.js?build=4653767-53bee440:5 in y/<: [pay] Error message: TRANS_CONFIG_FAILED

Comment 1

[krupa raj[:krupa]]

Attachment: screenshot.png

Comment 2

[krupa raj[:krupa]]

Attachment: screenshot.png

Comment 3

[Kumar McMillan [:kumar]]

Keir, could you look at this? This is similar to bug 1036120 but instead of a cancel it happened on a successful purchase.

The query string in the success redirect looked like:

w.bango:INFO Bango success: <QueryDict: {
u'BillingConfigurationId': [u'149326235'], 
u'ResponseCode': [u'OK'], u'P': [u''], 
u'Currency': [u'EUR'], 
u'BangoUserId': [u'1763270485'], 
u'MerchantTransactionId': [u'webpay:fc81d710-899d-4a33-baf6-2406eb8f86a7'], 
u'MozSignature': [u'e05d771f6a93822bcf1f677d47fca93d25bccabe059c73fe828cda18d8450254'], 
u'Token': [u'93866f67-2b96-4590-b9a9-ce3b2547c8c6'], 
u'ResponseMessage': [u'Success'], 
u'BangoTransactionId': [u'1530754825'], 
u'TransactionMethods': [u'ESP_MOVISTAR,Telefonica Spain,BLUEVIA,BLUEVIA Hub'], 
u'Price': [u'0.89'], 
u'Network': [u'ESP_MOVISTAR']}>

The token check was missing a transaction (not a signature):

(TokenCheckerResponse){
   ResponseMessage = "Success"
   ResponseCode = "OK"
   Signature = "e05d771f6a93822bcf1f677d47fca93d25bccabe059c73fe828cda18d8450254"
   MerchantTransactionId = None
   BangoUserId = 1763270485
   BangoTransactionId = 1530754825
   Price = 89.0
   Currency = "EUR"
   TransactionMethod = 
      (TransactionMethod){
         networkId = "ESP_MOVISTAR"
         networkDescription = "Telefonica Spain"
         paymentMethodId = "BLUEVIA"
         paymentMethodDescription = "BLUEVIA Hub"
      }
 }

More info on the server exception: http://sentry.dmz.phx1.mozilla.com/marketplace-stage/marketplace-stage-webpay/group/20583/

Comment 4

[Wil Clouser [:clouserw]]

Please treat this bug as high priority.  It's blocking an important initiative (packaged app - see blocked bug)

Comment 5

[Keir Kettle]

Investigating now.

Comment 6

[Keir Kettle]

OK - looks like I've found an issue with the token checker when checking requests initiated using billing configuration v2.  As you guys are probably aware, Bango is undertaking a data center migration and as such we are in a platform freeze until next week (7/21).

Comment 7

[Wil Clouser [:clouserw]]

(In reply to Keir Kettle from comment #6)
> OK - looks like I've found an issue with the token checker when checking
> requests initiated using billing configuration v2.  As you guys are probably
> aware, Bango is undertaking a data center migration and as such we are in a
> platform freeze until next week (7/21).

Krupa - is this impacting end users or only our packaged app?  Does this happen 100% of the time?

Comment 8

[Kumar McMillan [:kumar]]

This isn't impacting end users because it's limited to the Billing Config service version 2.0 which is only active on stage right now while we test the new Bango identity feature. It is not happening in prod.