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.6.0 Features
272 August 7, 2012 Adaptive Payments Developer Guide
580022 Invalid request parameter: <value>
The clientDetails parameter is missing
Invalid request parameter: payKey with value <value>
payKey <value> is expired
Invalid request parameter: <value> with <value>
No sender is associated with this key
The funding plan data is not present
payKey <value> has already been used to make a payment
580022
Invalid request parameter: <value>
Invalid Request Parameter: institutionId with value <value>
The institution id <value> is not activated
The clientDetails parameter is missing
Invalid request parameter: payKey with value <value>
Invalid Phone Country Code <value>
Invalid Country Code <value> for Receiver
Invalid Receiver Phone Type <value> <value> <value>
Invalid Phone Format <value> <value>
Invalid Phone Number <value> <value>
Invalid Receiver Phone Number <value> <value>
Invalid Area or Exchange Code <value> <value>
<value> has already been set and cannot be set multiple times
Invalid request parameter: <value> with value <value>
Invalid request parameter: <value> <value> is invalid
Invalid request parameter: <value> <value> is duplicated
Invalid request parameter: <value> <value> cannot be negative or zero
580022
Invalid request parameter: <value>
Invalid request parameter: payKey with value <value>
580022
Invalid request parameter: <value>
Invalid request parameter: payKey with value <value>
No sender is associated with this key
580022 The funding plan data is not present
Code Message