941476 - [B2G][User Story] [DSDS] Marketplace Payment

Status: RESOLVED INCOMPLETE

(Core :: DOM: Device Interfaces, defect)

Description

[Sandip Kamat]

From payments perspective, treat the primary SIM as the SIM that marketplace/payments uses (same as single SIM experience). The second SIM will not be considered (until it is made the primary SIM).

Comment 1

[Ken Chang[:kenkai]]

Add 2 depending bugs.

Comment 2

[Jean Gong :jgong]

Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]

Comment 3

[Jason Smith [:jsmith]]

Fernando - Doesn't bug 936471 already resolve the user story in this bug? Or is there something left to do here?

Comment 4

[Fernando Jiménez Moreno [:ferjm]]

Quoting my own emails:

"... the current situation after bug 936471 is:

1. We are exposing the iccID/mcc/mnc information *only* for the SIM located in slot[0].
2. This solved the immediate regression but didn't solve the problem.
3. With this model, use cases like the following won't work:
3.1 The SIM at slot[0] is valid for carrier billing.
3.2 The SIM at slot[1] is the primary SIM for SMS.
3.3 The user starts her first payment. The payment provider gets the information from the SIM at slot[0] and starts the silent SMS flow.
3.4 The SIM at slot[1] will be used for the silent SMS flow, since it is the primary SIM for SMS.
3.5 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.
In this case 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.

I agree that these are edge cases. In fact, DSDS feels like an edge case to me. But still we need to solve it.

So, conclussions.

IMHO the best way to solve the multi-SIM scenario for payments (based on my previous assumptions) is:

1- Allow the user to select the primary SIM for carrier billing.
2- 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. IMHO this feels like a better UX."

So IMHO even if payments won't break in 1.3, this US is not fully completed (at least wrt the client side), as there are still missing edge cases (and security issues) that we need to fix. It seems unlikely that these changes will make it in 1.3 though.

Comment 5

[Ken Chang[:kenkai]]

Hi Wilfred, should we move this bug to DSDS v1.4? Thank you.

Comment 6

[Wilfred Mathanaraj [:WDM]]

yes i have just 1.4+ it - let me know if this works for you.

Comment 7

[Preeti Raghunath(:Preeti)]

Wilfred,

If this is a user story we do not need the 1.4+ on it. Hence please remove the same.

We'll track dependencies as blockers infact

Comment 8

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

FxOS/Gonk has been removed from the codebase. Mass-invalidating FxOS related Device Interface bugs to clean up the component. 

If I incorrectly invalidated something, please let me know.

Comment 9

[Firefox Bug Husbandry Bot]

Bulk correction of resolution of B2G bugs to INCOMPLETE.