Anyone interested in E-commerce can use this (not bound to any language or framework). This can be used as a solution where there is a need for a 2 way payment solution. Like in many E-commerce website we collect money from buyers and need to pay it to the dealers. Also in iPhone games or business solutions money is collected from some accounts and then credited to other accounts.
4. AGENDA
→ Embedded payments
→ Fee Payment Configuration
→ Applications use cases
→ API integration & Demo
→ How to make your App live?
Presenter: Supriti Panda, Mindfire Solutions
5. Why Adaptive Payment?
→ Build a small send money application for a social
networking site.
→ Traditional merchant website with a slight variation.
→ Build a Multi-merchant website.
Presenter: Supriti Panda, Mindfire Solutions
11. → Buyer makes a payment on a merchant’s website.
→ Buyer makes a single payment for a cart of items from
the same merchant.
→ Person on a social networking site makes a payment
for a purchase to the receiver.
→ A sender sends money to pay for lunch at a restaurant.
Basic Payment Use
Presenter: Supriti Panda, Mindfire Solutions
13. → A single payment for multiple items from different
merchants.
→ Purchases of items related to an event, such as a trip
that requires airfare, car rental, and a hotel booking.
Parallel Payment Use
Presenter: Supriti Panda, Mindfire Solutions
15. → Chained payments are useful in cases when the primary
receiver acts as an agent for other receivers.
→ The sender deals only with the primary receiver and
does not know about the secondary receivers, including
how a payment is split among receivers.
→ You have at most one primary receiver and 1-5
secondary receivers.
Chained Payment Use
Presenter: Supriti Panda, Mindfire Solutions
16. Delayed Chained Payment
Presenter: Supriti Panda, Mindfire Solutions
→ You can choose to delay a payment to a secondary
receiver.
→ As primary receiver, you may require secondary
receivers to perform some action, such as shipping
goods or waiting for expiration of a return period,
before making payment.
→ To complete the payment, you must explicitly execute a
payment to secondary receivers after the sender pays
you.
→ The payment must occur within 90 days, after which
you cannot complete the payment as part of the
original chained payment.
21. Embedded Payments
Presenter: Supriti Panda, Mindfire Solutions
→ An embedded payment is a payment that initiates a visual
presentation of the Adaptive Payments payment flow in
which the sender appears to never leave your checkout or
payment page.
→ The payment flow can be embedded as a lightbox on your
web page.
→ The payment flow can appear in a mini browser in your
webpage.
→ The payment flow can be embedded as a lightbox in an
iFrame on your webpage.
22. Fee Payment Configuration
→ Sender Pays the Fee
→ Receiver Pays the Fee in a Parallel Payment
→ Each Receiver Pays the Fee in a Chained Payment
→ Primary Receiver Pays the Fee in a Chained Payment
Presenter: Supriti Panda, Mindfire Solutions
23. Adaptive Payments Service Permissions
→ Standard services
- Making simple or parallel payments with explicit
approval of the sender.
- Getting payment details.
- Making refunds.
- Performing currency conversions.
→ Advanced services
- Chained Payment
- Implicit approval
Presenter: Supriti Panda, Mindfire Solutions
24. Application Use cases
Presenter: Supriti Panda, Mindfire Solutions
1. Accepting Payments for Online Content, like music or video
2. Accepting Payments for Online Game Subscriptions
3. Accepting Payments for Usage
4. Accepting Shared Payments and Group Gifts
5. Creating and Using Virtual Currencies
6. Distributing Payroll Online
7. Distributing Rebate Payments Online
8. Enabling Fund Transfers within a Group
25. Application Use cases
Presenter: Supriti Panda, Mindfire Solutions
9. Encouraging Online Gift-Giving
10. Managing a Storefront for Physical or Digital Goods
12. Managing Business Payments
13. Providing Vouchers for Local Businesses
14. Selling Digital Goods on a Website
27. API Integration
→ Fields required in the API:
9. senderEmail
10. sender.accountId
11. preapprovalKey
12. pin
→ The Classic APIs needs api_username, api_password,
api_signature, app_id
→ You can download the Adaptive payment SDK, present
in different languages from here:
http://paypal.github.io/sdk/#adaptive-payments
Presenter: Supriti Panda, Mindfire Solutions
29. How to make your App live?
Presenter: Supriti Panda, Mindfire Solutions
→ Account status - Login to PayPal, go to your PayPal
Profile and click My settings. Confirm that your Account
type is either Premier or Business, or upgrade your
account.
→ Check your API settings. Click My selling tools. Expand
Selling online if needed and check API access.
→ Test your integration using the PayPal Sandbox, as
described in Testing Classic API Calls. For sandbox the App
ID:APP-80W284485P519543T
→ To go live with your application, follow the submission
steps outlined in Going Live with Your Application.