Developer's Guide

Adaptive Payments Developer Guide August 7, 2012 107
Pay API Operation
Pay Errors
580023 Invalid request
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>
 Inconsistant 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
Since 1.6.0
580027 The argument is unsupported
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
Since 1.6.0
580028 The URL <value> is malformed
580029 Invalid request
580030 This transaction cannot be processed at this time. Please try again
later.
Since 1.3.0
589009 This payment cannot be processed because no payment source is
available
589019 The preapproval key is invalid
589023 If a fractional amount is rounded due to currency conversion,
funds could be lost
589039 The email address is invalid. It may not be registered in PayPal’s
system yet
Code Message Additional Information