{"section":"known-issues","requestedLocale":"en","requestedSlug":"payment-does-not-advance-to-canceled-after-a-successful-cancellation-call","locale":"en","slug":"payment-does-not-advance-to-canceled-after-a-successful-cancellation-call","path":"docs/en/known-issues/Payments/payment-does-not-advance-to-canceled-after-a-successful-cancellation-call.md","branch":"main","content":"## Summary\n\nA cancellation/refund is requested on a transaction; the eRede REST connector accepts it and returns success, but the payment never transitions to Canceled — it stays in its pre-cancellation status indefinitely. The gateway logs the successful connector response in the transaction interactions and then stops, without completing the state transition.\n\n## Simulation\n\nNot reproducible on demand — the failure depends on the connector's asynchronous cancellation response in a live transaction, with no deterministic trigger identified.\n\nTo confirm a case is this KI, check the transaction:\n\n\n1. Affiliation is eRede REST (`erederest`).\n2. A `Cancel Request Url` interaction to `api.userede.com.br/erede/v1` exists.\n3. The paired response reads `HttpStatusCode:Accepted` with `\"returnCode\":\"360\"`.\n4. No status-change interaction follows it, and the payment is still in its pre-cancellation status.\n\n## Workaround\n\nN/A"}