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 117
PaymentDetails API Operation
PaymentDetailsResponse Message
PaymentInfoList Fields
PaymentInfo Fields
Fields Description
paymentInfo ap:PaymentInfo
Represents the payment attempt made to a receiver of a PayRequest. If the
execution of the payment has not yet completed, there are no transaction
details returned.
Field Description
pendingReason xs:string
The reason why a payment is pending. the payment has a pending refund.
Possible values are:
ADDRESS_CONFIRMATION – The payment is pending because the sender
does not have a confirmed address on file and receiver's Payment
Receiving Preferences is set for manually accepting payments or denying
each of these payments.
ECHECK – The payment is pending because it was made by an eCheck that
has not yet cleared.
INTERNATIONAL – The payment is pending because the receiver holds a
non-U.S. account and does not have a withdrawal mechanism. The receiver
must manually accept or deny this payment from the Account Overview.
MULTI_CURRENCY – The receiver does not have a balance in the currency
sent, and does not have the Payment Receiving Preferences set to
automatically convert and accept this payment. Receiver must manually
accept or deny this payment from the Account Overview.
UNILATERAL – The payment is pending because it was made to an email
address that is not yet registered or confirmed.
UPGRADE – The payment is pending because it was made via credit card
and the receiver must upgrade the account to a Business account or Premier
status to receive the funds. It can also mean that receiver has reached the
monthly limit for transactions on the account.
VERIFY – The payment is pending because the receiver is not yet verified.
RISK – The payment is pending while it is being reviewed by PayPal for
risk.
OTHER – The payment is pending for a reason other than those listed above.
For more information, contact PayPal Customer Service.
pendingRefund xs:boolean
Whether the payment has a pending refund.
Possible values are:
true – The payment has a pending refund.
false – The payment does not have a refund pending.