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 273
1.5.0 Features
1.5.0 Features
Adaptive Payments version 1.5.0 provides the new features for the APIs, such as the ability to
delay a chained payment and to obtain the reason a payment is pending.
In addition to API changes, version 1.5.0 also offers new features that do not affect the APIs,
such as guest payments, and ELV support.
Ability to Delay a Chained Payment Feature in Version 1.5.0
You can now set up chained payments to process the transaction leg to the primary receiver,
and delay the payment to the secondary receivers. To do this, you use the Pay or
ExecutePayment call and pass the new parameter actionType with PAY_PRIMARY.
580023 The fee payer <value> cannot be used if a primary receiver is specified
The fee payer <value> can only be used if a primary receiver is specified
The fee payer <value> must have exactly 2 receivers
The reverseAllParallelPaymentOnError field can be true only if a primary receiver is not
specified
The fee payer <value> cannot be used if a preapproval key is specified
Invalid request: FundingType cannot be specified when PaymentSubType is specified
Your Application is not approved to use the PaymentSubType: <value>
Your Application is not approved to use the PaymentType: <value>
Invalid request parameter: PaymentType should be the same for all receivers <value>
Inconsistent request parameter for digitalgoods
Invalid request parameter: PaymentSubType should be the same for all receivers <value>
Invalid Request: RECEIVABLE cannot be used with other funding types
For chained payments, receivers must have premier or business accounts
580027
Currently the system does not accept the currency <value>
Unsupported country code <value>
Currently the system does not accept the currency <value>
The parameter is not supported
580027 This parameter is not supported
580029 A pin is required to confirm this preapproval Missing required request parameter: <value>
580029 Missing required request parameter: <value>
580029 A pay key, transaction ID, or tracking ID is missing
589018 The pay key <value> is invalid
589019 The preapproval key <value> is invalid
589061 The receiver <value> is invalid for this refund
Code Message