{"section":"known-issues","requestedLocale":"en","requestedSlug":"transaction-stuck-in-approved-with-settled-payments-blocking-invoicing","locale":"en","slug":"transaction-stuck-in-approved-with-settled-payments-blocking-invoicing","path":"docs/en/known-issues/Payments/transaction-stuck-in-approved-with-settled-payments-blocking-invoicing.md","branch":"main","content":"## Summary\n\nA transaction whose payments were settled stays in `Approved` and never reaches `Finished`, leaving the order stuck in \"checking invoice status\". The settlement is recorded, and the connector responds successfully, but the payment never advances out of `Authorized` or `Settling`. Because a settlement record already consumes the payment's full value, every later invoice finds no balance left and fails.\nVisible symptoms:\n\n- Order stuck in \"checking invoice status\" / \"verifying invoice\"\n- Transaction in `Approved`, payment in `Authorized` or `Settling` on `/payments`, despite a settlement already recorded\n- Response from Gateway settlement: `The payment with Id = {paymentId} was not settled because the settlement value was 0.00` (`HTTP 500`)\n- OMS: `{\"error\":{\"code\":\"001\",\"message\":\"An error with Gateway has occurred\"}}`\n\nOn single-payment orders, the defect is silent — the transaction just sits in `Approved`. It only becomes blocking when the order generates more than one invoice.\n\n## Simulation\n\nNot reproducible on demand.\nTo confirm a case is this bug, check all three:\n\n1. `GET /api/pvt/transactions/{transactionId}/settlements` → `actions` sum to the full authorized value, `requests` is `[]`\n2. `GET /api/pvt/transactions/{transactionId}/payments` → a payment still in `\"status\": \"Authorized\"` or `\"Settling\"` while its `settlement` field is already populated\n3. `GET /api/pvt/transactions/{transactionId}/capabilities` → `\"minimumValue\": 0.01` even though settlements exist\n\n## Workaround\n\nThere is no workaround available."}