Check for a duplicate request before retrying
A frozen screen can leave uncertainty about submission. A second click is not a reliable way to resolve it.
The distinction that matters
Use transaction history and confirmation messages to establish whether the first request was created. Compare IDs, amounts and timestamps. Two visible records may represent a duplicate, a retry or two different stages, so do not cancel one at random. Ask the operator to identify which requests are active.
A worked example
You press submit, the page times out, then history shows a request for the expected amount. That is evidence to investigate before trying again. If a second request also appears, write down both references and ask whether both can proceed, rather than assuming one is only a display copy.
Your next steps
- Check history before resubmitting.
- Preserve any confirmation or error wording.
- Compare the request identifiers.
- Ask support to clarify the active records and any corrective step.
Where this answer stops
Northline cannot determine whether your request reached a server. Avoid changing the underlying balance while reconciling it. A timeout proves that a response was not received in time, not that no transaction was created.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction