{"section":"known-issues","requestedLocale":"en","requestedSlug":"transaction-proceeds-through-authorization-and-settlement-despite-being-cancelled","locale":"en","slug":"transaction-proceeds-through-authorization-and-settlement-despite-being-cancelled","path":"docs/en/known-issues/Payments/transaction-proceeds-through-authorization-and-settlement-despite-being-cancelled.md","branch":"main","content":"## Summary\n\nIn scenarios where two sub-orders are created within the same checkout session (same order group), a transaction that has already been **cancelled** may unexpectedly proceed through the full authorization, anti-fraud, and settlement flow — resulting in an **unintended charge to the customer**.\nThis occurs due to a race condition between the cancellation and authorization requests. When both are triggered near-simultaneously, the authorization flow may operate on an outdated transaction state, bypassing the `Cancelled` status and completing as if the order were still valid.\n**Expected behavior:** Once a transaction reaches `Cancelled` status, no further authorization or settlement should be permitted.\n**Observed behavior:** The transaction transitions from `Cancelled` → `Authorizing` → `Settled`, generating a charge that should not have occurred.\n\n## Simulation\n\nUnable to reproduce in a controlled environment. The issue occurs intermittently in production and is more likely to manifest in **marketplace scenarios with split orders**, where cancellation and authorization can be triggered near-simultaneously by different services within the same order group session.\n\n## Workaround\n\nThere is no workaround available."}