Q:

Paypal Adaptive Payments Allowing Third Party to Act on Your Behalf

I'm reading the adaptive paypals API ebook and it says on page 21, that :
"if you allow a third party to paypal to execute an application on your behalf the third party becomes the API caller because the third party is now calling the Adaptive Payments API. The third party must also have permission from Paypal to use the advanced service. For example if an application supports chained payments both you anf the third party must have permission to  use the service"
Does this mean if I have an application where a user of the site logs in and sends me $100 (as an approved user of chain payments), say only $50 of the money goes to me and another $25 goes to y, and the other $25 goes back to the ORIGINAL sender... can they ONLY accept this if they have an approved chain payment account??
or does only the primary receiver need to have a chain payment approved account?
Thanks

A:

This section is likely referring to third-party API authentication. E.g. if you're setting a USER, PWD and SIGNATURE but also passing a SUBJECT in order to force the API call to actually be called on behalf of another third party.
This wouldn't be strictly something to do with a chained payment scenario, because the SUBJECT can again be different from the primary receiver.  
For example:
METHOD=Pay
USER=myapi_api1.test.com
PWD=xxxxxx
SIGNATURE=xxxxxxxx
X-APPLICATION-ID=APP-XXXXXXXXX // The application ID as owned by yourstore@yourdomain.com
SUBJECT=yourstore@yourdomain.com // Call the 'Pay' API on behalf of yourstore@yourdomain.com, but use my API credentials (yourstore@yourdomain.com must have granted myapi_api1.test.com access to do this)
PRIMARYRECEIVER=blah@anotherdomain.com // This receiver only has to be able to receive money
Note: This does not constitute an actual API call you would send.  I don't happen to have an Adaptive Payments API call at hand to make a working example at the moment.

