PAYPAL	
  PLATFORM	
  	
  
EVOLVING	
  FOR	
  SIMPLICITY	
  AND	
  SCALE	
  
API	
  Strategy	
  &	
  Prac;ce	
  
October	
...
THE PAYPAL CONTEXT

PayPal …
–  137 million active accounts
–  193 markets in 26 currencies
– 

2012: Total Payment Volume...
PAYPAL	
  PLATFORM	
  HAS	
  EVOLVED	
  
TO	
  SUPPORT	
  NEW	
  INTEGRATION	
  NEEDS	
  
2001 Instant Payment Notificatio...
QUESTIONS	
  THAT	
  GUIDE	
  US	
  

Who	
  are	
  the	
  end	
  users?	
  
	
  
Who	
  are	
  the	
  developers?	
  
	
 ...
WHO	
  ARE	
  THE	
  END	
  USERS?	
  

segments	
  
experiences	
  
expecta;ons	
  
WHO	
  ARE	
  THE	
  DEVELOPERS?	
  

tools	
  and	
  processes	
  
technology	
  preferences	
  	
  
role	
  of	
  our	
 ...
HOW	
  SHOULD	
  WE	
  DESIGN	
  OUR	
  API?	
  

internal	
  api	
  vs.	
  external	
  api	
  
api	
  porKolio	
  vs.	
  ...
HOW	
  SHOULD	
  WE	
  EASE	
  LEARNING?	
  

good	
  documenta;on	
  
sdk	
  and	
  code	
  samples	
  
sandbox	
  
HOW	
  SHOULD	
  WE	
  SIMPLIFY	
  INTEGRATION?	
  

familiar	
  integra;on	
  model	
  
api	
  call	
  dashboard	
  
cust...
SUMMARY	
  

•  PayPal	
  has	
  grown	
  phenomenally	
  since	
  its	
  incep;on	
  
•  PayPal	
  PlaKorm	
  has	
  evol...
dn@paypal.com	
  
@deepak_nadig	
  
Upcoming SlideShare
Loading in...5
×

PayPal Platform - Evolving for Simplicity and Scale: API Strategy & Practice San Francisco 2013

9,514
-1

Published on

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

No Downloads
Views
Total Views
9,514
On Slideshare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

PayPal Platform - Evolving for Simplicity and Scale: API Strategy & Practice San Francisco 2013

  1. 1. PAYPAL  PLATFORM     EVOLVING  FOR  SIMPLICITY  AND  SCALE   API  Strategy  &  Prac;ce   October  24,  2013     Deepak  Nadig   Head  of  PlaKorm  Engineering  
  2. 2. THE PAYPAL CONTEXT PayPal … –  137 million active accounts –  193 markets in 26 currencies –  2012: Total Payment Volume was $145 billion –  –  –  –  –  –  Q3 2013 Total Payment Volume of $44 Billion At $5580 TPV / second Growing 25% YoY 729 million transactions 8 million payments every day 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   2001 Instant Payment Notification 2004 Transaction, Mass Pay API 2005 Direct Payment API, Express Checkout PayPal API 2007 Payment APIs (NVP) 2009 Adaptive APIs (SOAP/XML, NV, JSON) PayPal Capabilities 2013 Payment APIs (REST)
  4. 4. QUESTIONS  THAT  GUIDE  US   Who  are  the  end  users?     Who  are  the  developers?     How  should  we  design  our  API?     How  should  we  ease  learning?     How  should  we  simplify  integra;on?  
  5. 5. WHO  ARE  THE  END  USERS?   segments   experiences   expecta;ons  
  6. 6. WHO  ARE  THE  DEVELOPERS?   tools  and  processes   technology  preferences     role  of  our  api  
  7. 7. HOW  SHOULD  WE  DESIGN  OUR  API?   internal  api  vs.  external  api   api  porKolio  vs.  api   capability  api  vs.  personalized  api     API Design Team
  8. 8. HOW  SHOULD  WE  EASE  LEARNING?   good  documenta;on   sdk  and  code  samples   sandbox  
  9. 9. HOW  SHOULD  WE  SIMPLIFY  INTEGRATION?   familiar  integra;on  model   api  call  dashboard   customer  support  
  10. 10. SUMMARY   •  PayPal  has  grown  phenomenally  since  its  incep;on   •  PayPal  PlaKorm  has  evolved  to  support  this  growth   •  customer  scenarios   •  integra;on  channels   •  Five  ques;ons  are  guiding  the  next  genera;on  of  PayPal  PlaKorm   •  Who  are  the  end  users?   •  Who  are  the  developers?   •  How  should  we  design  our  API?   •  How  should  we  ease  learning?   •  How  should  we  simplify  integra;on?  
  11. 11. dn@paypal.com   @deepak_nadig  
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×