Confirmed users
483
edits
WebAPI/WebPayment/Multi-SIM: Difference between revisions
Jump to navigation
Jump to search
→Firefox OS v1.4
| Line 44: | Line 44: | ||
In order to have a full support for multi-SIM payments where: | 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 | * 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 always authenticate the correct SIM that is used for payments. | ||
* We know when to remove the payment session to trigger a new authentication flow. | * We know when to remove the payment session to trigger a new authentication flow. | ||
| Line 59: | Line 59: | ||
* 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]. | * 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'''. | ** 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 | ** 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 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. | * 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. | ||