> For the complete documentation index, see [llms.txt](https://docs.inqud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inqud.com/crypto-recurring/explore/authorization.md).

# Authorization

The Authorization page of the Inqud Crypto Recurring allows you to view user-approved spending agreements for your plans. An authorization represents the user's agreement to be charged based on the plan's conditions and involves an actual ERC-20 approval transaction made by the user using their Web3 wallet.

### **What is an Authorization?**

An authorization is a user-approved spending agreement for a specific plan. It signifies the user's consent to be charged according to the plan's conditions. This process includes an ERC-20 token approval transaction performed by the user via their Web3 wallet, ensuring secure and verifiable permissions for recurring payments.

{% hint style="info" %}
An authorization is created when a user subscribes to a plan.
{% endhint %}

### Authorization parameters

<table><thead><tr><th>Parameter name</th><th width="249">Description</th><th>Value (example)</th></tr></thead><tbody><tr><td>id</td><td>ID of authorization.</td><td>"AGR-55502ab7-d322-465e-b856-51f0ca077dd2"</td></tr><tr><td>wallet</td><td>Wallet used by user to subscribe.</td><td>0x364371e1fbe635922b0f37d569f8d0e12b122822</td></tr><tr><td>cryptoCurrency</td><td>Blockchain and token approved by user for spending.</td><td>"ETHEREUM_USDT"</td></tr><tr><td>status</td><td>Authorization status.</td><td>GRANTED, REVOKED_BY_MERCHANT</td></tr><tr><td>subscriptionId</td><td>ID of subscription associated with authorization.</td><td>"SUB-df39a8ab-0bbc-464c-acae-c0ce265a4713"</td></tr><tr><td>initApprovalTx</td><td>Transaction hash were user approved tokens spending.</td><td>"0xbd01120e922a778cc2047cf089b4772b0323587eaea4996b6572dedb67f6e52a"</td></tr><tr><td>planId</td><td>ID of plan associated with authorization.</td><td>"PLAN-d5208959-5ced-41c7-9d9e-31923b6a22a6"</td></tr></tbody></table>

### Authorization balance

By clicking on an authorization record, a user can see real-time balance details of the given authorization. This includes:

| Parameter name | Description                                                                  | Value (example) |
| -------------- | ---------------------------------------------------------------------------- | --------------- |
| balance        | The current balance of the user's account associated with the authorization. | 1000            |
| allowance      | The total amount approved for spending under this authorization.             | 500             |
| transferable   | The remaining amount that can be transferred based on the authorization      | 500             |

### Authorization statuses

* **GRANTED**: The authorization is active, allowing payments to be processed according to the specified plan conditions.
* **REVOKED\_BY\_MERCHANT**: The authorization has been canceled by the merchant, and no further payments will be processed.

### Authorization status transitions

<img src="/files/1w42HXeXB3JiL4YQXwfU" alt="" class="gitbook-drawing">


---

# 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.inqud.com/crypto-recurring/explore/authorization.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.