magento 2 Braintree error verifyCard options must include a BIN.

[sumeetmagento]

Preconditions and environment

We are using Magento version - 2.4.6-p3 after an upgrade from 2.4.5-p1

Steps to reproduce

1 - Add product to the cart
2 - Go to the checkout page page
3 - Try to place order via Braintree credit card with 3D Secure Verification should be enabled
4 - We will not be able to do place order because we are getting an error on browser console

Expected result

The order should be placed successfully.

Actual result

Getting this error on browser console -

3d-secure.js:135 3dsecure validation failed 
n {name: 'BraintreeError', code: 'THREEDS_MISSING_VERIFY_CARD_OPTION', message: 'verifyCard options must include a BIN.', type: 'MERCHANT', details: undefined}
code: "THREEDS_MISSING_VERIFY_CARD_OPTION"
details: undefined
message: "verifyCard options must include a BIN."
name: "BraintreeError"
type: "MERCHANT"
[[Prototype]]: Error

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]

Hi @sumeetmagento. 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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]

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: 👇

• 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 @sumeetmagento

Thank you for reporting and collaboration.

Verified the issue on magento 2.4.6-p3 after upgrading from 2.4.5p1 and the issue is not reproducible.

Able to place order successfully via Braintree credit card with 3D Secure Verification.
Please refer the screenshot.

[engcom-Dash]

Hi @sumeetmagento

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.