Paypal has stupid confusing docs explaining this. payerId getting appended to GET requests?

[clupoce]

I'm testing the sandbox and I'm using the .net sdk version 1.8 to create a payment. Using the Create method It's setting the PaymentUrl to

"https://www.sandbox.paypal.com/cgi-bin/webscr?cmd=_express-checkout&token=EC-76572603MF809350A"

and I'm setting the return url to /Cart/ProcessPaypalCheckout?orderId=<insert order id>

However, the response back from paypal is in the form of a GET request with the return url I set AND the payerId and paymentId appended as query parameters

But according to https://developer.paypal.com/docs/checkout/how-to/server-integration/#execute-the-payment-2 I should "Get the paymentID and the payerID from the request body" so why are these values getting appended to the request url as a GET request?

I've read an old way of getting the payerId was by appended query parameters. It's my understanding that was for legacy APIs but I'm not using a legacy api

[ZachH83]

This entire api seems so much more difficult than it needs to be. Everyone else except paypal has seemed to figure out how to make APIs more friendly.

[antoniooi]

I don't understand why they have to make it so confusing and complicated. They just simply branch out anything as they like till you really don't know what to choose and how to choose. Just the naming of their products and API alone is so much complicated and confusing. I can feel that the person(s) who built their APIs and documentation is pretty messy in his/her brains and don't know what to do to simplify stuff. That makes their API sounds scary to many developers around the world and don't know how to go about getting started with it.