WebAPI/WebPayment/Multi-SIM: Difference between revisions

← Older edit

WebAPI/WebPayment/Multi-SIM (view source)

Revision as of 23:24, 1 October 2014

8 bytes added , 1 October 2014

no edit summary

Chaasof

Confirmed users

1,340

edits

@@ Line 2: / Line 2: @@
 * [https://wiki.mozilla.org/WebAPI/WebTelephony/Multi-SIM#Multi-SIM_Scenario Multi-SIM scenario]
 * [https://wiki.mozilla.org/FirefoxOS/DSDS DSDS]
+See the [[WebAPI/WebPaymentProvider|WebPaymentProvider]] for how one would access multi-SIM data.
 == Payment User Stories ==
@@ Line 44: / Line 46: @@
 In order to have a full support for multi-SIM payments where:
-* The user is always aware about which one of her SIMs is used for payments. Even if this SIM is not in the device!
+* 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.
@@ Line 50: / Line 52: @@
 the proposal is the following:
-* We will expose to the payment provider the serviceId associated with the SIM selected for payments via '''mozPaymentProvider.getPaymentServiceId'''. It can be the primary SIM for data by default, it doesn't really matter.
+* 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 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:
-** This means that '''mozPaymentProvider.iccId''' will return an object like:
+** {'serviceId1': { iccId: '1234', mcc: '222', mnc: '333', dataPrimary: false }, 'serviceIdN': { iccId: '5678', mcc: '222', mnc: '333', dataPrimary: true }}
-*** {'serviceId1': { id: '1234' }, 'serviceIdN': { id: '5678', dataPrimary: true }}
-** The same for '''mozPaymentProvider.mcc''':
-*** {'serviceId1': { mcc: '213' }, 'serviceIdN': { mcc: '214', dataPrimary: true }}
-** And '''mozPaymentProvider.mnc''':
-*** {'serviceId1': { mnc: '2' }, 'serviceIdN': { mnc: '2', 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.
-** Once the payment provider selects the appropriate SIM it will set the serviceId associated with this SIM via '''mozPaymentProvider.setPaymentServiceId'''.
+* 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.
-** 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. We might be able to do it better and listen for incoming auth SMS. If the SMS is received in the device, we can set the serviceId of the receiving SIM as the one selected for payments. To do this, we will need the payment provider to specify the number from where the auth SMS is sent via '''mozPaymentProvider.observeAuthMessage(number)'''.
+* 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.
-* 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.
+[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.
+[[Category:Web APIs]]