Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Known issues
Authorization status is stuck for asynchronous transactions with 2 or more payments when the first one is canceled.
Authorization status is stuck for asynchronous transactions with 2 or more payments when the first one is canceled.
ID: 929517
Backlog
Published on 11/2/2023
Last update on 11/2/2023

Summary

When a transaction has multiple payments and becomes asynchronous due to Sherlock or Defense mode, and if the first payment authorization attempt fails, it can result in the other payments being stuck in an "Authorized" status. This is because the entire transaction is canceled, but our worker does not recognize this and proceeds with an authorization attempt for the second payment. Consequently, the second payment cannot be canceled, as the transaction has already been canceled, and it does not allow a cancellation request.

Simulation

Create a transaction with two payments, in which Defense Mode or any other feature that makes the transaction asynchronous is activated. Then, use a custom provider connector to decline the first payment authorization attempt while approving the other one.

Workaround

N/A

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback