Browse all guides
All guides
Docs

Stopping a contract

Cancel a contract before work starts, or stop one that is running, and know what happens to the money.

AppHandlers Updated 2026-10-03

A contract ends in one of two ways, and the difference is the money. Before any work has started you are cancelling, and nothing is charged. Once work is under way, whoever stops decides how the rest is settled.

Cancelling before work starts

If you have opened a contract but no work has started, the one action on it is Cancel this contract. The confirmation asks Cancel this contract? and the button inside it reads Cancel. Nothing has been paid, so nothing is charged, and the contract closes.

If you stop it

While a contract is running, your action is Stop and pay for the work. When nothing has been billed yet, the same button reads Stop this contract. The confirmation says which case you are in: You pay for what has been done so far. or Nothing has been worked, so nothing will be paid.

Stopping pays for the work that has already happened. Any stretch still in progress is closed into a bill and settled straight away, so the AppHandler is paid for what was delivered. If that work came to more than the amount you locked, the extra is not paid.

If the AppHandler stops it

The AppHandler can stop at any time with Stop working. Work that is unfinished is not paid for, and a bill they have raised that you have not approved is cancelled.

What happens to the money either way

The money you locked that the work did not use comes back to your spendable balance. Money that has already been released stays where it is: stopping does not take back a bill you approved.

While AppHandle is checking a dispute

You cannot stop a contract that is under review. AppHandle decides that first, and the contract says so if you try.

Where to go next

Disputes explains what happens when something is wrong, and The work clock and your bills covers the bills themselves.