2012
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
- ManagePendingTransactionStatus 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
- Revision History
- Index
What’s New in Version 69
288 August 2012 Name-Value Pair API Developer Guide
Changes to PaymentDetailsItemType in DoReferenceTransaction Request
PaymentDetailsItemType Fields
L_PAYMENTREQUEST_
n_QT
Y
m
New field
Item quantity. This field is required when you pass a value for ItemCategory.
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_PAYMENTREQUEST_
n_TA
XAMT
m
New field
(Optional) Item sales tax.
These parameters must be ordered sequentially beginning with 0 (for example
L_PAYMENTREQUEST_
n_TAXAMT0, L_PAYMENTREQUEST_n_TAXAMT1).
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.
Field Description
L_ITEMCATEGORY
n New field
Indicates whether the item is digital or physical goods. For digital goods, this
field is required and you must set it to Digital to get the best rates. It is one
of the following values:
Digital
Physical
These parameters must be ordered sequentially beginning with 0 (for example
L_ITEMCATEGORY0, L_ITEMCATEGORY1).
L_NAME
n Item name. This field is required when you pass a value for ItemCategory.
These parameters must be ordered sequentially beginning with 0 (for example
L_NAME0, L_NAME1).
Character length and limitations: 127 single-byte characters
L_AMT
n Cost of item. This field is required when you pass a value for ItemCategory.
These parameters must be ordered sequentially beginning with 0 (for example
L_AMT0, L_AMT1).
NOTE: If you specify a value for L_AMTn, you must specify a value for
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.
Field Description