2. Over thirty years technical, commercial and management experience in the supply of
payments including online, mobile payments, point of sale, general payment systems
and fleet systems including practical fraud experience across all platforms.
Spearheaded numerous new market entry strategies, new office set-up, in new regions
including SA, LATAM & China. Also completed extensive fund raising exercises and
M&A activity.
A payments expert and has held roles as CEO, MD, Director, Business Development /
M&A & most recently Regional Director LATAM
Holds a stake in a number of start ups and currently looking at launching a new PSP -
Lionpay
Nick Walker
3. â˘âŻ What are the challenges for developers of mobile apps
and websites when choosing a payments system?
â˘âŻ What payment types do you need to offer / accept
in certain regions?
â˘âŻ What functionality do you need and why do you want it?
Choosing an Online Payment Provider
4. System
 Needs
Â
â˘âŻ High
 availability
Â
â˘âŻ Merchants
 want
 100%
Â
â˘âŻ No
 single
 point
 of
 failure
Â
â˘âŻ If
 fail,
 hot
 switch
 over
Â
â˘âŻ Resilient
 and
 recoverable
Â
â˘âŻ Data
 is
 money
Â
â˘âŻ Secure
Â
â˘âŻ No
 risk
 of
 compromise
Â
 of
 data
Â
â˘âŻ Fraud
 free
Â
â˘âŻ High
 performance
Â
â˘âŻ Sub
 second
 response
 Fmes
Â
â˘âŻ Upgradeable
Â
â˘âŻ New
 interfaces
Â
â˘âŻ New
 technologies
Â
Business
 Needs
Â
â˘âŻ Increase
 revenue
 and
 proďŹtability
 â
Â
how?
Â
â˘âŻ Cross
 border
 mulF
 region
Â
â˘âŻ AccepFng
 all
 payments
Â
â˘âŻ AccepFng
 more
 genuine
 business
Â
â˘âŻ IdenFfying
 and
 protecFng
 genuine
Â
customers
Â
â˘âŻ Improving
 customer
 experience
 to
Â
generate
 repeat
 spend
Â
â˘âŻ Improving
 business
 operaFons
Â
â˘âŻ Easily
 adapFng
 to
 changing
 business
Â
models
Â
Card
 vendors
Â
Fraud
 vendors
Â
Credit
 bureau
Â
Alterna7ve
Â
payments
Â
Associa7ons
Â
Issuer
Â
Consumer
Â
Merchant
Â
Gateway
Â
Acquirer
Â
Who are the Payment Stakeholders?
What
 are
 their
 needs?
Â
5. Typical mCommerce user experience
Payment
 iniFated
 Payment
 in
 progress
Â
Merchant
 app
 Merchant
 app
Â
Payment
 successful
Â
mobile.connect
Â
The
 shopper
Â
proceeds
 to
 payment
Â
The
 shopper
 selects
 a
Â
payment
 method
Â
The
 shopper
 enters
Â
the
 payment
Â
informaFon
Â
The
 payment
 is
Â
processed
Â
The
 shopper
 receives
Â
a
 receipt
Â
6. Typical Transaction Flow
3
Choose
 the
 service
Consumer
Â
PSP
Â
Â
Acquire
 bank
Â
Merchant
Â
Â
Send
 the
 requirement
 of
 deducFon
Â
2
1
4
oďŹer
 the
 service
8 Result
 of
 payment
Â
7
Send
 the
 result
 to
Â
merchant
Input
 the
 credit
 card
 info
3-ÂâD
Â
Secure
Â
5
6
9
Send
 the
 pay
 order
Issuing
Â
 bank
Â
7. Past solutions
Server side API â (HTML over HTTP)
â˘âŻ
 Merchant
 has
 to
 provide
 the
 payment
 page
 â
 re-ÂâinvenFng
 the
 wheel
Â
â˘âŻ
 Merchant
 has
 full
 control
 over
 the
 layout
Â
Â
â˘âŻ
 Merchant
 touches
 the
 credit
 card
 data
 and
 must
 be
 PCI
 compliant
Â
â˘âŻ
 IntegraFon
 Fmeline
 weeks
 to
 months
Â
Provider hosted payment page
â˘âŻ
 Re-Ââuse
 and
 convenience
 â
 works
 out-Ââof-Ââthe-Ââbox
Â
â˘âŻ
 Limited
 control
 over
 layout,
 opFons
 and
 workďŹow
Â
â˘âŻ
 IntegraFon
 Fmeline
 â
 days,
 weeks
