2012

Name-Value Pair API Developer Guide August 2012 71
ExpressCheckout API Operations
SetExpressCheckout API Operation
6
Payment Details Item Type Fields
PAYMENTREQUEST_
n_PAY
MENTACTION
PAYMENTACTION
(deprecated)
How you want to obtain payment. When implementing parallel payments, this field
is required and must be set to Order. When implementing digital goods, this field
is required and must be set to Sale. You can specify up to 10 payments, where
n is
a digit between 0 and 9, inclusive; except for digital goods, which supports single
payments only. If the transaction does not include a one-time purchase, this field is
ignored. It is one of the following values:
 Sale – This is a final sale for which you are requesting payment (default).
 Authorization – This payment is a basic authorization subject to settlement
with PayPal Authorization and Capture.
 Order – This payment is an order authorization subject to settlement with
PayPal Authorization and Capture.
NOTE: You cannot set this field to Sale in SetExpressCheckout request and
then change the value to Authorization or Order in the
DoExpressCheckoutPayment request. If you set the field to
Authorization or Order in SetExpressCheckout, you may set the
field to Sale.
Character length and limitations: Up to 13 single-byte alphabetic characters
PAYMENTACTION is deprecated since version 63.0. Use
PAYMENTREQUEST_0_PAYMENTACTION instead.
PAYMENTREQUEST_
n_PAY
MENTREQUESTID
PAYMENTREQUESTID
(deprecated)
A unique identifier of the specific payment request, which is required for parallel
payments. You can specify up to 10 payments, where
n is a digit between 0 and 9,
inclusive.
Character length and limitations: Up to 127 single-byte characters
PAYMENTREQUESTID is deprecated since version 63.0. Use
PAYMENTREQUEST_0_PAYMENTREQUESTID instead.
Field Description
L_PAYMENTREQUEST_
n_NA
ME
m
L_NAME
n (deprecated)
Item name. This field is required when
L_PAYMENTREQUEST_
n_ITEMCATEGORYm is passed. You can specify up to 10
payments, where
n is a digit between 0 and 9, inclusive, and m specifies the list
item within the payment; except for digital goods, which supports single payments
only. These parameters must be ordered sequentially beginning with 0 (for
example L_PAYMENTREQUEST_
n_NAME0, L_PAYMENTREQUEST_n_NAME1).
Character length and limitations: 127 single-byte characters
This field is introduced in version 53.0. L_NAME
n is deprecated since version 63.0.
Use L_PAYMENTREQUEST_0_NAME
m instead.
Field Description