{"section":"known-issues","requestedLocale":"en","requestedSlug":"error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359","locale":"en","slug":"error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359","path":"docs/en/known-issues/Payments/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md","branch":"main","content":"## Summary\n\n\nThe 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.\n\n\n##\n\n## Simulation\n\n\nIt cannot be simulated as we depend on the provider's response.\n\n\n##\n\n## Workaround\n\n\nIf the payment on the provider side is already canceled\n\n    \\{\"returnCode\":\"355\",\"returnMessage\":\"Transaction already cancelled.\"\\}\n\nThe product support team has the option to utilize an internal API, '`force-cancel-status`', to update the payment and transaction status to 'canceled.'"}