Advanced Features Guide
Table Of Contents
- Express Checkout Advanced Features Guide
- Contents
- Preface
- Customizing Express Checkout
- PayPal Review Page Order Details
- Providing Gift Options
- Obtaining Buyer Consent to Receive Promotional Email
- Overriding Your Customer Service Number
- Adding a Survey Question
- PayPal Page Style
- Changing the Locale
- Handling Shipping Addresses
- Automatically Filling Out Shipping and Contact Information
- Buyer Pays on PayPal
- Express Checkout on Mobile Devices
- About the Express Checkout Experience on Mobile Devices
- Mobile Platforms Supported by Express Checkout
- About Mobile Express Checkout Integration
- Integrating Express Checkout With Your Mobile Website
- Enabling PayPal Account Optional Checkout on Mobile Devices
- Request Fields Supported by Express Checkout on Mobile Devices
- Locales Supported by Express Checkout on Mobile Devices
- Features Not Supported by Express Checkout on Mobile Devices
- Handling Recurring Payments
- How Recurring Payments Work
- Recurring Payments Terms
- Options for Creating a Recurring Payments Profile
- Recurring Payments With the Express Checkout API
- Recurring Payments Profile Status
- Getting Recurring Payments Profile Information
- Modifying a Recurring Payments Profile
- Billing the Outstanding Amount of a Profile
- Recurring Payments Notifications
- Reference Transactions
- Implementing Parallel Payments
- Integrating giropay with Express Checkout
- Implementing the Instant Update API
- Payment Review
- Express Checkout Dynamic Image Integration
- Immediate Payment
- Revision History
Express Checkout Advanced Features Guide April 2012 65
Implementing Parallel Payments
Name-Value Pair Syntax Supporting Parallel Payments
5
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 following format, 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.
The response name format is:
PAYMENTREQUEST_
n_NVPRESPONSEFIELDNAME
NOTE: Even if your Express Checkout integration supports single payments only, you must
use this format. Specify
n=0 for single payment with version 63.0 or higher of the
Express Checkout API.
The payment information returned in the DoExpressCheckoutPayment response has the
same basic format; however, the field name starts with PAYMENTINFO:
PAYMENTINFO_
n_NVPRESPONSEFIELDNAME
The NVP API reference documentation shows the proper format and naming for every NVP
field that uses this syntax.
Examples:
The following syntax represents the total amount of the first payment: