Skip to main content

What to Do When Still Being Charged After Match

Covers confirming you clicked Stop Stream and received confirmation, checking Multiview to verify stream is not still active, understanding that stopping the stream is required (closing browser tabs d

Written by Julian Rodrigues
Updated today

Overview

If you stop a match but streaming charges continue, the stream itself is still running. Closing the browser tab does not stop the stream or billing. You must explicitly stop the stream using the Stop Stream button or configure automation to stop it automatically.


Check That You Stopped the Stream

1. In Stream View, click the Stop button in the top right of the screen


2. Select Yes, stop stream in the confirmation dialog


3. Once confirmed, you stop incurring charges for streaming and highlights


If you closed the browser tab without clicking Stop Stream, the stream is still running and charges continue.


Verify Stream Status in Multiview

1. Click the Streaming tab in the left-hand dashboard


2. The Multiview page displays all active streams in a grid layout


3. Check if the match stream is still shown with a live indicator


4. If the stream appears in Multiview, it is still active and must be stopped


To stop it:


1. Click on the stream tile in Multiview to open detailed view


2. Click Stop Stream


3. Confirm the stop action


Use Automation to Prevent This Issue

Configure Auto Stream settings to automatically stop streams after matches end:


1. During stream creation or in stream settings, set Stream Stop to X minutes after match ends


2. The stream will automatically stop at the configured time


3. This ensures streams stop even if you forget to manually stop them


Important Points

* Charges begin as soon as you click "Yes, start stream"


* Charges continue until you stop the stream


* Closing browser tabs does not stop the stream or billing


* You must manually stop the stream or use automation to stop it


* Use Multiview to monitor all active streams and catch any that should have stopped


Did this answer your question?