
1.4.0 Features
274 August 7, 2012 Adaptive Payments Developer Guide
PaymentDetails Pending Reason Feature in Version 1.5.0
The PaymentDetailsResponse now returns the new pendingReason parameter. This
parameter returns a string describing the reason why a transaction is pending. 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.
1.4.0 Features
Release 1.4.0 provides the new API operations: ExecutePayment, GetPaymentOptions,
and SetPaymentOptions. The new API operations work with the actiontype CREATE in the
Pay API operation.
New API Operations for Version 1.4.0
New API Operation Description
ExecutePayment Execute a payment created with a PayRequest that had the
actionType set to CREATE.
Kommentare zu diesen Handbüchern