Wrong Guest Customer email when placing an order by graphql using payment "paypal_express"

[zexperto]

Preconditions and environment

• Magento version: 2.4.5-p2 the problem happened when we use this mutation setPaymentMethodOnCart(input: { cart_id: "{{guest_cart_id}}" payment_method: { code: "paypal_express" paypal_express: { token: "EC-****" payer_id: "**" } } }) after paying the order

Steps to reproduce

using Graphql

• createEmptyCart
• addSimpleProductsToCart
• setShippingAddressesOnCart
• setShippingMethodsOnCart
• setBillingAddressOnCart
• setGuestEmailOnCart (use for example paypal@magento.com)
• setPaymentMethodOnCart
• createPaypalExpressToken
• redirect tp Pay Pal to pay (use any buyer email except the above email EX: buyer@paypal.com)
• setPaymentMethodOnCart (the problem start in this step)
• placeOrder

Expected result

the Order email should be Customer Email "paypal@magento.com"

Actual result

the Customer email in the order and in the addresses is the buyer email which is not correct

Additional information

No response

Release note

No response

Triage and priority

• [ ] 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]]

Hi @zexperto. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. 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).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://2ad3c28fd6c4f46878e9fffe6eb11bed.instances-prod.magento-community.engineering Admin access: https://2ad3c28fd6c4f46878e9fffe6eb11bed.instances-prod.magento-community.engineering/admin_8853 Login: 995dc35f Password: b7b7517a4ee3

[engcom-Bravo]

Hi @zexperto,

Thank you for reporting and collaboration.

We have tried to reproduce the issue on Magento 2.4-develop instance.

Steps to reproduce

using Graphql

• createEmptyCart
• addSimpleProductsToCart
• setShippingAddressesOnCart
• setShippingMethodsOnCart
• setBillingAddressOnCart
• setGuestEmailOnCart (use for example paypal@magento.com)
• setPaymentMethodOnCart
• createPaypalExpressToken
• redirect tp Pay Pal to pay (use any buyer email except the above email EX: buyer@paypal.com)
• setPaymentMethodOnCart (the problem start in this step)
• placeOrder

We are able to set the Payment methods

We are not able to proceed further with placeOrder mutation could you please let us know we are missing anything.

We are getting error Unable to place order: A server error stopped your order from being placed. Please try to place your order again.

As per this document https://developer.adobe.com/commerce/webapi/graphql/schema/cart/mutations/place-order/ we will get this error when we don't have products in cart but we have products in cart.

Could you please help us to proceed further.

Thanks.

[sheyandckap]

Hi, I also face the same issue and my magento version is Magento ver. 2.4.5-p1. These are the steps to reproduce the issue

01.Create an Empty Cart mutation { createEmptyCart }

2. setGuestEmailOnCart

mutation { setGuestEmailOnCart(input: { cart_id: "test" email: "test@gmail.com" }) { cart { email } } }

03.Add products

mutation { addConfigurableProductsToCart( input: { cart_id: "test" cart_items: [ { parent_sku: "2018-test" data: { quantity: 1 sku: "100-test-AI" } } ] } ) { cart { items { uid quantity product { name sku } ... on ConfigurableCartItem { configurable_options { option_label } } } } } }

4. Cart Query

{ cart(cart_id: "test") { email items { id product { name sku } quantity errors { code message } } } }

05.setShippingAddressesOnCart

mutation { setShippingAddressesOnCart( input: { cart_id: "test" shipping_addresses: [ { address: { firstname: "ss" lastname: "sst" company: "Company Name" street: ["test"] city: "Los Angeles" region: "CA" region_id: 12 postcode: "90210" country_code: "US" telephone: "123-456-0000" save_in_address_book: false } } ] } ) { cart { shipping_addresses { firstname lastname company street city region { code label } postcode telephone country { code label } available_shipping_methods{ carrier_code carrier_title method_code method_title } } } } }

6. setBillingAddressOnCart

mutation { setBillingAddressOnCart( input: { cart_id: "test" billing_address: { address: { firstname: "ss" lastname: "sst" company: "Company Name" street: ["64 Strawberry Dr", "Beverly Hills"] city: "Los Angeles" region: "CA" region_id: 12 postcode: "90210" country_code: "US" telephone: "123-456-0000" save_in_address_book: true } } } ) { cart { billing_address { firstname lastname company street city region{ code label } postcode telephone country { code label } } } } }

07.setShippingMethodsOnCart

mutation { setShippingMethodsOnCart(input: { cart_id: "test" shipping_methods: [ { carrier_code: "custom-1" method_code: "custom" } ] }) { cart { shipping_addresses { selected_shipping_method { carrier_code method_code carrier_title method_title } } } } }

08.createPaypalExpressToken

mutation { createPaypalExpressToken( input: { cart_id: "test" code: "paypal_express" express_button: true urls: { return_url: "paypal-return" cancel_url: "paypal-cancel" } } ) { token paypal_urls { start edit } } }

09.setPaymentMethodOnCart

mutation { setPaymentMethodOnCart(input: { cart_id: "test" payment_method: { code: "paypal_express" paypal_express: { payer_id: "test123" token: "VB-test" } } }) { cart { selected_payment_method { code title } } } }

10. Place order

mutation { placeOrder( input: { cart_id: "test" } ) { order { order_number } } }

Order is able to place using these process but Order email is taken as the Paypal account email address which was used to sign in.

[sheyandckap]

Found the solution and I hope this will help for all. There is a patch for this already. https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/support-tools/patches/v1-1-29/acsd-49849-customer-email-was-replaced-with-paypal-email.html?lang=en

[engcom-Bravo]

@sheyandckap Thanks for your contribution & collaboration over here

Hi @zexperto,

Kindly refer this document https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/support-tools/patches/v1-1-29/acsd-49849-customer-email-was-replaced-with-paypal-email.html?lang=en there is a patch already released.

Similar issue has been confirmed here https://github.com/magento/magento2/issues/37824

Hence we are closing this issue.

Thanks.