Menu
Feedback
Start here

Known issues

Known issues
delayToAutoSettleAfterAntifraud triggering automatic capture even without antifraud
Payments
•
ID: 369633
Backlog
Published on5/8/2023
•
Last updated on5/8/2023
1 min read

Summary

When 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.

On 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.

For 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.

Simulation

To 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).

Workaround

N/A

Contributors
1
Photo of the contributor
+ 1 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Contributors
1
Photo of the contributor
+ 1 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX Community
Join our community
Request VTEX support
For personalized assistance, contact our experts
Open a support ticket
GitHubDeveloper PortalCommunityFeedback