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 89
ExpressCheckout API Operations
GetExpressCheckoutDetails API Operation
6
EbayItemPaymentDetailsItemType Fields
L_PAYMENTREQUEST_
n_ITEM
WIDTHVALUE
m,
L_PAYMENTREQUEST_
n_ITEM
WIDTHUNIT
m
L_ITEMWIDTHVALUEn and
L_ITEMWIDTHUNIT
n
(deprecated)
Width 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_ITEMWIDTHVALUE0,
L_PAYMENTREQUEST_
n_ITEMWIDTHVALUE1).
Character length and limitations: Any positive integer
L_ITEMWIDTHVALUE
n and L_ITEMWIDTHUNITn are deprecated in version
63.0. Use L_PAYMENTREQUEST_
n_ITEMWIDTHVALUEm and
L_PAYMENTREQUEST_
n_ITEMWIDTHUNITm instead.
L_PAYMENTREQUEST_
n_ITEM
HEIGHTVALUE
m,
L_PAYMENTREQUEST_
n_ITEM
HEIGHTUNIT
m
L_ITEMHEIGHTVALUEn and
L_ITEMHEIGHTUNIT
n
(deprecated)
Height 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_ITEMHEIGHTVALUE0,
L_PAYMENTREQUEST_
n_ITEMHEIGHTVALUE1).
Character length and limitations: Any positive integer
L_ITEMHEIGHTVALUE
n and L_ITEMHEIGHTUNITn are deprecated in version
63.0. Use L_PAYMENTREQUEST_
n_ITEMHEIGHTVALUEm and
L_ITEMHEIGHTUNIT
m instead.
L_PAYMENTREQUEST_
n_ITEM
CATEGORY
m
Indicates whether the item is digital or physical. 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. These parameters
must be ordered sequentially beginning with 0 (for example
L_PAYMENTREQUEST_
n_ITEMCATEGORY0,
L_PAYMENTREQUEST_
n_ITEMCATEGORY1). It is one of the following values:
Digital
Physical
This field is available since version 65.1.
Field Description
L_PAYMENTREQUEST_
n_EB
AYITEMNUMBER
m
EBAYITEMNUMBERn
(deprecated)
Auction 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.
Character length: 765 single-byte characters
EBAYITEMNUMBER
n is deprecated since 63.0. Use
L_PAYMENTREQUEST_0_EBAYAUCTIONTXNID
m instead.
Field Description