> For the complete documentation index, see [llms.txt](https://docs.abapays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abapays.com/trust-and-safety/kill-switches.md).

# Kill switches

All of them stop the agent, not just the UI — enforced by the same code path (or the contract itself) regardless of which channel or credential is calling in, MCP and A2A included.

* **Per-channel pause** — an operator can pause just the MCP surface without touching Telegram/WhatsApp/X.
* **Global pause** — the contract itself can be paused; payments revert while paused, but refunds deliberately stay callable so anyone already charged can still be made whole.
* **Relayer kill switch** — instantly disables the agent-initiated payment path system-wide, on-chain, independent of anything the backend does. A compromised backend cannot re-enable itself.
* **Per-credential rate limiting** — every money-moving call is rate-limited per API key, on top of the PIN requirement.
* **PIN lockout** — escalating lockout on repeated failed PIN attempts.

The two contract-level switches, verbatim:

```solidity
/// Instantly disables the agent-initiated path system-wide, on-chain --
/// independent of anything the backend does. A compromised backend
/// cannot re-enable itself.
function setRelayer(address newRelayer) external onlyOwner {
    relayer = newRelayer;
}

/// payBillFor reverts while paused. Refunds deliberately stay callable
/// so anyone already charged can still be made whole.
function pause() external onlyOwner { _pause(); }
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abapays.com/trust-and-safety/kill-switches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.