Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Braintree error : Exception message: Your payment could not be taken. Please try again or use a different payment method. Declined Trace: #38686

Open
5 tasks
sumeetmagento opened this issue Apr 30, 2024 · 3 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.6-p3 Indicates original Magento version for the Issue report.

Comments

@sumeetmagento
Copy link

Preconditions and environment

  • Upgrade Magento version from 2.4.5-p1 to 2.4.6-p3
  • Magento version 2.4.6-p3

Steps to reproduce

1 - In production environment Place order with braintree creditcard or braintree Paypal
2 - We are getting an error of "Exception message: Your payment could not be taken. Please try again or use a different payment method. Declined Trace:" on magento logs
3 - This issue is only coming for few customers
4 - 3D Secure Verification is enabled
5 - Always request 3DS is enabled

Expected result

Order should be placed successfully.

Actual result

We are getting an error of "Exception message: Your payment could not be taken. Please try again or use a different payment method. Declined Trace:" on magento logs

On Braintree portal it is showing -
Status Processor Declined
Processor Response Text Declined(2046)
Additional Processor Response 2046: PAYER_ACTION_REQUIRED

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”.
Copy link

m2-assistant bot commented Apr 30, 2024

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:


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.

Copy link

m2-assistant bot commented Apr 30, 2024

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).
    1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
    1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
    1. 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!

@engcom-Delta engcom-Delta added the Reported on 2.4.6-p3 Indicates original Magento version for the Issue report. label Apr 30, 2024
@engcom-Dash
Copy link

Hi @sumeetmagento

Thanks for reporting and collaboration.

Verified the issue after upgrading the instance from 2.4.5-p1 to 2.4.7 but the issue is not reproducible.

Steps to reproduce
1 - In production environment Place order with braintree creditcard or braintree Paypal
2 - We are getting an error of "Exception message: Your payment could not be taken. Please try again or use a different payment method. Declined Trace:" on magento logs
3 - This issue is only coming for few customers
4 - 3D Secure Verification is enabled
5 - Always request 3DS is enabled

We are able to place the order successfully via braintree Paypal

Please refer the attached screenshots. Let us know if we missed anything.

Screenshot 2024-05-09 at 11 44 28 AM Screenshot 2024-05-09 at 11 44 55 AM Screenshot 2024-05-09 at 2 01 26 PM

@engcom-Dash engcom-Dash added the Issue: needs update Additional information is require, waiting for response label May 9, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.6-p3 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

3 participants