1. Payforit

2. Agenda
 What is Payforit?
 What‟s new in Payforit 4
Break
 Single Click
 Payforit &PhonepayPlus
 Examples

3. What is Payforit

4. What is Payforit?
 Really easy way for people to pay online
 Cost of purchase added to phone bill
 Only works online (web & mobile)
 Get income from smartphone users

5. Mobile network operators
 Produce Payforit scheme rules
 Consistent across all networks
 Work together as the:
“Payforit management group”
 Appoint APIs to enable services

6. Accredited Payment Intermediates
 Implement scheme rules
 Lose API status if they break the rules
 Act independently of merchants
 Trusted by MNOs

7. Why use Payforit?

8. 3 reasons
1. MSISDN Pass through
2. Direct to bill technology
3. Regulatory protection

9. MSISDN Pass through
 MNO passes MSISDN to APIs URL
 Secured to prevent unauthorized use
 Works on 2G/ 3G/ 4G connection
 Not available for Blackberry or Opera
Don‟t need to ask consumer for number

10. MSISDN Pass through rules
 Only after purchase
 Content or service delivery
 Customer support
 Marketing (if opt in)
Not for PSMS or other forms of billing

11. Direct to bill
 Available on Orange, Three, Vodafone
 Currently rolling out on O2
 Granular pricing (eg £1.99)
 Correct VAT handling
 Refunds, crediting, bill descriptions

12. Regulation
 Light touch regulation by PhonepayPlus
 Better clarity for merchant
 Less ambiguity

13. What Payforit won’t do
 Prevent complaints
 „Get out of jail‟ card
 Force businesses to embrace it

14. Payforit 4

15. Payforit 4
 Mobile flow
 Web flow
 Embed flow
 Payforit Single Click
 Marketing messages
 Service Delivery Messages

16. Mobile Flow

17. MSISDN Pass through

18. Branded Unbranded

19. MT Method

20. MO Method

21. MT/MO Hybrid Method

22. Success Error

23. Receipt message Mobile option

24. Web Flow

25. Branded Unbranded

26. Optional API Logos

27. MSISDN Pass through

28. MT Method

29. MO Method

30. Success Error

31. Embed Method

32. Embed for Mobile
200px wide, 120px high

34. 300px wide, 200px high

35. <iframe width=300 height=200 src=URL></iframe>
iFrameTag:
Provided by API

36. MSISDN Pass through

37. MT Method

38. MT Hyperlink

39. MO Method

40. MT/MO Hybrid Method

41. Success Screen
 Payforit Single Click is optional
 Marketing is optional
 Screen is optional if no marketing

42. Error Screen

43. Break

44. Payforit Single Click

46. Payforit Single Click
Merchant
website
Merchant
website
Redirect to API
for billing
API hosts image

47. Initial Purchase 2nd Purchase

48. Initial
Purchase
Next login
Next
purchase

