WebAPI/WebPayment/Multi-SIM: Difference between revisions
No edit summary |
|||
Line 42: | Line 42: | ||
== Firefox OS v1.4 == | == Firefox OS v1.4 == | ||
For v1.4 we would like to: | For v1.4 we would like to: | ||
* Allow the user to select the primary SIM for carrier billing, which should | * Allow the user to select the primary SIM for carrier billing, which should also also the primary SIM for data connections. | ||
* Expose to the payment provider the whole list of mcc/mnc for all the SIMs in the device, indicating which one is the primary one for carrier billing. This way, if the selected SIM is not valid, the payment provider will be able to check if the other SIM is valid, and in that case, suggest the user to change her selection (no need to change slots). If none of the SIMs are valid, we can even disable the setting to select the primary SIM for payments until the SIMs are changed. | * Expose to the payment provider the whole list of mcc/mnc for all the SIMs in the device, indicating which one is the primary one for carrier billing. This way, if the selected SIM is not valid, the payment provider will be able to check if the other SIM is valid, and in that case, suggest the user to change her selection (no need to change slots). If none of the SIMs are valid, we can even disable the setting to select the primary SIM for payments until the SIMs are changed. | ||
[https://bugzilla.mozilla.org/show_bug.cgi?id=938993 Bug 938993] will track the client side changes required for this and [https://bugzilla.mozilla.org/show_bug.cgi?id=942361 Bug 942361] the payment provider changes. | [https://bugzilla.mozilla.org/show_bug.cgi?id=938993 Bug 938993] will track the client side changes required for this and [https://bugzilla.mozilla.org/show_bug.cgi?id=942361 Bug 942361] the payment provider changes. |
Revision as of 16:43, 3 December 2013
Background information
Payment User Stories
1. As a User when I am on a data network and am purchasing an app I would like to be offered the option to pay for my purchase with the operator that I am currently using for my data if that operator supports payments, otherwise I should be offered an option to pay with my credit card.
- if I have not previosly made a purchase with that SIM before with my existing Persona account my device should be authenticated before any payment is charged to my account.
- if I have made a purchase previously with that operator from the Marketplace with that exact SIM, the payment system should recognize that and I should be automatically authenticated.
2. As a User, if I am in flight mode and do not have a current data network (BUT WIFI!), when I use Marketplace I would like to be offered the option to pay for my purchase with the operator that I have set for my data network (even if not in use) if my operator supports payments, otherwise I should be offered an option to pay with my credit card.
- if I have not previously made a purchase with that SIM before with my existing Persona account my device should be authenticated before any payment is charged to my account.
- if I have made a purchase previously with that operator from the Marketplace with that exact SIM, the payment system should recognize that and I should be automatically authenticated.
3. As a User I would like to understand that my data network operator that I am currently using with Marketplace will also be used for my payments. (There is also a confirmation screen for this - so users are not billed without knowing this is happening)
4. As a User, if I switch the choice of my data network SIM in my phone since my last purchase of an app, when I purchase an app, I should be able to purchase an app on the new data network SIM if my operator supports operator billing.
Firefox OS v1.3
For v1.3 bug 936471 was filed and fixed to mend the regression caused by the DSDS feature.
Single-SIM scenario
Payments should work ok in a single-SIM scenario, even with DSDS support in the platform.
Multi-SIM scenario
There is currently no plans for shipping any multi-SIM commercial device, but in that remote case, we might have some issues. The current situation after bug 936471 is:
- We are exposing the iccID/mcc/mnc information *only* for the SIM located in slot[0].
- This solved the immediate regression for single-SIM but didn't solve the problem for multi-SIM.
- With this model in a multi-SIM, use cases like the following won't work:
- The SIM at slot[0] is valid for carrier billing.
- The SIM at slot[1] is the primary SIM for SMS.
- The user starts her first payment. The payment provider gets the information from the SIM at slot[0] and starts the silent SMS flow.
- The SIM at slot[1] will be used for the silent SMS flow, since it is the primary SIM for SMS.
- Result: we will be authenticating the wrong SIM :(
The UX might also be confusing in this case:
- slot[0]: not valid SIM for payments
- slot[1]: valid SIM for payments, but unknown for the payment provider.
- The payment provider does not even know that the device has multiple SIMs, so I guess that we would silently skip the carrier billing step. But the user knows that she has a valid carrier billing SIM inserted on the device. She will need to try luck and change the slots for the SIMs with any pointers or recommendations from our side.
Firefox OS v1.4
For v1.4 we would like to:
- Allow the user to select the primary SIM for carrier billing, which should also also the primary SIM for data connections.
- Expose to the payment provider the whole list of mcc/mnc for all the SIMs in the device, indicating which one is the primary one for carrier billing. This way, if the selected SIM is not valid, the payment provider will be able to check if the other SIM is valid, and in that case, suggest the user to change her selection (no need to change slots). If none of the SIMs are valid, we can even disable the setting to select the primary SIM for payments until the SIMs are changed.
Bug 938993 will track the client side changes required for this and Bug 942361 the payment provider changes.