Order payment not received - Paypal Express

jamie-selesti commented 4 years ago

Preconditions (*)

Using Magento 2.3.5-p1
Using PHP 7.3
PayPal Express Checkout enabled and setip

Steps to reproduce (*)

Place an order using Paypal Express

Expected result (*)

Receive payment for the order

Actual result (*)

We had an order whereby Magento told us the order was paid but looking in our Paypal account we don't have the money.
Looking at the sales_order_payment table entry I can see in the additional_information column we have

{"paypal_express_checkout_shipping_overridden":1,
"paypal_express_checkout_shipping_method":"",
"paypal_payer_id":"REDACTED",
"paypal_payer_email":"REDACTED",
"paypal_payer_status":"unverified",
"paypal_address_status":"Confirmed",
"paypal_correlation_id":"REDACTED",
"paypal_express_checkout_payer_id":"REDACTED",
"paypal_express_checkout_token":"REDACTED",
"method_title":"PayPal",
"paypal_express_checkout_redirect_required":null}

The key thing here is that there isn't a paypal_payment_status in the information as you would expect. Below is what another order's additional_information looks like whose money we did receive

{"paypal_express_checkout_shipping_overridden":1,
"paypal_express_checkout_shipping_method":"",
"paypal_payer_id":"REDACTED",
"paypal_payer_email":"REDACTED",
"paypal_payer_status":"unverified",
"paypal_address_status":"Confirmed",
"paypal_correlation_id":"REDACTED",
"paypal_express_checkout_payer_id":"REDACTED",
"paypal_express_checkout_token":"REDACTED",
"method_title":"PayPal",
"paypal_express_checkout_redirect_required":null,
"paypal_protection_eligibility":"Eligible",
"paypal_payment_status":"completed",
"paypal_pending_reason":"None"}

Therefore the question is why did Magento think the order was fully paid when it was not?

Note, this does bug not always happen so it will be hard to replicate

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

[ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 4 years ago

Hi @jamie-selesti. Thank you for your report. To help us process this issue please make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

Join Magento Community Engineering Slack and ask your questions in #github channel.

m2-assistant[bot] commented 4 years ago

Hi @engcom-Lima. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Lima commented 4 years ago

Hello @jamie-selesti Could you provide more details for reproduce this issue? Please add steps to reproduce.

Thank you!

engcom-Lima commented 4 years ago

@jamie-selesti we are closing this issue due to inactivity. If you'd like to update it, please reopen the issue.

magento / magento2