Flow Payment Recovery Hub
Tenant: global | Fokus: snabb recovery och tydligt ägarskap
Recovery decision lane
When failed, pending or disputed payment rows appear, the next step should be the owner lane that can repair them, not only the summary view.
Keep failed, pending and matched visible together.
Route to operations, disputes or confidence depending on the queue.
Use the launch report once recovery is back in control.
Payment recovery path
The goal is to clear failed payments first, then protect the revenue signal and give a clean launch handoff when recovery is done.
Retry the failure batch and review reason-codes.
Check reconciliation drift and close the evidence trail.
When revenue is clean, export proof and launch the pack.
0
100%
0
0%
Stable
0
| Owner lane | Owner | Backlog | Aging | SLA | Next action |
|---|---|---|---|---|---|
| Checkout failures | Payments ops owner | 0 | fresh | ok | Kör retry batch och uppdatera reason-codes. |
| Reconciliation drift | Finance reconciliation owner | 0 | fresh | ok | Replay events + lås closure evidence. |
| Chargeback/dispute | Dispute automation owner | 0 | fresh | ok | Routa till dispute-lane och eskalera P1. |
| Action lane | Signal | Priority | Runbook |
|---|---|---|---|
| Retry orchestration | 0 failed attempts | P3 | Retry i batch + fallback kanal. |
| Reconciliation sweep | 0 pending / 0 failed | P3 | Replay, compare, close med evidence. |
| Revenue assurance | 0 recovered | P3 | Optimera copy, routing, callback fallback. |
Snabbt till omkringliggande payment-lanes när recovery behöver mer stöd.