2XX
in the allocated time or returned a non-2XX status code. We will attempt for up to 3 days. Due to the retry behavior, you might receive an event more than once if a timeout has occurred. You might also never receive an event if no successful delivery was possible in the 3-day window.intent
for a transaction is set to capture
.
This allows us to perform various additional checks before proceeding with the capture. This also allows us the ability to hold a transaction in review.
As a consequence, this will sometimes result in multiple webhooks per transaction in case the first capture fails. In a normal situation, you would
only receive a transaction.captured
event, but in case of a failure to capture we will automatically retry. In this situation you may
receive a transaction.authenticated
webhook first, followed by a transaction.captured
event.
This same order of events will happen when the async_capture
property is set to true
in the transaction request, as this will always handle
the capture asynchronously from the capture.