1. PAYPAL
PLATFORM
EVOLVING
FOR
SIMPLICITY
AND
SCALE
API
Strategy
&
Prac;ce
October
24,
2013
Deepak
Nadig
Head
of
PlaKorm
Engineering

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. 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. 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. WHO
ARE
THE
END
USERS?
segments
experiences
expecta;ons

6. WHO
ARE
THE
DEVELOPERS?
tools
and
processes
technology
preferences
role
of
our
api

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. HOW
SHOULD
WE
EASE
LEARNING?
good
documenta;on
sdk
and
code
samples
sandbox

9. HOW
SHOULD
WE
SIMPLIFY
INTEGRATION?
familiar
integra;on
model
api
call
dashboard
customer
support

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. dn@paypal.com
@deepak_nadig