Live: recognise a request, a revision and a receipt
In a live interface, the stream, score and market panel may update at different moments. Pressing a button sends a request, which can remain pending, return a revised price, be rejected or produce an accepted receipt. These stages have different consequences. Check the final account history instead of relying on an animation or a delayed video frame. The stream may show an event after the market has already moved.
If the screen stops responding, inspect history before repeating a tap. A second tap might create a second request. Record the event, market, amount, local time and time zone. When the status remains unclear, use the provider's published support contact and ask for the outcome of that particular attempt. An absent visual confirmation is not proof that an action was not processed.
Know the service's revision rule
Find out what happens when a price changes before acceptance. Does the provider ask for confirmation again, reject the request or apply another published method? Read its rules for a suspended market, interrupted match and corrected result. Another provider's approach may differ. The accepted receipt is more reliable than the earlier price on a changing screen. If there is too little time to read the final state, leaving the market is a valid choice.
For a later support case, record the sequence: what the screen showed before the tap, after the tap and in account history. Include any reference number. This helps a support team locate one transaction without guessing from a broadcast frame.