1 / 23

Mobile Wallets

Mobile Wallets. Tackling the multi-wallet p roblem to achieve mass market adoption of contactless payment services. A Quick Introduction. Neal Michie ( neal.michie@helixion.com ) - Technical Business Development Director at Helixion

yardan
Download Presentation

Mobile Wallets

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mobile Wallets Tackling the multi-wallet problem to achieve mass market adoption of contactless payment services

  2. A Quick Introduction • Neal Michie (neal.michie@helixion.com) - Technical Business Development Director at Helixion • Background in software engineering before falling into Business Development role • Helixion works with both network operators and service providers to deploy secure contactless transaction products.

  3. Agenda • Understanding the different wallet architecture options. • What is the multi-wallet problem and what it means for service providers. • How to address the multi-wallet problem.

  4. Wallet architectures

  5. The mobile wallet • “Wallet” means everything to everyone. • For this presentation a mobile “wallet” is simply a container for services.

  6. Wallet types • Container wallet, widget wallet? – Unfortunately it’s not quite as neat as that. • At the very least need to think of wallets as a sliding scale – even then that’s a simplification. Control moves from Service Provider to Wallet Provider

  7. Wallet types – thin - “phone as a wallet” • Wallet functionality embedded deep into the phone. • No visible wallet icon on phone’s launcher. • Each service appears to the user an it’s own application – because it is it’s own application. • As Service Provider applications are native applications, it is flexible and can take advantage of all handset functionality.

  8. Wallet types – thick - “monolithic wallet” • Wallet functionality is provided as an app on the phone. • Wallet also provides service functionality. • Service provider simply provides branding information to the wallet provider.

  9. Wallet types – middle ground - “widget wallet” • Most likely the wallet will be somewhere in the middle of the two extremes. • Wallet functionality is provided as an app on the phone. • Service provides create “widgets” that run within the wallet application. • “Widgets” typically created in platform independent code (e.g. JME, HTML). • “Widgets” typically light weight and can only use functionality exposed by wallet.

  10. Multi-wallet problem

  11. The multi-wallet problem

  12. Independent solutions • We said each wallet is different and so each wallet requires its own solution. • Recreating solution of each wallet is expensive. • Recreating solution of each wallet takes time.

  13. Weakened branding • Depending where a wallet sits on our sliding scale, the ability to create the desired user experience changes. • Thick wallets limit scope for defining service provider user experience. • Balancing act between: • Defining a user experience to the lowest common dominator. • Having different user experiences on each wallet deployment.

  14. Solving the multi-wallet problem (technical)

  15. Requirements of a solution • Provide an efficient (low cost / low effort) route to reach ALL customers. • To protect their brand by providing a consistent user experience to the customer. • Give Service Providers control over the user experience.

  16. A Solution • Solution is to architect solutions that build on a consistent platform or base. • This reduces rework for each deployment: • Saving time and money • Makes it easier to develop a consistent experience • Avoids unintentional differences in experience caused by different understands of requirements or coding errors.

  17. A Solution • A wallet standard? • GSMA are currently looking into this – they were presenting ideas about it in the “Connected City” at MWC. • Is this feasible? Would the wallet providers be willing to confirm to a standard. • Most likely that a service provider will need to create their own “standard” that they can integrate into each wallet. This will give them the benefits described without the wallet providers having to conform.

  18. Solving the multi-wallet problem (commercial)

  19. A Solution • As with most deploy issues around secure services – solving the technical issues is only have the story. • To drive mass market adoption, users have to be able to access the service who every is there network operator. This means that a service provider will commercial relationships with each wallet provider. • For large services providers – this is feasible (if time consuming) • But to drive mass market acceptance, small(er) service providers also need a route to market – potentially a place for service aggregators.

  20. Thank you. neal.michie@helixion.com

  21. Final thought: There’s a lot more SPs than MNOs….

  22. So what happens if we add multiple SP?

More Related