2013
Table Of Contents
- Name-Value Pair API Developer Guide
- Contents
- What’s New
- Preface
- PayPal Name-Value Pair API Basics
- AddressVerify API Operation
- Authorization and Capture API Operation Reference
- DoDirectPayment API Operation
- DoNonReferencedCredit API Operation
- ExpressCheckout API Operations
- GetBalance API Operation
- GetPalDetails API Operation
- GetTransactionDetails API Operation
- ManagePendingTransactionStatu s API Operation
- MassPay API Operation
- Recurring Payments and Reference Transactions API Operations
- CreateRecurringPaymentsProfile API Operation
- GetRecurringPaymentsProfileDetails API Operation
- ManageRecurringPaymentsProfileStatus API Operation
- BillOutstandingAmount API Operation
- UpdateRecurringPaymentsProfile API Operation
- CreateBillingAgreement API Operation
- SetCustomerBillingAgreement API Operation
- GetBillingAgreementCustomerDetails API Operation
- BAUpdate API Operation
- DoReferenceTransaction API Operation
- RefundTransaction API Operation
- TransactionSearch API Operation
- API Error Codes
- General API Errors
- Validation Errors
- DirectPayment API Errors
- SetExpressCheckout API Errors
- GetExpressCheckoutDetails API Errors
- DoExpressCheckoutPayment API Errors
- Authorization and Capture API Errors
- GetTransactionDetails API Errors
- TransactionSearch API Errors
- RefundTransaction API Errors
- MassPay API Errors
- Recurring Payments Errors
- SetCustomerBillingAgreement Errors
- GetBillingAgreementCustomerDetails Errors
- CreateBillingAgreement Errors
- UpdateBillingAgreement Errors
- DoReferenceTransaction Errors
- AddressVerify API Errors
- ManagePendingTransactionStatus API Errors
- Countries and Regions Supported by PayPal
- State and Province Codes
- Currency Codes
- AVS and CVV2 Response Codes
- About Previous Versions of the API
- What's New in Version 95.0
- What's New in Version 93.0
- What's New in Version 92.0
- What's New in Version 91.0
- What's New in Version 89.0
- What's New in Version 88.0
- What’s New in Version 85.0
- What’s New in Version 84.0
- What’s New in Version 82.0
- What’s New in Version 80.0
- What’s New in Version 74.0
- What’s New in Version 72.0
- What's New in Version 69
- What's New in Version 66
- Revision History
- Index
ExpressCheckout API Operations
SetExpressCheckout API Operation
6
72 February 01, 2013 Name-Value Pair API Developer Guide
L_PAYMENTREQUEST_n_DE
SC
m
L_DESC
n (deprecated)
(Optional) Item description. 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_DESC0, L_PAYMENTREQUEST_n_DESC1).
Character length and limitations: 127 single-byte characters
This field is introduced in version 53.0. L_DESC
n is deprecated since version 63.0.
Use L_PAYMENTREQUEST_0_DESC
m instead.
L_PAYMENTREQUEST_
n_AM
T
m
L_AMTn (deprecated)
Cost of item. 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_AMT0, L_PAYMENTREQUEST_n_AMT1).
NOTE: If you specify a value for L_PAYMENTREQUEST_n_AMTm, you must
specify a value for PAYMENTREQUEST_
n_ITEMAMT.
Character length and limitations: Value is a positive number which cannot exceed
$10,000 USD in any currency. It includes no currency symbol. It must have 2
decimal places, the decimal separator must be a period (.), and the optional
thousands separator must be a comma (,).
This field is introduced in version 53.0. L_AMT
n is deprecated since version 63.0.
Use L_PAYMENTREQUEST_0_AMT
m instead.
L_PAYMENTREQUEST_
n_NU
MBER
m
L_NUMBER
n (deprecated)
(Optional) Item number. 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. These
parameters must be ordered sequentially beginning with 0 (for example
L_PAYMENTREQUEST_
n_NUMBER0, L_PAYMENTREQUEST_n_NUMBER1).
Character length and limitations: 127 single-byte characters
This field is introduced in version 53.0. L_NUMBER
n is deprecated since version
63.0. Use L_PAYMENTREQUEST_0_NUMBER
m instead.
L_PAYMENTREQUEST_
n_QT
Y
m
L_QTYn (deprecated)
Item quantity. This field is required when
L_PAYMENTREQUEST_
n_ITEMCATEGORYm is passed. For digital goods
(L_PAYMENTREQUEST_
n_ITEMCATEGORYm=Digital), this field is required.
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
only supports single payments. These parameters must be ordered sequentially
beginning with 0 (for example L_PAYMENTREQUEST_
n_QTY0,
L_PAYMENTREQUEST_
n_QTY1).
Character length and limitations: Any positive integer
This field is introduced in version 53.0. L_QTY
n is deprecated since version 63.0.
Use L_PAYMENTREQUEST_0_QTY
m instead.
Field Description