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
1.4.0 Features
276 August 7, 2012 Adaptive Payments Developer Guide
Changes to the Pay API Operation
Changes to PayRequest and PayResponse Message
Changes to the PaymentDetails API Operation
Changes to PaymentDetails response messages
Field Description
actionType New CREATE value:
PAY – Use this option if you are not using the Pay request
in combinations with the ExecutePayment request.
CREATE – Use this option to set up the payment
instructions with the Pay request and then execute the
payment at a later time with the ExecutePayment
request.
paymentType New person-to-person values PERSONAL and CASHADVANCE.
Person-to-person payments can only be made under the
following conditions:
simple and parallel payments (not chained)
all transactions within the single Pay request must be
person-to-person
feesPayer field set to EACHRECEIVER or SENDER.
this feature requires the appropriate permission level from
PayPal
Receiver.PhoneNumberType New field:
common:PhoneNumberType
Allows you to pass a receiver’s mobile phone number,
including the country code and extension.
NOTE: This feature is available for applications with special
permission level.
Field Description
actionType New CREATE value:
PAY – Use this option if you are not using the Pay request
in combinations with the ExecutePayment request.
CREATE – Use this option to set up the payment
instructions with the Pay request and then execute the
payment at a later time with the ExecutePayment
request.