The Community Forum is not available for new posts or responses; previous posts remain available to review. For comprehensive support options, please visit PayPal.com/HelpCenter Merchant Technical Support: For technical support and related questions, please visit our Technical Support Help Center or Developer Central
If you want to report illegal content under the EU Digital Services Act, please do so here
Received word from the REST team that the information is indeed missing. They may or may not re-add it in the future. We just have to keep an eye on the docs and "wait and see" at this time.
... View more
Still nothing? Apparently the "Community" does not know why the payer status has been removed from the REST API v2. Trying to get ahold of anyone inside PayPal is next to impossible. I wonder how to actually get the request/information added to the REST API v2 then.
... View more
Could there be an off chance the redirect is occurring on your server config? As in, paypal is trying to send the user to the "http" version of your url, and then your server bounces around to "https"? It was something that happened once for us as we force "https" urls for everything, and somehow paypal got a url with just "http" in front. Just a thought. Might not be the case, but I've not seen paypal doing the redirect twice as you described.
... View more
You will need to add disable-funding options to the sdk/js include line like so: <script src="https://www.paypal.com/sdk/js?client-id={YOUR_ID}&disable-funding=credit,card,venmo,sepa,bancontact,eps,giropay,ideal,sofort,p24"></script>
... View more
Verifying is pretty much just doing a GET on the orderID, and looking over the response to see if the user has "CONFIRMED" (approved) the amount to be paid. Or if the order has already been captured, you check to see if its status is "COMPLETED". Capturing is actually telling the PayPal API to take those funds from the user (the payer) and dump it into your merchant account (the payee) after they have confirmed (onApprove). Once you do this, its a good time to store all of this information in a database (if you have not already)... so fulfilling the purchase can be handled and tracked. Most of the examples I see skip the step of looking at the order first, and instead goes straight into capturing, and then looking at the order. Like their example for the js sdk "onApprove" does a capture immediately instead of verifying the order first. Its a flow choice, but at some point you would want to do a GET on that orderID to check that everything checks out and to store details from it into a database.
... View more
You can get your data by reading the file: php://input, for example using file_get_contents('php://input') and then decode that input with json_decode(). $json = file_get_contents('php://input');
$data = json_decode($json);
$orderid = $data->orderID;
... View more
@samebenezer wrote: Thanks for your answer...🤗 Is there an example code snippet that i can refer to with respect to the above said problem using the script tag on the client side?? I assume you mean the v2 javascript sdk method like described here: (?) https://developer.paypal.com/docs/checkout/integrate/#4-set-up-the-transaction If so, it would go outside of the `purchase_units` section like so: return actions.order.create({
purchase_units: [{
amount: {
value: '0.01'
}
}],
application_context: {
shipping_preference: 'NO_SHIPPING'
}
});
... View more
In the REST API v2 for Orders, you could pass "application_context.shipping_preference = NO_SHIPPING" when you POST to "/v2/checkout/orders". https://developer.paypal.com/docs/api/orders/v2/#definition-order_application_context In the REST API v1, you would first have to create an Experience Profile, and then pass that profile ID with the create payment on "experience_profile_id" (set after "intent"). https://developer.paypal.com/docs/integration/direct/payment-experience/?mark=experience_profile_id#create-paypal-payment-with-web-profile
... View more
After some poking, I have discovered what I need. These instructions are for if using the Checkout PHP SDK (however the solution can also be found with any SDK using curl). After receiving a response (that is not an Exception) from a REST request, the Correlation ID can be found in the return headers by the name of "Paypal-Debug-Id". To access these headers with the Checkout PHP SDK, you can simply pull it via: // following the same format as the example code provided with the SDK
$request = new WhateverMethodYouAreDoing();
$client = PayPalClient::client();
$response = $client->execute($request);
// thankfully $response->headers is exposed and not set as private or protected!
$correlationid = $response->headers['Paypal-Debug-Id'];
And then you now have the ID like we are used to getting in prior versions of the paypal processes. Which can then be used to lookup these calls and debug.
... View more
