Improved Webhook Timing for Batched Underwriting Results
What's New?
The Batched_UnderwritingComplete event now fires when all underwriting services have finished processing for a merchant application. Because underwriting services run independently, this webhook may fire more than once for a single application — once at the 15-minute timeout if any services are still pending, and again as each remaining service completes. Previously, this webhook often fired before results were available.
See Batched Underwriting Results in our Guides for more information.
Webhook Event Timing
The webhook behaves differently depending on whether all underwriting services complete within the 15-minute timeout window:
| Scenario | Result |
|---|---|
| All services complete before the timeout | One webhook fires containing results from all services. |
| One or more services exceed the timeout | A webhook fires at the 15-minute mark with available results, then an additional webhook fires each time a late service completes. |
Example
A merchant application has 3 underwriting services configured to run: InfiniScore Social, USPS Address Validation, and LegitScript Direct. After 15 minutes, only InfiniScore Social is complete.
- Webhook 1: fires at the 15-minute timeout with the results of InfiniScore Social only. USPS Address Validation and LegitScript Direct are not included.
- Webhook 2: USPS Address Validation completes 2 minutes after the timeout. A webhook fires with InfiniScore Social and USPS Address Validation results. LegitScript Direct is not included.
- Webhook 3: LegitScript Direct underwriting completes 3 minutes later. A webhook fires containing the results from all three services — InfiniScore Social, USPS Address Validation, and LegitScript Direct.