908884 - Skip MT Auth and use silent SMS when possible

Status: RESOLVED FIXED

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Description

[Kumar McMillan [:kumar]]

beta builds of Firefox OS will allow Bango to do a silent SMS to a short code. This can replace the complex user interaction of doing manual MT auth. Bango needs to work with this JavaScript API and provide a user experience (a wait screen?) to integrate it into the payflow.

The device API landed in bug 816564

Comment 1

[Kumar McMillan [:kumar]]

Until docs are ready, this is a sneak peak: http://hg.mozilla.org/projects/birch/rev/e660fb3f8481#l1.210 It's available as window.mozPaymentProvider.observeSilentSMS(shortCode, myCallback)

Comment 2

[Kumar McMillan [:kumar]]

Maureen can help with UX. I guess it should show a spinner and say something like "Please wait while we set up direct billing"

Comment 3

[Maureen Hanratty]

Attachment: Screen Shot 2013-08-23 at 4.27.57 PM.png

What about generalizing to "Setting up payment"? Just thinking we might not want to refer to carrier billing as the user might choose to do credit card instead when they get to the confirm screen.

Comment 4

[Kumar McMillan [:kumar]]

I like that better! Thanks Maureen. FYI, the mock-up shows an MT auth input form in the background but that won't be visible.

Comment 5

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Kumar McMillan [:kumar] from comment #1)
> Until docs are ready, this is a sneak peak:
> http://hg.mozilla.org/projects/birch/rev/e660fb3f8481#l1.210 It's available
> as window.mozPaymentProvider.observeSilentSMS(shortCode, myCallback)

I wrote a few words about the silent SMS flow at https://bugzilla.mozilla.org/show_bug.cgi?id=816564#c69

I'll try to update the docs as soon as possible.

Comment 6

[Fernando Jiménez Moreno [:ferjm]]

https://wiki.mozilla.org/WebAPI/WebPaymentProvider#Silent_SMS

Comment 7

[Andy McKay]

Clearing out the bango assignment and priority until we've completed the required business scoping with Bango and can file some more specific bugs based on needs.

Comment 8

[Andy McKay]

This is being scoped by Bango.

Comment 9

[Jim]

This would fall under (or at least after) the delivery of Silent SMS functionality.

Comment 10

[Steve Ruston]

Attachment: SoW - Silent SMS V1.docx

Comment 11

[Andy McKay]

Looks good to me, comments:

"In the case where the MT Auth SMS is not intercepted by the Mozilla API (and in all cases that the Bango registered callback function is not called), the Bango flow will timeout after 10 seconds and display the Bango “Error” page at which point the user must retry the purchase from the start of the flow."

In that scenario, the user is back at the beginning and will hit this point again, if the flow does not happen quickly enough. We've seen quite a few cases where SMS's take a long time. Would it make sense to fall back to the MT Auth screen or find a way to increase that timeout. I'm worried people will get caught in a loop of not being able to get the silent SMS done.

"The Bango integration will utilise the observeSilentSMS method, passing the defined shortcode number"

Presumably if no short code exists for that operator, it will fall back to MT Auth for that user?

Comment 12

[David Bialer [:dbialer]]

An alternative would be to increase the timeout and try again.  

So the error could say something like "Authentication timed out.  Try again/Cancel"

in which case the timeout could increased be increased by 50% each try.

I rather not have to maintain 2 flows or switch flows and on the try again scenario.

When would we not have a short code?  and if so, can we even support those scenarios (as Andy mentioned to me he can't do MT Auth in Canada)?

Comment 13

[Steve Ruston]

Work to monitor and review timeout periods will be required, Google Analytics can be used to see how many users fall back to MT auth visible flow. 

Silent SMS won't work on FF for Android however 893050 will help previous poor UX

Comment 14

[Simone Masiero]

This release is now Live.

Comment 15

[Steve Ruston]

(In reply to Simone Masiero from comment #14)
> This release is now Live.

Simone, do you mean Live or on Test

Comment 16

[Keir Kettle]

Live

Comment 17

[Andy McKay]

Let's test this.