Build one timeline with named events
| Event | Useful evidence | What it does not prove |
|---|---|---|
| Request submitted | Account timestamp and reference | Approval or release |
| Review completed | Recorded status or support explanation | Receipt by a payment provider |
| Payment released | Transfer reference and route | Final credit to the destination |
| Funds received | Destination timestamp | The same speed on future requests |
Test the shortest-time interpretation
Our hypothetical case uses an 18-hour approval period and a 12-minute transfer. The total is 1,092 minutes: 18 hours 12 minutes. The 12-minute figure accurately describes the second stage but not the complete request-to-receipt experience. This is a calculated example, not a transaction we performed.
Identify exclusions before comparing claims
Check whether an advertised window excludes incomplete verification, business-day boundaries or a receiving-bank delay. Record the amount and currency too. Card routes, wallet routes and blockchain transfers introduce different participants and records; they should not be compressed into one universal number.
Ask support a question it can answer
For an existing delay, ask which stage is pending, when its clock started and which published condition applies. Supply a reference through the official support channel. Keep passwords, PINs and unredacted identity records out of public discussions. A demand for another payment to unlock a withdrawal deserves independent scrutiny, not an automatic transfer.
State a measured conclusion
One documented request can establish an observed time for that request. Repeated observations with a defined sample can support a broader description, but only within that sample's conditions. Our review method keeps observed results separate from an operator's advertised window.
