Closed n2diving-dgx closed 3 years ago
Hi @n2diving-dgx. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release
For more details, please, review the Magento Contributor Assistant documentation.
Please, add a comment to assign the issue: @magento I am working on this
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, please join the Community Contributions Triage session to discuss the appropriate ticket.
:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel
:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel
Hi @engcom-November. 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).Details
If the issue has a valid description, the label Issue: Format is valid
will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid
appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description
label to the issue by yourself.
[ ] 3. Add Component: XXXXX
label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop
branchDetails
- 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.
This following issue is only happening with Venmo.
When a customer places an order using Venmo:
1.) They are not brought to the order success screen that provides them with an order number.
2.) They are not emailed an order confirmation.
3.) The order does not show up in Magento.
4.) The payment IS taken/received and it shows up correctly in Braintree. An order number is assigned correctly and shows in Braintree only, but the rest of the order process/experience with Venmo/Magento is broken.
Support at Gene Commerce, the ultimate maintainer of this component has advised "The team confirmed that this issue will be fixed with the next Magento release which will roll out on the 12th of October. " I assume they mean M2.4.3-p1
Upon upgrading from M2.3.7-p1 to M2.4.3, customers attempting to checkout and place orders using the Braintree Venmo payment method fail with Error message "Something went wrong with your request. Please try again later." There is no order received by Magento.
However, most IMPORTANTLY, the customer Venmo account is charged even though no order is successfully placed.
Steps to reproduce....
Install vanilla Magento 2.4.3 with Luma store sample data
In Magento 2.4.3 admin, configure Braintree Payments (by GENE Commerce)
Navigate to frontend Luma Store URL on mobile device with Venmo app installed and configured (tested with both iOS 14.7.1 + Safari and Android 11 + Chrome)
Note: Although a live Venmo account must be used to test with the Venmo app, the Sandbox setting in the store Braintree Payments credentials will not actually capture genuine funds from the account. The Sandbox setting will successfully override the genuine account and switch to the "venmojoe" account for sandbox testing.
In Magento Admin, view Sales > Orders and confirm no related order is present.
From CLI, in var/logs view system.log and find the following error for each payment attempt...
Login to Sandbox Braintree Gateway URL
The expected behavior is customer is able to checkout with Venmo payment method to place a Magento order successfully with an order number being displayed.
Unfortunately, the actual results when attempting to place order in Magento with Braintree Venmo payment method are only that the customer Venmo account will be sandbox "charged" for the total amount of the order. However, no order is received and recorded by Magneto and no order success page with an order number is displayed to the customer. Instead the customer receives an error message instructing them to try again. Multiple attempts by customer to place order using the "Pay with Venmo" button will result in multiple sandbox charges to customer but no orders.
Behavior is similar in Production mode on our live store with live Braintree credentials. Other Braintree payment methods in our live store (ApplePay, GooglePay, PayPal, and cards) work as expected, issue appears to be limited to Venmo payment method. Problem was discovered after customers asked WISMO because their Venmo account had actually been charged and funds collected, in some cases multiple times.
This is a SERIOUS high priority S1 bug, customers funds are collected but no order or audit trail, and if not an existing customer then not even any customer contact information at all, in Magento. Only work around for Magento 2.4.3 is to disable the Venmo payment method which was working for us in Magento 2.3.7-p1 (and seemingly tested OK in 2.4.2 but was never in production). An emergency MQP patch will be required to use the Venmo payment method with Magento 2.4.3