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
About Previous Versions of the API
What's New in Version 66
300 February 01, 2013 Name-Value Pair API Developer Guide
L_PAYMENTREQUEST_n_NAME
m
L_NAME
n (deprecated)
Item name. For digital goods, 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. 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
L_NAME
n is deprecated since version 63.0. Use
L_PAYMENTREQUEST_0_NAME
m instead.
L_PAYMENTREQUEST_
n_DESC
m
L_DESC
n (deprecated)
Item description. For digital goods, 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. 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
L_DESC
n is deprecated since version 63.0. Use
L_PAYMENTREQUEST_0_DESC
m instead.
L_PAYMENTREQUEST_
n_AMTm
L_AMTn (deprecated)
Cost of item. For digital goods, 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. 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: Must not exceed $10,000 USD in any
currency. No currency symbol. Regardless of currency, decimal separator must
be a period (.), and the optional thousands separator must be a comma (,).
Equivalent to nine characters maximum for USD.
L_AMT
n is deprecated since version 63.0. Use L_PAYMENTREQUEST_0_AMTm
instead.
L_PAYMENTREQUEST_
n_QTYm
L_QTYn (deprecated)
Item quantity. For digital goods, 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. 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
L_QTY
n is deprecated since version 63.0. Use L_PAYMENTREQUEST_0_QTYm
instead.
Field Description