49. Payforit Single Click Button
1. Present the Payforit Single Click logo with a minimum size of 40 pixels wide by 20
pixels high.
2. Present the price and call-to-action no more than 30 pixels apart and with no
overlapping or touching.
1. Present the price and call-to-action in a contrast colour.
o Convert dominate background to HSL (hue, saturation, lightness).
o If the lightness is less than 50%, the text must be white (#FFFFFF). If the
lightness is above 50%, the text must be black (#000000). If the lightness is
exactly 50%, the text may be either white or black.

50. Receipt message
Single Receipt Aggregated Receipt

51. £30 or 90 day spend limit

52. Approval process
 API logs in to Payforituk.com
 Registers merchant
 Default approved in 5 working days
 Custom Button approval by Payforit
Management Group, meets monthly
 Approval revoked if abused

53. Monitoring
 API hosts helpline in receipt messages
 Helpline can direct to merchant
 Monitors call volume

54. Enhanced Payforit
Single Click

55. Enhanced Single Click

56. Cancel purchase
 Consumer may cancel purchase within 10
minutes of most recent selection
 All unbilled purchases are also cancelled
 Marketing permission becomes void if
cancelled
 Consumer may access site again without
restrictions

57. Screen Logging
 API must serve every page viewed
 Page must be retained for 12 months
 API must add all Payforit elements
 API must add pricing & billing links
 API must serve thumbnails

58. MSISDN Aliasing
 API must not pass MSISDN to merchant
 Merchant agrees to forfeit all rights to MSISDN
 Merchant may have a MSISDN alias
 Merchant may market via alias (when opted
in)
 API manages marketing opt in/ opt out
 No PSMS may be marketed

59. Billing & retries
 Only bill full amount shown to consumer
 No split amounts, eg £1.50 + £1.50
 Retries must be inline with MNO policy
 Billing must take place immediately after
cancellation period
 API must ensure only one charge per item
 API must ensure they are not billed for item
already purchased

60. Pricing consistency
 May have multiple prices on selection screen
 (if so, font size must be 14px+)
 Price on content delivery screen must be
same amount or less
 Consumer must return to selection screen to
purchase at a different price point

61. Call logging
 API must record customer care calls
 Call recording must be retained for 3 months
 API must analyse all calls, each week
 If call volume increases by 10%, API must
suspend service and investigate root cause

62. Additional requirements
 Improved receipt message must be used
 Only 1 API redirect between advert and site
 PFI SC opt in must be shown every time
 API must complete a certification assessment

63. Marketing messages

65. Service Delivery Message

66. Service Delivery Message
 Send 1 SMS message
 Sent within 15 minutes
 Direct sales not permitted
 Prompt to return to website

67. Subscriptions

68. Requirements
 Welcome message after signup
 £20 (inc VAT) or monthly reminder text
 API managed STOP command
 API must bill subscription
 PPP Apprvoal when £4.50+/wk

69. Customer Service

70. Requirements
 Refunds without unnecessary hurdles
 9-5 telephone support (VM out of hours)
 Respond in 1 day, resolve in 2 days
 English speaking UK helpline

71. Payforit
&PhonepayPlus

72. About PhonepayPlus
 UK regulator for premium rate services (PRS)
 PRS includes payment on a phone bill
 PPP regulate promotion, operation and content
 Regulates MNOs, APIs & Merchants

73. Why Regulate?
 All payment services in UK are regulated
• FSA or OFCOM
 Past issues destroy consumer trust
• Subscriptions
• Voting
 Fair charging creates equal opportunities

74. Payforit Regulation
 Define as a Controlled Premium Rate Service
 PhonepayPlus recognizes that Payforit is
capable of lessening consumer risk
 PhonepayPlus sits on Payforit Management
Group to provide appropriate input
 PhonepayPlus statement on regulation of PFI

75. Payforit and the Code
Payforit provides assistance with:
 Transparency and Pricing
 Some scenarios around Fairness
 Consumer consent to charging
 Privacy - consent to market

76. Payforit and the Code (2)
Payforit cannot help with:
 Misleading info before payment screen
 Bill shock unless reminders sent
 Inappropriate marketing (e.g. to children)
 Legality (Section 2.1) and Avoidance of Harm

77. Complaints
Complaints referred to the merchant when:
• No immediate indication that Payforit used incorrectly
• No indication of significant, or trending, consumer harm
 MNO may be contacted to establish merchant
 Dissatisfied consumers can be referred to PPP

78. Prior Permission
Some categories of PRS require written permission
before providers can operate them:
Current list includes:
• Subscription over £4.50 per 7 days
• Consumer credit services
• Multi party chat
• Remote gambling
Full list at: http://www.phonepayplus.org.uk/For-Business

79. Registration of services
 Services must be registered with number checker
to reflect how they are described by MNOs to
consumers
 Allows many parties to quickly identify the merchant
involved from the bill descriptor
 MNOs have differing descriptions - work in
progress

80. Payforit 4.1

81. In App billing
 Ideal for App stores (exciOS)
 Intuitive user experience
 Currently in trial

82. Payforit Certification

83. Modify user experience
 For scenarios when PFI doesn‟t fit
 Can take amendment to PFIMG
 MNO review and provide feedback
 If accepted, available to all

84. Case Studies

86.  UK‟s #1 flat sharing website
 Someone finds a flat mate every 3 mins
 Freemium model
• Pay to view landlord details early
• Pay to boost your advert
Spareroom.co.uk

87. Early bird upgrade

88. Payforit Payment

89. Payment Completed

90.  50% more people than Paypal
 168% increase when using Payforit 4
 87% people make a payment
 17% make a repeat purchase
Service Revenue

91. Virgin train WiFi

92. Paying by card
 Security issue with people watching
 Not a great experience on a train
 Business users more likely to use phone

94. Results
 Most popular option
 73% make a purchase
 20% repeat purchases

95. Keep in touch
Chris@ImpulsePay.com
0207 099 2450
@CN_UK