Advanced Features Guide

Table Of Contents
Implementing Parallel Payments
Integrating Parallel Payments by Using the SOAP API
5
68 April 2012 Express Checkout Advanced Features Guide
&L_PAYMENTREQUEST_0_DESC0=SJC Terminal 1. Flight time: 7 hours 12 minutes
&L_PAYMENTREQUEST_0_DESC1=BWI Terminal 1. Flight time: 7 hours 38 minutes
&L_PAYMENTREQUEST_1_NAME0=Night(s) stay at 9990 Deereco Road,Timonium, MD
21093
&L_PAYMENTREQUEST_1_NUMBER0=300
&L_PAYMENTREQUEST_1_QTY0=1
&L_PAYMENTREQUEST_1_TAXAMT0=20
&L_PAYMENTREQUEST_1_AMT0=180
&L_PAYMENTREQUEST_1_DESC0=King No-Smoking; Check in after 4:00 PM; Check
out by 1:00 PM
Response Parameters
[successResponseFields]
&TOKEN=EC-17C76533PL706494P
Integrating Parallel Payments by Using the SOAP API
Parallel payments uses the PaymentDetailsType structure to pass data for each merchant
receiving payment. You can pass up to a 10 structures in a single call to
SetExpressCheckout and DoExpressCheckoutPayment.
NOTE: Be sure to use structure fields that are not marked as ‘deprecated’ in the SOAP API
reference documentation.
To integrate parallel payments by using the SOAP interface to Express Checkout:
1. Create PaymentDetails as an array of PaymentDetailsType structures, one for each
payment you host on your marketplace.
2. You are required to pass values in the following PaymentDetailsType fields in the call
to SetExpressCheckout and DoExpressCheckoutPayment.
Pass the value Sale or Order in PaymentAction.
Pass a unique value in PaymentRequestID. You will use this value to locate the
matching response details for that payment.
Pass the merchant’s Payer ID (secure merchant account ID) or the merchant’s email
address in the SellerDetailsType.PayPalAccountId field.
3. Use PaymentDetailsType and PaymentDetailsItemType fields, as appropriate, in
the call to SetExpressCheckout and DoExpressCheckoutPayment to pass data
about each payment.