Developer's Guide

Introducing Adaptive Payments
Payment Approval
22 August 7, 2012 Adaptive Payments Developer Guide
In this example, the primary receiver receives $100 from the sender’s perspective. The
primary receiver actually receives only $10 and passes a total of $90 to secondary receivers,
Receiver 2 and Receiver 3.
NOTE: This scenario is an example only and does not take PayPal fees into account.
Delayed Chained Payments
By default, payments to all receivers in a chained payment are immediate. However, you can
choose to delay a payment to a secondary receiver. For example, 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.
Payment Approval
The sender of a payment must approve the transfer. The sender can log in to paypal.com to
approve each payment, preapprove payments, or when the sender is your application, be
implicitly approved to make payments.
NOTE: Preapproval requests require permission from PayPal.
There are 3 kinds of payment approvals:
 Explicit approval payments, in which the sender logs in to paypal.com to approve each
payment.
Explicitly approving payments is the traditional way to pay with PayPal. This method is the
only option unless the sender has set up a preapproval agreement or you, the API caller, are
also the sender.