WebAPI/WebPayment/Multi-SIM: Difference between revisions

← Older edit

WebAPI/WebPayment/Multi-SIM (view source)

Revision as of 23:24, 1 October 2014

2,066 bytes added , 1 October 2014

no edit summary

Chaasof

Confirmed users

1,340

edits

@@ Line 3: / Line 3: @@
 * [https://wiki.mozilla.org/FirefoxOS/DSDS DSDS]
-== Multi-Sim User Stories ==
+See the [[WebAPI/WebPaymentProvider|WebPaymentProvider]] for how one would access multi-SIM data.
-=== Payment User Stories ===
+== Payment User Stories ==
 . 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.
@@ Line 19: / Line 19: @@
 . 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 ===
+== Firefox OS v1.3 ==
 For v1.3 [https://bugzilla.mozilla.org/show_bug.cgi?id=936471 bug 936471] was filed and fixed to mend the regression caused by the DSDS feature.
-==== Single-SIM scenario ====
+=== Single-SIM scenario ===
 Payments should work ok in a single-SIM scenario, even with DSDS support in the platform.
-==== Multi-SIM scenario ====
+=== 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 [https://bugzilla.mozilla.org/show_bug.cgi?id=936471 bug 936471] is:
@@ Line 42: / Line 42: @@
 * 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 ===
+== Firefox OS v1.4 ==
-For v1.4 we would like to:
-* Allow the user to select the primary SIM for carrier billing, which should be also the primary for the data connections.
+In order to have a full support for multi-SIM payments where:
-* 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.
+* The user is always aware about which one of her SIMs is used for payments if the SIM is in the device.
+* We always authenticate the correct SIM that is used for payments.
+* We know when to remove the payment session to trigger a new authentication flow.
+the proposal is the following:
+* We will expose to the payment provider the serviceId associated with the SIM selected for payments via '''mozPaymentProvider.paymentServiceId'''. It can be the primary SIM for data by default, it doesn't really matter.
+* We will expose to the payment provider the whole list of ICCID/MCC/MNC for all the SIMs in the device indexed by serviceId, indicating which one is the primary one for data. We will remove the '''.iccIds''', '''.mcc''' and '''.mnc''' properties and will introduce a new '''.iccInfo''' property of this form:
+** {'serviceId1': { iccId: '1234', mcc: '222', mnc: '333', dataPrimary: false }, 'serviceIdN': { iccId: '5678', mcc: '222', mnc: '333', dataPrimary: true }}
+* If there is a record of a previous payment (I guess, a payment cookie), the payment provider will need to check that nothing changed wrt to the SIM selected for payments. Otherwise, a new authentication flow needs to be triggered.
+* If there is no record of a previous payment, a new authentication flow needs to be triggered. The payment provider will need to process the list containing the services information in order to set the correct SIM for payments. The decision algorithm could be something like [http://www.gliffy.com/go/publish/image/5175268/L.png this].
+** Once the payment provider selects the appropriate SIM it will set the serviceId associated with this SIM via '''mozPaymentProvider.paymentServiceId'''.
+** Note that in case that the (not silent) SMS flow is required, we will need to ask the user for her MSISDN and this could be an MSISDN from an external SIM. In this case, the payment provider will set the service ID to '''null''' and will need to call '''mozPaymentProvider.observeSilentSms(number)'''. If the SMS is received in the device, we can set the serviceId of the receiving SIM as the one selected for payments.
+* If there is a record of a previous payment and the payment serviceId is null, it means that the payment was done with an external SIM and so we need to allow the user to remove the payment session to retrigger the authentication flow with another SIM.
+* The selected SIM will be the one used for the silent SMS flow if needed and the one shown in settings as primary for payments, if we decide to show this information.
 [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.
+[[Category:Web APIs]]