Not getting customer id in the brain tree transaction object response.

[prajeswari]

Preconditions and environment

Magento Version : 2.4.6 EE and 2.4.6 P1 EE

I am not getting customer id in the brain tree transaction response while using Magento 2.4.6 and 2.4.6 P1 EE with PWA venia-ui store. I have verified same in Magento 2.4.5 EE and 2.4.4 EE version I am getting customer id in the response.

Steps to reproduce

-Install PWA venia store and point it to any of Magento 2.4.6 EE instance. -configure braintree -And place an order with Brain Tree and verify the transaction response.

Expected result

Customer id should be there in the response

Actual result

Customer id is not coming in the braintree response Response In 2.4.6

Additional information

Posted issue on magento pwa-studio https://github.com/magento/pwa-studio/issues/4155

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 @prajeswari. 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-Dash. 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!

---

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

[engcom-Dash]

Hi @prajeswari ,

verified the issue in 2.4.7beta 1 instance the issue got reproducible,Hence we are confirming the issue. Kindly refer the below screenshots:

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-9369 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Dash]

Hi @prajeswari ,

As per the internal discussion we need some information from your end,Could you please tell me did the payment either in luma side with PWA setup or With Venia side with PWA setup???

Thanks.

[prajeswari]

Hi @engcom-Dash

I did the payment with venia side with PWA setup.

Thanks

[prajeswari]

Hi @engcom-Dash ,

Any update on this issue? I have a dependency on it.

[engcom-Dash]

Hi @prajeswari

Thanks for reporting and collaboration.

Verified the issue in PWA venia instance and the issue is reproducible.

We are not getting the customer id in the Braintree transaction object response.

Please refer the attached screenshot.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-9369

[github-jira-sync-bot]

:x: You don't have permission to export this issue.