Network and Session Problems During Payment

Do not infer a payment result from a timeout

A browser or app can lose its connection before receiving a response even when a provider has already processed the instruction. A page can also fail before the provider receives anything. The screen alone cannot distinguish these cases. Check the wallet, bank or card history and the merchant account before starting another payment.

Record the approximate time, method, amount, and any reference or error message. If a prompt is still visible, do not approve it twice. If a new prompt appears unexpectedly after reconnecting, verify the recipient and amount again.

Restore the session safely

Use a stable connection and reopen the official website or app from a known bookmark or store listing. Avoid links in unexpected messages. If the session asks you to sign in again, verify the domain and use your normal sign-in method; do not enter credentials into a page reached through a pop-up or unrelated redirect.

Never install a remote support app or share a screen containing a wallet PIN because a stranger says they can repair the network. The provider or merchant should be able to explain its official troubleshooting process without taking control of your phone.

Escalate with useful facts

If the provider history shows a transaction, contact the provider with its reference. If the provider shows success but the merchant account does not, contact the merchant with the same reference. If neither side shows a record, share the error and time with the merchant support team before retrying.

A weak network can make status updates arrive late; it does not change the need to protect credentials. Do not share OTPs to “refresh” a payment.

A page freezes when you press confirm

Avoid pressing again while the request may still be processing. Reopen the official wallet history on a stable connection and then check the merchant separately. Save any visible order reference before clearing browser data.