Integration Guide
Table Of Contents
- Express Checkout Integration Guide
- Contents
- Preface
- Introducing Express Checkout
- Express Checkout Button and Logo Image Integration
- PayPal Name-Value Pair API Basics
- Implementing the Simplest Express Checkout Integration
- Testing an Express Checkout Integration
- Customizing Express Checkout
- Implementing the Instant Update API
- Immediate Payment
- Implementing Parallel Payments
- Handling Payment Settlements
- Handling Recurring Payments
- How Recurring Payments Work
- Recurring Payments Terms
- Options for Creating a Recurring Payments Profile
- Recurring Payments With Express Checkout
- Recurring Payments Profile Status
- Getting Recurring Payments Profile Information
- Modifying a Recurring Payments Profile
- Billing the Outstanding Amount of a Profile
- Recurring Payments Notifications
- Using Other PayPal API Operations
- Integrating giropay with Express Checkout
Express Checkout Integration Guide May 2010 99
Implementing Parallel Payments
Name-Value Pair Syntax Supporting Parallel Payments
9
Name-Value Pair Syntax Supporting Parallel Payments
The PayPal API uses a special syntax for NVP fields to support parallel payments.
The NVP interface to the PayPal API supports up to a maximum of 10 parallel payments in a
transaction. To accommodate this, request fields have the format shown below, where
n is a
number in the range 0 to 9 representing a payment.
PAYMENTREQUEST_
n_NVPREQUESTFIELDNAME
The first numbered field in a list of payments starts with n equal to 0, the second field has n
equal to 1, and so forth. If you are upgrading to version 63.0 of the Express Checkout API, you
will recognize
NVPREQUESTFIELDNAME to be the single-payment NVP request field name.
The response name format is:
PAYMENTREQUEST_
n_NVPRESPONSEFIELDNAME
NOTE: Even if your Express Checkout integration is for single payments, you must use this
format and specify
n=0 for single payment with version 63.0 and later of the Express
Checkout API.
The payment information returned in the DoExpressCheckoutPayment response has the
same basic format but the field name starts with PAYMENTINFO, as shown below:
PAYMENTINFO_
n_NVPRESPONSEFIELDNAME
The NVP API reference documentation shows the proper format and naming for every NVP
field that uses this syntax.
Examples: