# Account

An **account** represents a shared multisig wallet managed by a group of users.

## Account details

To access account details, go to **Account** in the main menu.

In the upper part of the page, you can find essential information about the account:

**Total balance**

The total value of all assets held by the account, converted to the base currency.

This value reflects both collected and uncollected funds.

***

**Uncollected balance**

The total amount of funds that were received but not yet collected to the account base address, converted to the base currency.

***

**Uncollected invoices**

The number of invoices that currently have payments that haven't yet been collected.

***

**Current nonce**

The latest transaction nonce used by the account smart contract.

This value shows how many transactions were already processed and helps avoid transaction conflicts.

***

**Account address**

The smart contract address representing the account on the selected blockchain network.

This address is used as the main destination for incoming funds and can't be modified.

***

**Account name**

The label for the account that helps distinguish it from other accounts.

This value can be modified anytime.

The information below is divided into tabs.

{% tabs %}
{% tab title="Assets" %}
On this tab, you can view a list of all assets held on the account, including their balances and value in the base currency.

The following information is provided about each asset:

**Currency**

The asset alphabetical code, logo, and full name.

***

**Balance**

The amount of the asset held on the account, in the asset units.

***

**Balance in base currency**

The value of the asset converted to the account base currency.
{% endtab %}

{% tab title="Members" %}
On this tab, you can view and manage the members and signing policy of the account.

#### Member cards

The upper part of the tab shows a set of member cards that represent wallets associated with the account.

Each card provides the label assigned to the member and the underlying blockchain address.

Members marked with the **eye icon** have read-only access to the account.

#### Confirmation rules

The lower part of the tab contains the **Confirmation rules** section, which defines who can approve transactions and how many approvals are required.

**Signers**

The list of addresses and names that have full control over the account.

Signers can create, sign, execute, and decline transactions.

Each row shows the signer label (if available) and the wallet address.

***

**Required signatures**

The number of signer approvals that must be collected before a transaction can be executed.

The ratio, such as `1/3`, shows how many signatures are required out of the total number of signers.

Transactions remain pending until the required number of signatures is collected.

{% hint style="success" %}
View [Manage signers and required signatures](#manage-signers-and-required-signatures) for step-by-step instructions.
{% endhint %}
{% endtab %}

{% tab title="Settings" %}
On this tab, you can manage integration and security settings for the account, including the callback secret and API keys.

#### Callback secret

The **Your callback secret** section provides the **Regenerate** action that issues a new secret. Regeneration invalidates the previous secret and updates the value used for verifying callbacks.

#### API key management

The **API key management** section lists API keys used to access the account through integrations.

The table includes the following columns:

**Name**

The label assigned to the key.\
This value helps identify where the key is used.

***

**Key**

The shortened representation of the API key, for example `094j8...9h34a`.\
The full value is shown only when the key is created.\
For security reasons, it is not possible to restore the full key from this page.

***

**Created at**

The date and time when the key was created.

***

**Revoked at**

The date and time when the key was revoked.\
For active keys, the value is shown as `—`.

{% hint style="success" %}
View [Configure callback secret and API keys](#configure-callback-secret-and-api-keys) for step-by-step instructions.
{% endhint %}
{% endtab %}
{% endtabs %}

## Common use cases

The **Account** page helps with daily monitoring and administration of the account. This section describes common scenarios step by step.

### Rename the account

You can modify the account name anytime.

{% stepper %}
{% step %}
Go to **Account** in the main menu and select the required account in the header.
{% endstep %}

{% step %}
Click the **pencil icon** next to the account name and enter a new value.
{% endstep %}

{% step %}
In the **Edit account name** popup, enter the new account name, up to 32 characters long.
{% endstep %}

{% step %}
Click **Save** to confirm changes.
{% endstep %}
{% endstepper %}

The changes are applied immediately. The smart contract address, confirmation rules, and accesses remain unchanged.

### Manage signers and required signatures

Add new signers and adjust account settings that affect confirmation rules.

{% stepper %}
{% step %}
Go to **Account** in the main menu and switch to the **Members** tab.
{% endstep %}

{% step %}
Click **Edit** in the **Confirmation rules** section.
{% endstep %}

{% step %}
**To add a new signer:**

Click **Add signer** and enter a new signer address in the corresponding field. The system validates the address format and network before allowing you to proceed:

* If the entered address has an invalid format or doesn't belong to the expected network, the `Invalid address format` error appears and the changes aren't saved.
* If the entered address is already in the signer list, the `Address is already added` notification appears and the address isn't duplicated.

**To remove a signer:**

Click the **bin icon** in the corresponding signer row.
{% endstep %}

{% step %}
Adjust the **Required signatures** value to set how many signatures are needed to execute transactions:

* If there is only one signer, confirm that **Required signatures** is set to `1/1` by default and that editing is disabled.
* If the account has more than one signer, click **Edit**, then adjust the **Required signatures** value in the `X/Y` format, where `Y` is the number of signers and `X` is less than or equal to `Y`.

{% hint style="danger" %}
If you set `X` equal to `Y`, review the warning that explains the risk of losing funds if any single account becomes unavailable, then save the changes only if this configuration is acceptable.
{% endhint %}

{% hint style="info" %}
When signers are added or removed, the `Y` value in `Required signatures` updates to match the current signer list, and the editing control reflects the updated limits immediately.
{% endhint %}
{% endstep %}

{% step %}
Click **Save**.

The **Sign transaction** popup appears with the note that the action requires collecting a certain number of signatures before it can be completed.
{% endstep %}

{% step %}
Review the changes and click **Sign**.
{% endstep %}
{% endstepper %}

The changes are processed according to the current confirmation rules. New rules will be applied once the transaction is properly confirmed.

### Configure a callback secret and API keys

Set up technical integration with external systems through [callbacks](https://docs.defi.b2binpay.com/get-started/key-terms#callback) and API access.

{% stepper %}
{% step %}
Go to **Account** in the main menu and switch to the **Settings** tab.
{% endstep %}

{% step %}
In the **Your callback secret** section, click **Regenerate** to issue a new callback secret, then update this value in your external systems.
{% endstep %}

{% step %}
In the **API key management** section, click **Generate API key**.
{% endstep %}

{% step %}
In the **Generate API key** popup, enter the name for the API key and click **Generate**.
{% endstep %}
{% endstepper %}

The newly generated key will be displayed in the **API key is generated** popup: make sure to copy it and store it securely, as it only reveals once in this popup.

The new API key entry is added to the list where you can revoke it anytime.

### Create a new account

Create a new multisig account and define its initial configuration.

{% stepper %}
{% step %}
In the topbar, expand the **account select**.
{% endstep %}

{% step %}
Select **Create new account**.
{% endstep %}

{% step %}
In the **Create account** popup, click **Create**.

If a popup appears with the text “Creating new account will discard all unsaved changes,” decide whether to continue and click **Proceed** to move on or **Cancel** to keep working with the current account.
{% endstep %}

{% step %}
In the **Create new account** popup:

* Enter the account name.
* Add one or more members.
* Specify the number of signatures required for transaction confirmation.

Then click **Create account**.
{% endstep %}

{% step %}
In the **Confirm new account** popup, verify the summary of **Account name**, **Members**, **Required signatures**, and then click **Confirm**.
{% endstep %}
{% endstepper %}

The changes are processed according to the configured confirmation rules.

### Disconnect the wallet

Log out from the current account and return to the login screen.

{% stepper %}
{% step %}
In the topbar, click the **account select**.
{% endstep %}

{% step %}
Select **Logout**.
{% endstep %}

{% step %}
In the **Logout confirmation** modal, confirm the action.
{% endstep %}
{% endstepper %}

You'll be redirected to the login page with account selection.


---

# Agent Instructions: 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:

```
GET https://docs.defi.b2binpay.com/user-guide/account.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.