Advanced Features Guide

Implementing Parallel Payments
Integrating Parallel Payments by Using the NVP API
5
66 April 2012 Express Checkout Advanced Features Guide
PAYMENTREQUEST_0_AMT
The following represents the second line of the name for the third payment:
L_PAYMENTREQUEST_2_NAME1
Integrating Parallel Payments by Using the NVP API
To integrate parallel payments by using the NVP API, you need to use the syntax for creating
unique NVP request field names and create a unique set of fields for each payment. You also
need to set a few required variables.
To integrate parallel payments using the NVP interface to Express Checkout:
1. Create a unique set of NVP request fields for each payment you will be hosting on your
marketplace using the syntax PAYMENTREQUEST_
n_NVPREQUESTFIELDNAME where n is
a value from 0 - 9.
2. You are required to pass values in the following Payment Details Type fields in the call to
SetExpressCheckout and DoExpressCheckoutPayment. For each of the
n payments
you host:
– Pass the value Sale or Order in PAYMENTREQUEST_
n_PAYMENTACTION.
– Pass a unique value for PAYMENTREQUEST_
n_PAYMENTREQUESTID. You will use this
value to locate the matching payment response details for that payment.
– Pass the merchant’s Payer ID (secure merchant account ID) or the merchant’s email
address in PAYMENTREQUEST_
n_SELLERPAYPALACCOUNTID.
3. Use the Payment Details Item Type fields as appropriate in the call to
SetExpressCheckout and DoExpressCheckoutPayment to pass data about each
payment.
Result:
For each payment in the transaction, the DoExpressCheckoutPayment response returns:
 A PAYMENTINFO_n_PAYMENTREQUESTID value that matches the
PAYMENTREQUEST_
n_PAYMENTREQUESTID value you passed in the
DoExpressCheckoutPayment request. Use this value to locate the response data for
each payment.
 A PAYMENTINFO_n_SELLERPAYPALACCOUNTID. This value is whichever one of the
following values was passed in:
– The merchant’s email address
– The merchant’s Payer ID (secure merchant account ID)