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 271
1.6.0 Features
Additional Error Messages for Version 1.6.0
Code Message
520003 Authentication failed. API credentials are incorrect.
520003
The caller’s credential doesn't have permission for the fee payer <value>
The caller's credential doesn't have permission for the payment type <value>
Authentication failed. API credentials are incorrect.
540031 You do not have permission to execute this payment
Operation is not permitted because the credentials do not match those of the initial operation
540031 You do not have permission to get these preapproval details
540031 You do not have permission to get these payment options
Operation is not permitted because the credentials do not match those of the initial operation
540031 You do not have permission to set these payment options
Operation is not permitted because the credentials do not match those of the initial operation
540031 Operation is not permitted because the credentials do not match those of the initial operation
540031 You do not have permission to get these payment details
550001
You are not allowed to confirm the preapproval for this key
User is not allowed to perform this action.
550001 You do not have permission to execute this payment implicitly
550001
User is not allowed to perform this action.
You are not allowed to get the funding plans for this key
You do not have permission to get these funding plan details
550001
User is not allowed to perform this action.
You are not allowed to get the addresses for this key
580001
Invalid request: both email and phone cannot be set <value> <value> <value>
Invalid request: neither email nor phone is set <value>
To use currency <value>, currency must be held by sender and all receivers
Invalid request: More than one field cannot be used to specify a sender
Invalid request: <value>
580001 Invalid request: <value>
580022
Invalid request parameter: <value>
The clientDetails parameter is missing
The PIN is invalid