Â
New approach
Merchant-hosted payment page, embedding a ready-made JavaScript payment
component
â˘âŻ
 Re-Ââuse
 and
 convenience
Â
â˘âŻ
 Gives
 full
 control
 to
 the
 developers
Â
â˘âŻ
 Solves
 PCI
 problem
Â
â˘âŻ
 IntegraFon
 Fmeline
 hours
 -Ââ
 days
Â
Â
Payment Integration has moved onâŚ
8. Merchant provides and controls surrounding page
Ready-made JavaScript widget comes from the provider
Widget honors CSS (Cascading style sheets) of the surrounding page, so it adapts to the layout
When the shopper pays, the widget securely sends the credit card data to the provider
Provider sends back a secure token
Component sends payment request with token but no card data
Merchant can refer to the payment using the secure token
New solutions: How do they work?
Merchant
Â
Server
Â
Provider
Â
Â
Server
Â
Payment
 Page
Â
Â
Â
Â
Â
Â
Â
Â
JS
Â
Component
Â
9. Understanding the clients needs
â˘âŻ Products, type and number
â˘âŻ Consumer demographics
â˘âŻ Regional cover â language and currency
â˘âŻ Time to marketsaid
Building & protecting developers reputation
â˘âŻ Security of payment systems
â˘âŻ Ease of integrating payment modules into OpenSource systems
â˘âŻ Ease of setting up between bank source and payment system for financial
transactions
â˘âŻ Need for high performance and availability
Ongoing support
â˘âŻ Technical and business
â˘âŻ Familiarity of payment system (marketing, existing clients)
â˘âŻ Speed of payments, support by provider
â˘âŻ Adoption of new payment types and channels
What are the challenges for m commerce developer and
payments?
Said
 that
 fraud
 can
 be
 x4
Â
1mes
 higher
 via
 mobile
Â
channel
Â
10. Dimension 1:
Is Easy, convenient, customisable, works out-of-the-box â
technically and commercially
Dimension 2:
Supports full breadth of payment methods
Dimension 3:
Supports full breadth of channels (omni-channel)
Shop for a three dimensional payment solution that...
11. Prevalence of payment types vary country on country
Need to ensure optimal conversion
What Payment Methods?
International
France
Netherlands
UK Germany
Denmark
Japan
Korea
China >30
??
Sing
MerchantMerchantShopper
12. Support all channels â Omni Channel
â˘âŻSeamless one time integration
â˘âŻSingle backend, control panel and consolidated reporting
â˘âŻEase of addons - payments, channels, 3rd party applications.
â˘âŻOne payment provider not multiple
Support all payments not just credit
â˘âŻMainstream and alternative
â˘âŻMulti region, multi currency, multi language
Fast, safe and secure
â˘âŻHigh speed response times
â˘âŻIntegrated fraud prevention services
â˘âŻContracted up times
Commercial recognition for target audience
â˘âŻFast sign for start ups â hours/days not weeks
â˘âŻMinimal if any contractual commitment
What functionality do you need and why do you want it?
13. Omni Channel Payment processing
Omni-Ââchannel
 plaBorm
Â
eCommerce
 mCommerce
Â
mPOS
 MOTO
Â
h_ps://tompays.test.ctpe.info
Â
Â
14. Ensure provider supports fast sign up and support the respective merchant type
category and period in business
Not just technical selectionâŚ.
15. In summaryâŚâŚ.
Make sure of a match with clients current and future needs
Regional
 coverage
 and
 payment
 types
 â
 who
 is
 the
 target?
Â
Just
 Visa/MasterCard
 will
 be
 shortsighted
 and
 limiFng
Â
Add
 value
 -Ââ
 think
Â
 for
 the
 client
 â
 increase
 your
 value
Â
Take an omni-channel approach
One
 placorm
 supporFng
 all
 channels
 giving
 a
 seamless
 experience
Â
Seek fast development with proven sample code and process
Sandbox
 development
 tool
 kit
Â
Online
 test
 and
 validaFon
Â
Â
Ensure highly secure, high availability and fast response times with a fraud
management focus
Build
 and
 protect
 your
 reputaFon
Â
Verify ongoing support needs and enhancements
Low
 maintenance
 but
 opportunity
 for
 repeat
 business
Â
Validate the sign up process for the merchant in terms of viability and timeline
Be commerce driven not just technicalâŚâŚ..
Choosing an Online Payment Provider âŚ.