Developer's Guide

Getting Started
Making a Parallel Payment (NVP)
70 August 7, 2012 Adaptive Payments Developer Guide
In this particular scenario, the paymentExecStatus variable is set to CREATED instead of
COMPLETED, which indicates that the payment has been created, but has not yet been executed.
Making a Parallel Payment (NVP)
A parallel payment is when a sender (whose account is debited) sends a single payment
(amount and currency) up to 6 receivers. The sender can see each payment to a receiver.
 You send a PayRequest, specifying an amount to be paid for each receiver.
 You receive a response with a pay key.
 You must redirect the sender’s browser to PayPal to approve the payment.
In the example below, Paul makes a single payment of $14, which is split into a $9 payment to
Andrea and a $5 payment to Linda. The following event sequence takes place:
Pay Request for Parallel Payment
&actionType=PAY
&cancelUrl=http:\\example.com\cancel.htm
&currencyCode=USD
&receiverList.receiver(0).amount=9.00
&receiverList.receiver(0).email=[e-mail]
&receiverList.receiver(1).amount=5.00
&receiverList.receiver(1).email=[e-mail]
&requestEnvelope.errorLanguage=en_US
&returnUrl=http:\\example.com\return.htm
Pay Response for Parallel Payment
responseEnvelope.timestamp=2009-11-03T08%3A12.937-07%3A00
&responseEnvelope.ack=Success
&responseEnvelope.correlationId=b1cc3eabfa4c1
&responseEnvelope.build=942345
&payKey=AP-688241038Y786593D
&paymentExecStatus=CREATED
The response includes a pay key, which is a token you use in subsequent calls to Adaptive
Payments APIs to identify this particular payment.
In this particular scenario, the paymentExecStatus variable is set to CREATED instead of
COMPLETED, which indicates that the payment has been created, but has not yet been executed.