Monetizing your Applications with PayPal X Payments Platform
•
3 likes•1,366 views
This document provides an overview of monetization models, PayPal payments, and the PayPal X Payments Platform. It discusses various payment methods like credit cards, debit cards, and bank accounts. It then describes the Adaptive Payments API and how it can be used to enable different payment types and scenarios like social networking payments, gaming payments, payouts, and more. It also outlines the development process including using sandbox accounts, getting API credentials, and going live.
Recommended
More Related Content
What's hot
What's hot (13)
Viewers also liked
Viewers also liked (15)
Similar to Monetizing your Applications with PayPal X Payments Platform
Similar to Monetizing your Applications with PayPal X Payments Platform (20)
More from PayPalX Developer Network
More from PayPalX Developer Network (18)
Recently uploaded
Recently uploaded (20)
Monetizing your Applications with PayPal X Payments Platform
- 1. Monetizing your ApplicationswithPayPal X Payments Platform Praveen Alavilli Developer Evangelist PayPal X Developer Network @ppalavilli
- 2. Agenda Monetization Models A quick overview of Payments PayPal X Payments Platform Adaptive Payments Development Process
- 6. Pay as you use
- 7. Free to use, pay to Services
- 8. Freemium
- 10. What are Payments anyway ? exchange of value from one party to another As a developer, the sender and receiver may have many different names, depending on their role and objective.
- 12. different technology to interfaceAs a developer, you select the forms of payments that best fit your application and target the consumer experience.
- 13. Credit Cards usage of the card is authorized by the issuer in real time PaymentSystem Acquirer Issuer Consumer Merchant
- 14. How the Money moves authorizations are captured immediately and settled in batch PaymentSystem Acquirer Issuer Consumer Merchant
- 15. Chargebacks Consumers have the right to chargeback transactions. PaymentSystem Acquirer Issuer Consumer Merchant
- 16. Chargebacks Consumers have the right to chargeback transactions. The funds are withdrawn from the merchant’s account and credited to the consumer’s account. PaymentSystem Acquirer Issuer Consumer Merchant
- 17. Debit Cards PaymentSystem Acquirer Issuer Consumer Merchant
- 18. Debit Card differences PaymentSystem With debit cards, processed as a debit card, the authorization transaction and the settlement (capture) transaction are the same. Money movement is in real time. Acquirer Issuer Consumer Merchant
- 19. Bank Accounts & ACH PaymentSystem ODFI RDFI Consumer Merchant
- 20. PaymentSystem With Automated Clearing House (ACH), there is no authorization transaction. Money movement is batch. ODFI RDFI Consumer Merchant Bank Accounts & ACH
- 21. Do I really need to worry about these ?
- 23. Manage Accounts
- 25. While taking care of Risk and Fraud Management Security Compliance Settlements Refunds/Charge backs
- 27. Split payments
- 28. Bill payments
- 29. Payroll payments
- 30. B2B payments
- 31. Remittances
- 34. Points and miles
- 35. Mass payments
- 36. Invoice payments
- 39. Money transfers
- 48. Pre-approved payments (with PIN)
- 51. SEND MONEY Basic building block allows merchants to transfer money from one entity to another
- 53. Allows an API caller to make payments on behalf of a sender within the constraints specified
- 54. PIN optional for future payments made within the authorized amountC Pre Approval
- 56. Future interactions with each transaction can be separate
- 57. Enable partnership opportunities₤10 ₤100 ₤40 Sender Visibility ₤50
- 60. COMBINE AND C Pre Approval
- 63. So what can I do with Adaptive Payments?
- 67. You can design a payment solution using Adaptive Payments.Primary
- 70. You can design a payment solution using Adaptive Payments.OR Primary
- 72. You can design a payment solution using Adaptive Payments.Primary
- 75. PAYMENT APPROVAL: WEB MODULE 1. Login Payment Confirmation 2. Review Your Payment 3. Redirect
- 76. API WEB UseCase Sender Business Send money Implicit send money Pre-approved payments (with PIN) Split payments: chained Pay API Pay Key Redirect User to PayPal Return URL 41 Redirection URL= www.P_Mart.com/apstore IPN= https://ww.P_Mart.com/IPN Sender Email: john_m@mail.com Receiver Email: Business@P_Mart.com Redirect Confidential and Proprietary 41 Notification Confidential and Proprietary 41
- 77. API WEB UseCase Sender Photographer Send Money Implicit send money Pre-approved payments (with PIN) Split payments: chained Pay API Pay Key 42 42 User Name = P_Mart_admin.api Amount = 2000 Password = keep$secret Currency = USD Signature = 23KJHO5AS09I32SDROR Fee Paid by = Sender Sender Name = Business@P_Mart.com Receiver email = Photographer1@mail.com IPN= https://www.P_Mart.com/IPN Sender Email: Business@P_Mart.com Receiver Email: Photographer1@mail.com Request Notification Paykey = AP-234DEF95GAT230BET Status = Complete Response
- 78. API WEB WebGames UseCase Sender Receiver Send Money Implicit send money Pre-approved payments (with PIN) Split payments: chained PreApproval PreApp Key Redirect User to PayPal User Name = WebGames_admin.api Amt. per Payment = 100 Password = keep$secret Max. Number of Payments = N/A Signature = 23KJHO5AS09I32SDROR Payment Period = N/A User Email = john_m@mail.com Max. Payments per Period = N/A Expiration Date = 12/30/2009 Day of Period = N/A Starting Date = 11/05/2009 Return URL = www.WebGames.com/apstore Max. Amount = 1000 Cancel URL = www.WebGames.com/home PreApproval Key = PA-84HK2A57FCOP3RW Request PreApproval Key = PA-84HK2A57FCOP3RW Response Redirect User Confidential and Proprietary 43 Confidential and Proprietary 43 Pre-approved Payment AgreementSign-Up
- 79. 1. Login PRE-APPROVAL: WEB MODULE 2. Review Your Payment 3. Redirect
- 80. API WEB WebGames UseCase Sender Receiver Send Money Implicit send money Pre-approved payments (with PIN) Split payments: chained PreApproval PreApp Key Redirect User to PayPal Return URL IPN= https://ww.WebGames.com/IPN Sender Email: john_m@mail.com Receiver Email: GameDeveloper@paypal.com Notification Pre-approved Payment AgreementSign-Up
- 81. API WEB UseCase Sender Rental App Send Money Implicit send money Pre-approved payments (with PIN) Split payments: chained Pay API Pay Key Redirect User to PayPal Return URL User Name = Rental_admin.api Secondary Receiver [2] = Sec Receiver_2@mail.com Password = keep$secret Amount = 50.00 Signature = 23KJHO5AS09I32SDROR Tracking ID = 234235986 Sender Email = john_m@mail.com Cancel URL = www.PayRent.com/home Currency = USD Return URL = www.PayRent.com/apstore Primary Receiver [0] = Prim Receiver@mail.com Amount = 1000.00 Secondary Receiver [1] = Sec Receiver_1@mail.com Amount = 40.00 Request IPN= https://www.Rental.com/IPN Sender Email: john_m@mail.com Receiver Email: PrimReceiver@paypal.com Pay Key = PA-84HK2A57FCOP3RW Response Notification Confidential and Proprietary 46 Confidential and Proprietary 46
- 82. Development Process Submit for application review Get API credentials Go Live Design and build application Create Sandbox account Get APP ID Signup on x.com
- 83. X.Com – Developer Portal
- 85. SDKs and Sample code
- 86. Forums – non-moderated content
- 87. Blogs – PayPal and developers
- 88. Connected with PayPal Site
- 89. Docs rating and commenting
- 90. Instant feedback from developers
- 91. Videos
- 93. Manage Sandbox API Credentials
- 94. Monitor Sandbox payment confirmation emails
Editor's Notes
- building and running an app is cheap buta successful and profitable company needsGood Monetization Strategyunfortunately most of the monetization techniques that people talk about rely heavily on advertisingAffiliate programsBanner adsBlog advertisingContextual adsInterstitial adsIn-text contextual adsCPA/CPC/CPMPaid Blog PostsLead GenerationRSS adsDataSurveys/Polls
- A subscriptions model is where you charge your customers a flat membership fee (often charged weekly, monthly, yearly, or for lifetime) to use your application, services, or content. A pay as you use model is where you charge your customers based on the usage of your application - time, content, resources used, etc. without a fixed flat fee. Amazon Web Services (AWS) is a good and very successful example of Pay only for what you use. A free to use, pay to Services model is where you provide your application for free but charge your customers for services like customization, training, and other value added services. A good example are the companies that provide value added services for the Open Source software (ex. Linux Operating System, Drupal, MySQL, Java, etc.). A freemiummodel is where you give away a basic version of your application for free and charge your customers for an enhanced version of your application that provides more extended feature set or content. There are several good examples of using the freemium model in the industry. Flickr, Skype, Newsgator, Trillian, Google App Engine, etc.. And last but not least the traditional eCommerce model which is usually about selling of products (digital/physical) online through your applications. Obviously we are not talking about selling products at the scale of big retailers (like Amazon & Walmart) out there, but most of the applications could provide ways for it’s customers to buy products (digital or physical) that are related to the application or content or services it is offering. A good example is a social gaming application that could provide merchandise like T-Shirts, Coffee mugs, Photo frames, etc.. with it’s brand name on it. As your application grows it’s audience base and, as it’s brand becomes more known among customers – you can generate revenue based on your brand in this way too. in most cases the monetization model really depends on what your application is providing. Also in some cases it is very important (as your monetization strategy gets more closely bound to the functionality – for example as in the pay as you use model where you would want to keep track of everything the customer is doing) to start thinking about the way you are going to monetize in the future during your application design and implementation phase itself. Otherwise you might be forced to redesign and/or re-implement your application when the times comes to turn the monetization switch on. And when you add different platforms, and devices on which your application is being offered, it would obviously turn into a very costly affair.
- Another important aspect of monetization, as you might guess, is the payments platform itself. There are several online payments platforms and solutions available out there in the industry and it becomes vital to choose one that not only provides the payments functionality in the way that you would want but also is economical in terms of the transaction and monthly fees.
- Not really – fortunately there are payment platforms out there that hide all the complexities for developers like you and me. PayPal X Payments Platform is one such platform that empowers developers to successfully monetize their applications in many different ways.Consumers, businesses, merchants, sellers, buyers, etc….
- enabling