{"section":"known-issues","requestedLocale":"en","requestedSlug":"when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed","locale":"en","slug":"when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed","path":"docs/en/known-issues/Payments/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md","branch":"main","content":"## Summary\n\n\nAt times, errors may occur while processing our operations through the gateway. In the case of Firstdata's connector, an error may arise immediately after the settlement approval on our side. To sort out this, we need to request a settlement again. However, due to idempotency, the provider does not send an \"approved\" response again, which can cause the transaction to become stuck in a \"settling\" status until a new status update is provided.\n\n\n##\n\n## Simulation\n\n\nIt's not possible to reproduce because it's intermittent.\n\n\n##\n\n## Workaround\n\n\nThere's no workaround available"}