Adaptive Payments API allows you to send money in various ways , from simple to complex . For example, you can create a small application to send money in social networks or stable payment system.
Adaptive Payments processes payments between their sender and one or more recipients. You – the owner of the application (trader who owns a website , the owner of the widget in the social network , provider payment applications on mobile phones , etc.). Your application – a subscriber adaptive payments.
With many applications, you can be the owner of the application , and the recipient. For example, as the owner of Website , you are the recipient of payments from senders ( your customers ) . The following diagram shows the relationship between the sender , you as the beneficiary , and PayPal:
You do not have to be the recipient. For example, if you own a “shopping basket”, you do not need to receive payments directly. You can organize the passage of payment from the sender to the recipient, who actually sell the product. The following diagram shows the relationship between the payer, you as the owner of the application that sends payments to the recipient, and PayPal:
The diagram shows the payment which the payer sends multiple recipients parallel payments. With such parallel payment transaction can see the sender for each address.
The following diagram shows the relationship between the sender, you as the owner of the application that sends a payment to recipients and PayPal payment in the chain:
In the chain, it sends the primary payer payment payee, of which the primary beneficiary pays secondary recipients. Payer only known primary recipient, but no known secondary. Secondary recipients know only the primary beneficiary, but not the sender.
The following diagram shows the relationship between you as the sender, and the owner of the application that sends payments to recipients:
For example, you can use this configuration in applications sales commission that trafficked means for commissions from your account on your account sales managers.
Simple Parallel Chain and payments
Adaptive Payments provides several types of payments : simple, parallel and chain . Each of these types , you can create using PayAPI.
Simple payments allow the payer to send a single payment to a single recipient. For example, your website can use Adaptive Payments system to transfer money from the sale to the PayPal account of your client on your own. This is the traditional method.
Parallel payments allow the payer to send one payment to multiple recipients. For example, your application can be a “shopping basket”, which allows the buyer to pay for goods from several merchants with one payment. Your “basket” collects the payments to vendors who sell products directly. PayPal then withdraws money from the account of the payer and places them on the account of the recipient.
Continued payments allow the payer to send a separate payment to the primary recipient. The primary recipient of the payment and keeps the secondary recipient pays the remainder. For example, your application may be an online travel agency , which draws air ticket booking, hotels and car rentals. Payer sees only the primary beneficiary . You get a transfer, including payment services , which represent a third party , and your commission . PayPal withdraws money from the account and places them in your account and accounts for secondary recipients .
Approval of payment
Sender must approve payment. He can do it on paypal.com, selecting the appropriate method of approval : each payment individually previously or if the sender – is your application indirectly approve payments .
There are 3 methods of payment approval :
Direct approval of the payment when the payer comes into your account at paypal.com, to approve each payment. Payments approved directly – is a familiar operation on PayPal. This is the only option , unless the payer has not set the prior approval of the agreement on or you , the user API, also a payer.
For pre-approved payments sender comes to PayPal and pre-approval establishes subsequent payments or sets preliminary approval in the ” inserted ” stroke order of payment.
Sender comes to paypal.com once to set prior approval. Once the sender agrees to prior approval , additional approval is no longer necessary .
Indirect approval of payments , it is necessary , when your application is the sender and payment, and the subscriber Adaptive Payments PayAPI. In this case, PayPal makes payment from your own account , which reduces the need for approval.
Resolution on services Adaptive Payments
Services there are two categories: standard , does not require a special permit for use , and advanced , which require approval by PayPal. You can request approval for use of the service by request in PayPal.
You can use standard services without special permission :
- the use of simple or parallel payments that require direct approval of the sender.
- Making a simple parallel or payments that require direct approval of the sender.
- receipt of payment details.
- committing refund.
- committing the currency conversion.
The direct payment approval
To express approval of payment need to go to paypal.com for approval of payment. You can check the connection between your application and PayPal, pointing to redirect links in different situations.
The following diagram shows the standard stroke control of payment ( such as payment of goods in the basket from the online store ) , which requires that the sender has approved payment via paypal.com:
Prior approval of the payment process
Prior approval for payment sender must go paypal.com, to establish a payment agreement with a particular vendor .
You can check the connection between your application and PayPal, indicating a link to redirect to different situations.
Payer comes to paypal.com, establishes prior approval , which includes setting the following details:
duration of prior approval.
the maximum possible amount of pre- approved.
the maximum number of payments.
The following diagram shows the standard stroke control payment with prior approval :
Indirect approval process payments
Indirectly approved payments – these are payments in which the sender and the API caller using the same account. Since PayPal removes amounts for payments from your own account, there is no need for approval, and there is no visible process for indirect approval as such.
The following diagram shows a typical process control during operations indirect approval of payments:
Built-in payment – a payment that initiates a visual representation of the process of Adaptive payments when the sender does not seem to go away from the page ” on the cash” or “payment” . Built simplify payments paid to the sender because PayPal can allow him to skip the login and password .
Types of embedded payments
Built payments may include :
- simple payments ;
- parallel payments ;
- continued payments .
You can also allow pre-approval for future payments or allow shipping address associated with integrated delivery.
Fundamentals of implementing embedded payments
To implement a process embedded payments , you must
preferred to run the built- payment process , which is either an advertising banner (lightbox) or mini- browser and redirects the browser to the address of the payer PayPal, which supports embedded payments , namely www.paypal.com/webapps/adaptivepayment/flow/pay?paykey = ..
Configuration fees payments
You can set the transaction in a way that pays a fee for transfer sender or recipient . If the recipient pays the commission , then you can set the primary payer commission or recipient or all recipients pay part of the commission .
So We Have tried to cover everything, Anything left ?
Comment below your query.
Comment below your query.