Recover a missed webhook in Starter Integration
Recover a stale invoice status after a missed webhook. Work through duplicate delivery, an absent event and a failed current read.
By Lars Holdgaard, Founder & CEO of Debitura

When a Debitura collection request looks stale, read the current request from your server using its saved request ID. Update the matching invoice row from that result. Keep the last confirmed state visible with a warning if the read fails and hide any old Continue link until you have a fresh response.
Reconcile existing invoice rows
- List the existing requests affected by the missed update. Keep the partner account, your client mapping, invoice row and Debitura request ID together. A collection request ID identifies the request. The case ID identifies the resulting case.
- Run a server-side
GET /collection-requests/{id}after a return from hosted setup, after a verified webhook or on a manual recheck. Read all affected known requests if a shared setup step could have changed more than one. Use the same environment as the original request. - Replace the display with the current status and outcome from the response. Show Continue only when the present status requires customer action and the current response provides its link. If the read fails, label the last checked result with its time and a refresh error. Keep stale links out of view and retry the read using your retry policy.
Three fictional recovery decisions
| Existing request | What happened | Current read or error | Display and next owner |
|---|---|---|---|
| Request A · INV-41 | The same verified event arrived twice. | 10:03 UTC · submitted, case ID present, case status still under verification. | Show the case and its actual status. Deduplicate the repeated event in the handler and record recovery against the existing invoice row. |
| Request B · INV-42 | The user returned from hosted setup and no event was observed. | 10:06 UTC · awaiting_signature, current action link present. | Show Continue from this read. The user can open the linked action and the integration rechecks the request on return. |
| Request C · INV-43 | The user selected Refresh and the current read timed out. | 10:08 UTC · No new state. Last confirmed result at 09:58 UTC was needs_fixing. | Keep the previous status labeled as last checked, show the refresh error and hide Continue. The integration owner checks the request mapping and logs if retries keep failing. |
Escalate with evidence
Give the implementation owner the request ID, invoice reference, environment, last successful read time, failed attempt time and error class. Keep keys, signing secrets, raw customer details and hosted action URLs out of the recovery log. A redirect, a missed event and a timeout each leave the current state unconfirmed until a successful read. Use the existing request for recovery. A fresh submission has a different purpose and should follow the documented submission flow.
Copy the recovery log
Paste the tab-separated rows into a spreadsheet. Keep the time zone on every timestamp and record who owns each open check.
| Invoice row | Request reference | Trigger | Attempt time UTC | Last confirmed status | Current read result | Continue link | Next owner |
|---|---|---|---|---|---|---|---|
| INV-41 | Request A | Repeated event | 10:03 | submitted | Case under verification | Hidden | Integration |
| INV-42 | Request B | Hosted return | 10:06 | awaiting_signature | Current link returned | Shown | User |
| INV-43 | Request C | Manual refresh | 10:08 | needs_fixing at 09:58 UTC | Timeout | Hidden | Integration owner |
Read the integration guides
Use the Starter Integration recipe and collection-request reference for the request shape, signature verification and event deduplication. The embedded debt collection guide covers how the collection step fits into your product.
See how to embed debt collection
References
-min.webp)
Sign up to our newsletter
Get updated on best practices, tips and tricks about international debt collection and accounts receivable management.

.webp)