{"section":"known-issues","requestedLocale":"en","requestedSlug":"debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field","locale":"en","slug":"debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field","path":"docs/en/known-issues/Payments/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md","branch":"main","content":"## Summary\n\n\nWhen utilizing the Firstdata connector for processing debit payments, our code is designed to expect the field TransactionState to be set as \"CAPTURED.\" However, we have encountered an issue where the provider is sending both \"CAPTURED\" and \"SETTLED\" values, which is causing an error to occur:\n\n\n    Error Message: Unknown Error on AutoSettle. There is an error in the XML document (1, 745). & Error executing the Settlement operation. Please refer to the inner exception. Connector: Firstdata. Message: Input string was not in the correct format.\n\n\n\n#### Simulation\n\n\nIt is not possible to simulate since it is an intermittent behavior that depends on the payment provider's response.\n\n\n#### Workaround\n\n\nN/A"}