payment screens and the checkout pipeline
TRANSCRIPT
Payment screens and the checkout
pipelineSebastien Mirolo
Put what I say in context
The business:- Software-as-a-Service- selling up-time- period basis
Me:- Engineer at heart- Marketer by choice- Accountant by necessity
Let’s start simple
… is it that simple?
Pricing and Payment pages
Most simple: details
- Is the subscriber logged in?
- Redirect through the registration page?
- Do we support a shopping cart functionality?
Payment page layout
Credit CardInformation
OrderDetails
ConfirmButton
- Phone number?- Chat Window?
- Minimal or full menu bar?- Opportunity to remove items?
- Save credit card on file?- Ask even when total is zero?
ReceiptsMore receipts format,
the better.UX considerations
- Where to after receipt?- Liabilities and balances?Backend considerations
- What about chargebacks?
- Log IP, Browser, etc.?- Keep log files for 90
days?
Grand opening!
… clearly not done with the checkout pipeline
Discounts! Genius!
- Unintended side effect?- Unintended use?
Redeem, pricing, checkout.
How to present priceswith/without discount applied?
Backlog is good.A bit of accounting:
cash flow and income recognition
Redeem, pricing, advance periods, checkout.
Euh, wait…- How do discounts combine?- Same price for 3 and 6 months subscriptions?- Pay for 6 months, but free for 12 months?
But we are not done…
- Group buy?- Separate buyer vs. subscriber?- Buy on behalf of (un-)registered user?
B2B vs. B2C
- Which customer support rep has access to what?
- Pro-rating and charging interests?
- a lot more…
There is more…(… but it will next time)
Real life examplesfrom
github.com/djaodjin/djaodjin-saasThank You
Sebastien Mirolo@seabasscapoeira