Last Comment Bug 834257 - Pay via MT SMS challenge without leaving the Trusted UI
: Pay via MT SMS challenge without leaving the Trusted UI
[waiting on telefonica] p=1
Product: Marketplace
Classification: Server Software
Component: Payments/Refunds (show other bugs)
: 1.1
: x86 Mac OS X
P1 normal (vote)
: 2013-01-31
Assigned To: Keir Kettle
Depends on: 832790
Blocks: marketplace-payments
  Show dependency treegraph
Reported: 2013-01-24 08:13 PST by Kumar McMillan [:kumar] (needinfo all the things)
Modified: 2013-05-30 16:54 PDT (History)
4 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Kumar McMillan [:kumar] (needinfo all the things) 2013-01-24 08:13:13 PST
In Marketplace:

1. Launch marketplace-dev app on your unagi phone
2. Log in to Identity
3. Search for the paid app 'private yacht'
4. Click on the purchase button
5. Create your Payments PIN

Bango is implementing this (called an MT, mobile terminated, flow):

6. When prompted, enter your phone number into the payments flow
7. See message in payments flow that a " confirmation is being sent via SMS and you will be asked to re-enter the code [ here ] "
8. See confirmation code in SMS on top of the screen without leaving trusted UI
8b. if user misses the SMS text, they can pull down the notification drawer and still read the code
8c. if they get really lost, they can open the SMS app, read the code, return to the Maketplace app, and the Trusted UI will open again and pick up where they left off
9. enter confirmation code into payments flow and proceed with payment process

- user is not dropped out of flow (this is better than bug 832108)
- this will not require any device code changes
Comment 1 User image Steve Ruston 2013-01-28 09:49:00 PST
MT SMS is done, awaiting shortcode to complete flow. Assigning to Bango to resolve
Comment 2 User image Steve Ruston 2013-02-15 09:06:07 PST
Shortcode fix implemented 16.55 UK time 15th Feb
Comment 3 User image krupa raj[:krupa] 2013-05-30 16:54:57 PDT
this is done and it works

Note You need to log in before you can comment on or make changes to this bug.