1. Booking.com’s main drivers and organisation:
- Two religions: data + experimentation and conversion
- How they make payments a part of the experience, NOT separate function
2. Payment is a product
- Why product department not finance /corporate treasury department should in charge of payments in e-commerce
- Payments are most the sensititive part of the experience
- Merchant acquirer pages are shocking and should be avoided
- Managing the omni-channel payment experience is vital
- What corporate treasury department should be left with.
- Key timing points
- 1:08 Booking.com - basic stats and structure
- 4:50 Key drivers & religions
- 7:00 Conversion - what helps sale
- 9:50 Why payments are in Product Department
- 11:30 Mind shift in e-commerce payments needed
- 12.00 Look and feel of payment pages should be the same as rest of site; do not use ugly acquirer pages
- 16:06 Managing the omni-channel experience
- 19:12 Should finance be in charge of payments?
- 21:20 What should corporate treasury department be left with
CTMfile take: Here is the essence of how payments in e-commerce sites work. The vital drivers and structures to convert browsing into buying. Most corporate treasury departments should accept that e-commerce payments should be in product and NOT under their control.
Like this item? Get our Weekly Update newsletter. Subscribe today