> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/getting-setup/approvals-feature-guide.md).

# Approvals feature guide

## Overview

The Approvals feature allows you to create custom approval rules for crypto withdrawals and bank withdrawal requests made through your business account. By setting up approval rules, you can ensure that transactions require review and authorization from designated team members before they're processed.

## Creating Approval Rules

To create an approval rule, navigate to **Approvals → Approval Rules**, click **Create approval rule** and follow these steps:

{% hint style="info" %}
Only users with the [Owner role](https://docs.txn.io/getting-setup/back-office-user-roles.md) can create approval rules. You can create one rule per scope — one for Crypto Payouts and one for Bank Withdrawals.
{% endhint %}

### 1. Choose Your Rule Scope

In **Applies to**, select which type of transactions this rule will apply to:

**Crypto Payouts** — This scope covers:

* Creating payouts from crypto accounts
* Creating mass payouts via CSV upload
* Creating payout payment links

**Bank Withdrawals** — This scope covers:

* Bank withdrawal requests only

{% hint style="warning" %}
**Approval rules apply to dashboard-initiated transactions only.** Crypto payouts and bank withdrawals created via the API using an API key are processed without requiring approval, even if a matching rule is active.
{% endhint %}

### 2. Designate Approvers

In **Approvers**, select which users are authorized to approve or reject transaction requests under this rule. You can search users by name or email.

### 3. Set Required Approvals

In **Approvals required**, specify the minimum number of approvals needed for each transaction request that falls under this rule.

### 4. Self-Approval Settings

Decide whether transaction initiators can approve their own requests (**Initiator can approve the request**). By default, this option is disabled, meaning initiators cannot approve their own transactions.

Click **Create rule** and confirm with the 6-digit code from your authenticator app.

<figure><img src="https://1963856601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgfUDRstNYYBTf2futZ28%2Fuploads%2Fgit-blob-60a0008c9dc44b3d8c7e3c4b3ca04ba70a1febab%2FCreate%20Rule.png?alt=media" alt=""><figcaption><p>Creating a new approval rule</p></figcaption></figure>

## How Approvals Work

Once an approval rule is active:

**For Transaction Initiators:**

* Any transaction request you create that matches a rule will require the specified number of approvals before processing
* You can view the status of your requests on the **Approvals → Pending Requests** tab, and past requests on the **Request History** tab
* You can cancel your own request at any time (even if you can't approve it)
* If you're allowed to approve your own requests, you can both approve and cancel them
* You'll receive email notifications when your request is approved or rejected

**For Approvers:**

* You'll receive email notifications when a transaction requires your review
* All pending approval requests are visible on the **Approvals → Pending Requests** tab
* You can either approve or reject the request
* If even one rejection is received, the transaction request is canceled completely
* The transaction will only proceed once the required number of approvals is reached

## Managing Approval Rules

### Deleting Rules

Only users with the Owner role can initiate rule deletion. To delete a rule, open it on the **Approval Rules** tab, click **Delete** and confirm with your authenticator app code. The rule then enters a 24-hour cooling-off period before being permanently removed: it shows a countdown (**Deletes in**), and you can cancel the deletion with **Restore**. Until the rule is removed, you cannot create a new rule for the same scope. This safeguard helps prevent accidental deletions.

**Important:** If you delete a rule while transaction requests are still pending approval, those requests will still need to be resolved (approved, rejected, or canceled) according to the original rule requirements.

<figure><img src="https://1963856601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgfUDRstNYYBTf2futZ28%2Fuploads%2Fgit-blob-7b875a829b62d8514e4a0a8a5c467b805724d320%2FDelete%20Rule.png?alt=media" alt=""><figcaption><p>The rule is set for deletion and can be restored during the cooling-off period</p></figcaption></figure>

For questions about setting up approval rules or managing transaction approvals, contact support at <support@txn.io>.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.txn.io/getting-setup/approvals-feature-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
