{"section":"known-issues","requestedLocale":"en","requestedSlug":"checkout-cancels-transaction-after-creation","locale":"en","slug":"checkout-cancels-transaction-after-creation","path":"docs/en/known-issues/Payments/checkout-cancels-transaction-after-creation.md","branch":"main","content":"## Summary\n\nA transaction already approved (and in some cases captured) receives a cancellation request directly from the checkout:\n\n\n    An external application called to cancel this transaction Id = with Value RequestId = . Priority: default. Author: vtex-service::checkout::stable.\nThis cancellation request occurs due to a timeout when the checkout calls the payments route from the gateway, and the service takes too long to respond.\n\nThis happens when the `GatewayCallback` method is triggered at two different points in the order flow:\n\n\n\n1. **During the order processing stage** – when the endpoint `gatewayCallback/{orderGroup}` is called.\n2. **After the payment authorization** – when the endpoint `gatewayCallback/{orderGroup}/{messageCode}` is called.\n\nIn both cases, the `GatewayCallback`  performs a request to the payment gateway. If the gateway takes too long to respond, the same type of timeout error can occur in either scenario.\n\nTo clarify further:\n\n\n- The first call is a **POST request** to `gatewayCallback`, which occurs right after the user completes the checkout process.\n- The second call is a **GET request** to `gatewayCallback`, which is triggered during payment confirmation – this is when the shopper is redirected to the \"Order Placed\" screen.\n\n## Simulation\n\nSimulation is not possible.\n\n## Workaround\n\nNo workaround available."}