Developer's Guide
Table Of Contents
- Adaptive Payments Developer Guide
- Contents
- What’s New?
- Introducing Adaptive Payments
- Adaptive Payments Actors and Objects
- Simple, Parallel, and Chained Payments
- Payment Approval
- Adaptive Payments Service Permissions
- Explicit Approval Payment Flow
- Preapproved Payments Flow
- Implicit Approval Payments Flow
- Embedded Payments
- Embedded Payment Flow Presentations
- Kinds of Embedded Payments
- Embedded Payments Implementation Basics
- Embedded Payment Experience
- Preapprove Future Payments Checkbox
- Shipping Address Information
- Embedded Payment Experience
- Setting Up Web Pages to Invoke the Embedded Payment Flow Using a Lightbox
- Setting Up Web Pages to Invoke the Embedded Payment Flow Using a Minibrowser
- Displaying and Collecting Shipping Addresses
- Guest Payments
- Fee Payment Configuration
- Getting Started
- Pay API Operation
- PaymentDetails API Operation
- ExecutePayment API Operation
- GetPaymentOptions API Operation
- SetPaymentOptions API Operation
- Preapproval API Operation
- PreapprovalDetails API Operation
- CancelPreapproval API Operation
- ConvertCurrency API Operation
- Refund API Operation
- GetFundingPlans API Operation
- GetShippingAddresses API Operation
- Adaptive Payment Commands and Redirects
- Instant Payment Notifications
- Older Versions of the Adaptive Payments API
- 1.8.0 Features
- 1.7.0 Features
- 1.6.0 Features
- New API Operations for Version 1.6.0
- Changes to PayRequest Fields for Version 1.6.0
- Changes to PayResponse Fields for Version 1.6.0
- Changes to ExecutePaymentRequest Fields for Version 1.6.0
- Changes to GetPaymentOptionsResponse Fields for Version 1.6.0
- Changes to SetPaymentOptionsRequest Fields for Version 1.6.0
- Changes to PreapprovalRequest Fields for Version 1.6.0
- Changes to Address Structure for Version 1.6.0
- Changes to DisplayOptions Structure for Version 1.6.0
- New CurrencyConversion Structure for Version 1.6.0
- New InvoiceData Structure for Version 1.6.0
- New InvoiceItem Structure for Version 1.6.0
- New SenderOptions Structure for Version 1.6.0
- New SenderIdentifier Structure for Version 1.6.0
- New AccountIdentifier Structure for Version 1.6.0
- New ReceiverOptions Structure for Version 1.6.0
- New ReceiverIdentifier Structure for Version 1.6.0
- Additional Error Messages for Version 1.6.0
- 1.5.0 Features
- 1.4.0 Features
- 1.3.0 Features
- 1.2.0 Features
- 1.1.0 Features
- Revision History
- Index
Adaptive Payments Developer Guide August 7, 2012 73
3
Pay API Operation
Use the Pay API operation to transfer funds from a sender’s PayPal account to one or more
receivers’ PayPal accounts. You can use the Pay API operation to make simple payments,
chained payments, or parallel payments; these payments can be explicitly approved,
preapproved, or implicitly approved.
Pay Summary
Create your PayRequest message by setting the common fields. If you want more than a
simple payment, add fields for the specific kind of request, which include parallel payments,
chained payments, implicit payments, and preapproved payments.
Common Fields for All Payments
For each kind of payment, you must specify values for the following fields:
Field Description
actionType The action for this request. Possible values are:
PAY – Use this option if you are not using the Pay
request in combination with ExecutePayment.
CREATE – Use this option to set up the payment
instructions with SetPaymentOptions and then
execute the payment at a later time with the
ExecutePayment.
PAY_PRIMARY – For chained payments only, specify this
value to delay payments to the secondary receivers; only
the payment to the primary receiver is processed.
receiverList.receiver(0).email A receiver’s email address
receiverList.receiver(0).amount Amount to be credited to the receiver’s account
currencyCode The code for the currency in which the payment is made;
you can specify only one currency, regardless of the number
of receivers
cancelUrl URL to redirect the sender’s browser to after canceling the
approval for a payment; it is always required but only used
for payments that require approval (explicit payments)