Creating a User-Centric Mobile Payment Architecture

21
Creating a User-Centric Mobile Payment Architecture Jonathan LeBlanc (@jcleblanc) Head of Developer Evangelism (North America) PayPal | Developer

description

Payment architectures are no longer flat experiences that are static for all users. Mobile experiences have become personalized, providing an identity infrastructure to promote payment ease for users. Through the lessons learned from a mobile first PayPal product overhaul, we'll explore how identity and in-app purchasing coalesce to create a scalable mobile payment infrastructure, looking into how building cross-platform payment personalization increasing user ease and revenue.

Transcript of Creating a User-Centric Mobile Payment Architecture

Page 1: Creating a User-Centric Mobile Payment Architecture

Creating a User-Centric Mobile Payment

Architecture

Jonathan LeBlanc (@jcleblanc)Head of Developer Evangelism (North America)

PayPal | Developer

Page 2: Creating a User-Centric Mobile Payment Architecture

The Age of Online Identity

Page 3: Creating a User-Centric Mobile Payment Architecture

Developer efficiency task 4

Offload complexity to the implementing provider

Offload Complexity

Page 4: Creating a User-Centric Mobile Payment Architecture

Identity as a Mobile Foundation

Social Login Systems

Page 5: Creating a User-Centric Mobile Payment Architecture

Lots and Lots of Fake Data

Page 6: Creating a User-Centric Mobile Payment Architecture

Identity is Not Facebook

Page 7: Creating a User-Centric Mobile Payment Architecture

Identity is Not Even PayPal

Page 8: Creating a User-Centric Mobile Payment Architecture

These Are Simply Just Tools

Page 9: Creating a User-Centric Mobile Payment Architecture

User Curated Identity

Page 10: Creating a User-Centric Mobile Payment Architecture

Concrete Identity

Page 11: Creating a User-Centric Mobile Payment Architecture

Moving Identity Forward

Using Identity to Remove Login

Page 12: Creating a User-Centric Mobile Payment Architecture

Identity to Remove Registration

Page 13: Creating a User-Centric Mobile Payment Architecture

How We’re Handling Identity

Page 14: Creating a User-Centric Mobile Payment Architecture

Time Interactions and Identity

Page 15: Creating a User-Centric Mobile Payment Architecture

InterestsUser A

InterestsUser B

Inte

rests

Com

mon

Expanding Identity via Commonality

Page 16: Creating a User-Centric Mobile Payment Architecture

Personalized Recommendations

Optimists consider that up to a 30% of ecommerce sales increase is

thanks to cross-selling recommended products

fikobservatory

Page 17: Creating a User-Centric Mobile Payment Architecture

Identity is Mobile Foundation

Personalization for User Shortcuts

Page 18: Creating a User-Centric Mobile Payment Architecture

23% of customers abandoned carts when asked to register (Forrester)

…At five questions, the drop-off rate is 2 percent; at 10 questions,

4 percent, and so on. Only at about question 35 does the correlation

end (Kevin Hale, Wufoo)

Page 19: Creating a User-Centric Mobile Payment Architecture

Fixing Mobile Form Drop Rates

Page 20: Creating a User-Centric Mobile Payment Architecture

Further Reducing Friction

Page 21: Creating a User-Centric Mobile Payment Architecture

Thank You!

Jonathan LeBlanc (@jcleblanc)Head of Developer Evangelism (North America)

PayPal | Developer