941952 - Detect and store region/carrier data in Webpay

Status: RESOLVED WONTFIX

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

Description

[Kumar McMillan [:kumar]]

Unlike Bango, we will send this data from Webpay to Zippy:

        carrier = 'USA_TMOBILE'
        region = '123'
        pay_method = 'OPERATOR'
        price = '0.99'
        currency = 'EUR'

The actual values will be derived from a few factors, mainly the MCC/MNC from window.mozPaymentProvider.

This bug is to pass in real values.

Comment 1

[Kumar McMillan [:kumar]]

This is mostly frontend stuff, checking MCC/MNC, but you can ping me when you get to the backend part. I have a TODO comment that is currently here (not yet landed) https://github.com/mozilla/webpay/pull/343

Comment 2

[Kumar McMillan [:kumar]]

We need this for Boku because the payment provider abstraction that we started for Zippy has these values hard coded. https://github.com/mozilla/webpay/blob/master/lib/solitude/api.py#L243-L245

Comment 3

[Kumar McMillan [:kumar]]

Nah, scratch that. Boku will do its own region detection and it can use the array of prices just like Bango

Comment 4

[Andy McKay]

The title makes it sound very similar to bug 987824, can we dupe?

Comment 5

[Kumar McMillan [:kumar]]

Actually, this bug was intended to patch Zippy but I don't think it's important now that I've made an adapter layer in webpay for each payment provider. bug 987824 will be the thing we need for Boku