The Future of Payments on the Road - API Days SF 2014

1,044 views

Published on

Paypal + Uber for seamless driver payment experience.
Samsung S5 fingerprint scanner for OAuth-based API identity in mobile payments utilizing FIDO
Paypal Beacon utilizing Bluetooth LE to provide location awareness

Published in: Automotive, Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,044
On SlideShare
0
From Embeds
0
Number of Embeds
103
Actions
Shares
0
Downloads
28
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The Future of Payments on the Road - API Days SF 2014

  1. 1. PAYPAL PLATFORM THE FUTURE OF PAYMENTS ON THE ROAD API Days SF June 14, 2014 Jason Harmon Head of API Design @jharmn jasharmon@paypal.com
  2. 2. PayPal … – 148 million active accounts – 193 markets in 26 currencies – 2013 – Total Payment Volume was $180 billion – $27 billion in mobile payments – Q1 2014 – Total Payment Volume of $52 Billion – At $6688 TPV / second – 834 million payments, 9+ million every day – $1 in every $6 spent on e-commerce – 25% spent on cross-border trade THE PAYPAL CONTEXT In a dynamic environment – 300+ features per quarter – We roll 100,000+ lines of code every two weeks
  3. 3. PAYPAL PLATFORM HAS EVOLVED TO SUPPORT NEW INTEGRATION NEEDS PayPal API PayPal Capabilities 2001 Instant Payment Notification 2004 Transaction, Mass Pay API 2005 Direct Payment API, Express Checkout 2007 Payment APIs (NVP) 2009 Adaptive APIs (SOAP/XML, NV, JSON) 2013 Payment APIs (REST)
  4. 4. PAYMENTS: THE WAY THINGS USED TO BE
  5. 5. PAYMENTS: HOW IT WORKS TODAY
  6. 6. HOW OFTEN DO YOU PAY AND DRIVE? EASILY…
  7. 7. UBER + PAYPAL: EASY
  8. 8. UBER + PAYPAL: EASY GET IN. RIDE. GET OUT.
  9. 9. UBER + PAYPAL: REST API
  10. 10. UBER + PAYPAL: MOBILE SDK
  11. 11. THE USUAL RULES: DUMB API CLIENTS ARE GOOD API CLIENTS • REST API should encapsulate business logic • Complicated steps should be made easy • Minimize the need to for client to persist state • Multiple identifiers are problematic • /widgets/{id}/things/{id}/stuff/{id} • Hypermedia helps • Encapsulate permissions • Opaque URLs
  12. 12. TO MAKE THINGS EASIER SOMETIMES THE CLIENT HAS TO BE SMARTER
  13. 13. WHEN API CLIENTS NEED SMARTS LOCATION AT THE EDGE  Mobile OS provides some location data  Identifying a specific venue is more difficult  Interacting with that venue is really tricky  Bluetooth LE allows interaction with the venue
  14. 14. WHEN API CLIENTS NEED SMARTS LOCATION AT THE EDGE
  15. 15. WHEN REST APIS AREN’T ENOUGH IDENTITY • OAuth 2 provides framework • Passwords are weak at best • API/OAuth provider can only provide so much…
  16. 16. BIOMETRIC IDENTITY Samsung S5  First implementation of FIDO  Fingerprint scan interacts with mobile client library  FIDO data is passed to Paypal for authentication  REST APIs + additional Oauth grant type http://www.embedded.com/design/real-world- applications/4430305/Implementing-Android-based-fingerprint-authentication- for-online-payments
  17. 17. PAYPAL BEACON VOICE RECOGNITION Plans to integrate voice recognition integrated into the app
  18. 18. THE FUTURE OF PAYMENTS IN THE CAR TODAY MOST OF THIS IS DOABLE ON A MOBILE DEVICE
  19. 19. TESLA: THE FUTURE OF CARS
  20. 20. TESLA: API-ENABLED CAR
  21. 21. APPS IN THE DRIVER EXPERIENCE • How could we tie all of this together? • Retail presence: connected sensors • Developers in the dash: installable apps • Bluetooth: already largely available in cars, developer access needed • Biometrics: FIDO provides a standard, vehicles would be safer if utilized
  22. 22. MOBILE DEVICES MIGHT BE BEST Dash-based apps could be a big risk http://www.kurzweilai.net/how-an-mp3-can-be-used-to-hack-your-car Mobile devices won’t give your car a blue screen of death at the drive-thru
  23. 23. jasharmon@paypal.com @jharmn

×