Loggedin customer address comes twice when we are placing order with Payflow credit card

[brianrootways]

trafficstars

Preconditions and environment

• Magento version - 2.4.6-p3
• Anything else that would help a developer reproduce the bug

Steps to reproduce

when I place an order: logged in customer > choose to add new address at shipping step > choose save to address book > ship here > new ship address selected > credit card method (Payflow credit card) > select the "My billing and shipping address are the same" checkbox under credit card method so that the order will use the new address as bill address > place the order

I see that the newly added address saved to the customer account twice. Please check the attached video for your reference.

Expected result

Customer address must be saved 1 time.

https://github.com/magento/magento2/assets/68637204/c306219c-47d2-4cb7-bfd1-495026902212

Actual result

Customer address must be saved 1 time.

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 @brianrootways. 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.

[brianrootways]

@engcom-Dash You can reproduce the issue even in the vanilla Magento 2.4.6-p3 version. Please check from your side. Let us know if you need anything else.

[engcom-Dash]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Dash, here is your Magento Instance: https://c431f0b00f162e5c6627970e4e850b07.instances-prod.magento-community.engineering Admin access: https://c431f0b00f162e5c6627970e4e850b07.instances-prod.magento-community.engineering/admin_0fb7 Login: ff480150 Password: 4f3619132e0d

[engcom-Dash]

Hi @brianrootways

Thanks for reporting and collaboration.

Verified the issue on magento 2.4.6-p3 and 2.4.7-beta 2 but the issue is not reproducible.

We are seeing the address save only once. Please refer the attached screenshots.

Will test in 2.4 dev instance and update the results.

[brianrootways]

@engcom-Dash can you please give me instance of 2.4.6-p3 we will check and replicate the issue for you. We have checked and we are able to generate from our side.

[brianrootways]

@engcom-Dash I have set up vanilla Magento 2.4.6-p3 on our server and added single category and one product for testing. We put payflow pro settings and paypal express settings for one store. When I try to checkout with Payflow credit card with newly address we are getting duplicate address save in the customer address area. Here I give you a video for your reference.

https://github.com/magento/magento2/assets/68637204/5466c493-963d-4ff5-ba78-de9b154b4de2

[engcom-Dash]

Hi @brianrootways

Thanks for reporting and collaboration.

Verified the issue in magento 2.4 dev instance and the issue is reproduce. Hence, confirming the issue.

We are seeing when placing order with Payflow credit card the customer address is coming twice in the address book.

Please refer the attached screen recording.

https://github.com/magento/magento2/assets/60198592/55f1cb9c-9161-4080-a1bb-90cafa126aa5

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-11506 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.

[github-jira-sync-bot]

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

[brianrootways]

@engcom-Dash Please try to fix this issue ASAP so we can go live.

[brianrootways]

@engcom-Dash, Any update? Please try to fix this issue ASAP so we can go live.

[brianrootways]

Any update? Please try to fix this issue as soon as possible so we can go live. This is a serious issue for the customer.