{"section":"known-issues","requestedLocale":"en","requestedSlug":"delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud","locale":"en","slug":"delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud","path":"docs/en/known-issues/Payments/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md","branch":"main","content":"## Summary\n\n\nWhen the transaction does **NOT** have antifraud, it takes the shortest value between `delayToAutoSettle` and `delayToAutoSettleAfterAntifraud`. In this case, the `EarlySettlementWorker` is responsible for capturing, which is the worker for early capture. Technically, it is the worker that is called after the antifraud performs, but when there isn't one, it starts its countdown after payment authorization.\n\nOn the other hand, in the scenario where antifraud **EXISTS**, it behaves as expected: whichever comes first, is called. Automatic capture starts the countdown after payment approval. Early capture starts the countdown after antifraud approval.\n\nFor example, if `delayToAutoSettle` is equal to 1 minute and `delayToAutoSettleAfterAntifraud` is equal to 1 second, and antifraud is called and approved before 1 minute after payment authorization, then the `EarlySettlementWorker` will be called.\n\n\n##\n\n## Simulation\n\n\nTo simulate, it is necessary that the connector in question is sending different periods for delayto[...]. Considering that this is configured, it is necessary to create a payment condition without an associated antifraud. Proceed to place an order and verify the time it takes for the settlement to be called (which will be the reference for `delayToAutoSettleAfterAntifraud` and not `delayToAutoSettle`).\n\n\n##\n\n## Workaround\n\n\nN/A"}