Menu
Feedback
Start here

Known issues

Known issues
Error in the cancellation process. ERedeRest and E-Rede V2 only allows cancelation when the returnCode is 359
Payments
ID: 740084
Backlog
Published on1/26/2023
Last updated on12/1/2023
1 min read

Summary

The legacy connectors, ERedeRest and E-Rede V2, initiate cancellations by sending a request to the provider and expect a "returnCode":"359" indicating a successful cancellation. Any other code is interpreted by our gateway as an undefined status, causing the transaction to get stuck in a cancelling state. Even though in some cases, the refund/cancellation request is successful. This led to repeated cancellation attempts, even when the cancellation had already been processed by the provider.

Simulation

It cannot be simulated as we depend on the provider's response.

Workaround

If the payment on the provider side is already canceled

{"returnCode":"355","returnMessage":"Transaction already cancelled."}

The product support team has the option to utilize an internal API, 'force-cancel-status', to update the payment and transaction status to 'canceled.'

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX Community
Join our community
Request VTEX support
For personalized assistance, contact our experts
Open a support ticket
GitHubDeveloper PortalCommunityFeedback