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
Name-Value Pair API Developer Guide February 01, 2013 101
ExpressCheckout API Operations
DoExpressCheckoutPayment API Operation
6
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.
L_PAYMENTREQUEST_
n_TA
XAMT
m
L_TAXAMTn (deprecated)
(Optional) Item sales tax. 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_TAXAMT0, L_PAYMENTREQUEST_n_TAXAMT1).
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 (,).
L_TAXAMT
n is deprecated since version 63.0. Use
L_PAYMENTREQUEST_0_TAXAMT
m instead.
L_PAYMENTREQUEST_
n_IT
EMWEIGHTVALUE
m,
L_PAYMENTREQUEST_
n_IT
EMWEIGHTUNIT
m
L_ITEMWEIGHTVALUE
n and
L_ITEMWEIGHTUNIT
n
(deprecated)
(Optional) Item weight corresponds to the weight of the item. You can pass this
data to the shipping carrier as is without having to make an additional database
query. 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_ITEMWEIGHTVALUE0,
L_PAYMENTREQUEST_
n_ITEMWEIGHTVALUE1).
Character length and limitations: Any positive integer
L_ITEMWEIGHTTVALUE
n and L_ITEMWEIGHTUNITn are deprecated since
version 63.0. Use L_PAYMENTREQUEST_0_ITEMWEIGHTVALUE
m and
L_PAYMENTREQUEST_0_ITEMWEIGHTUNIT
m instead.
L_PAYMENTREQUEST_
n_IT
EMLENGTHVALUE
m,
L_PAYMENTREQUEST_
n_IT
EMLENGTHUNIT
m
L_ITEMLENGTHVALUEn and
L_ITEMLENGHTUNIT
n
(deprecated)
(Optional) Item length corresponds to the length of the item. You can pass this
data to the shipping carrier as is without having to make an additional database
query. 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_ITEMLENGTHVALUE0,
L_PAYMENTREQUEST_
n_ITEMLENGTHVALUE1).
Character length and limitations: Any positive integer
L_ITEMLENGTHVALUE
n and L_ITEMLENGTHUNITm are deprecated since version
63.0. Use L_PAYMENTREQUEST_0_ITEMLENGTHVALUE
m and
L_PAYMENTREQUEST_0_ITEMLENGTHUNIT
n instead.
Field Description