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

# Settings

## <mark style="color:blue;">General Settings</mark>

<figure><img src="/files/NGnA3nbbryuHwJT2YQ2W" alt=""><figcaption></figcaption></figure>

In the "General" section, you'll find several customization options to enhance your user experience:

* **Language Selection**: Choose your preferred language, allowing you to interact with the platform in the language that works best for you. Currently supported languages include English, Traditional Chinese (繁體中文), Simplified Chinese (简体中文), Bengali (বাংলা) and Spanish (Español).
* **Background Theme**: Modify the visual appearance to suit your preferences with options for light or dark mode. This helps reduce eye strain based on your lighting environment and personal preference.
* **Balance Display Options**: Hide small transactions — specifically, any transaction history below 1 USD — to keep your dashboard clutter-free by only displaying significant transactions.

These personalisation features allow you to create an interface that maximizes ease of use and clarity for your specific needs.

## <mark style="color:blue;">KeyPair Management</mark>

The **KeyPair Management** section provides a centralized interface for managing all access KeyPairs associated with your AkashicPay account. Each KeyPair serves a specific purpose and comes with its own set of permissions and functions, allowing for fine-grained access control across different roles or systems. Integrating these KeyPairs follows a consistent process, ensuring a straightforward setup experience. You can generate as many KeyPairs as needed to accommodate your operational requirements.

For more detailed definitions and explanations, please refer to the [**KeyPairs Guide**](/guides/keypairs-guide.md).

### <mark style="color:blue;">Generate API/SDK KeyPair</mark>

<figure><img src="/files/3WzX33nL1sDG6WCkfKss" alt=""><figcaption></figcaption></figure>

The API/SDK KeyPair is a critical security credential required for integrating with the AkashicPay SDK or SecureAPI:

* When you first onboarded to AkashicPay, you should have already generated your first API/SDK KeyPair.
* This KeyPair is used to authenticate your integration with the AkashicPay SDK or SecureAPI.
* This KeyPair has all the permissions that the Owner KeyPair has, except being able to refresh itself and the Treasury KeyPair. It has access to managing the Customer Service KeyPairs.
* To create, remove or refresh an API/SDK KeyPair:
  1. Navigate to the KeyPair Management page.
  2. Click the "Generate KeyPair" button to create a new API/SDK KeyPair.
     1. Enter an Access Name to make identification easier.
  3. Or hover over the "⋮" icon and click either "Regenerate KeyPair" or "Remove KeyPair".
  4. Confirm the action when prompted.

> **Important**: There can infinite amount of active API/SDK KeyPairs at all times. Please make sure to keep all KeyPairs secure and update the KeyPair credentials within your AkashicPay SDK or SecureAPI implementation.

### <mark style="color:blue;">Generate Treasury KeyPair</mark>

<figure><img src="/files/E4v5r0nXilHQMStEjId4" alt=""><figcaption></figcaption></figure>

The Treasury KeyPair is a vital security credential that provides an additional layer of protection for withdrawing funds from your AkashicPay account.

* Generating your Treasury KeyPair activates the Multisig feature.
* The Treasury KeyPair serves as a secondary signature for withdrawals initiated by your API/SDK KeyPair.

  * Users can set a token value threshold for transactions that do not require approval or denial from the Treasury KeyPair when enabling the Multisig feature.&#x20;

  > **NB!** A value of 0 indicates that the transaction will always require Multisig authorisation using the Treasury KeyPair.

> **Important**: There can infinite amount of active Treasury KeyPairs at all times. Please make sure to keep all KeyPairs secure and update KeyPair credentials within your AkashicLink to continue to verify transactions in your AkashicPay.

#### <mark style="color:blue;">How to use your Treasury KeyPair</mark>

1. **Share the Treasury KeyPair**: Provide the Treasury KeyPair to your treasury department. Instruct them to download the AkashicLink application, which is required for secure access to the approval process.
2. **Log in with Treasury KeyPair**: Have the treasury department use the Treasury KeyPair to log in to AkashicLink. This ensures secure authentication for managing approvals.
3. **Access the Payout Approval Page**: Once logged in, navigate to the "Transfer" section, and select the [Payout Approval](/dashboard/transfer.md#payout-approval) page. From there, begin reviewing and approving or denying transactions as needed.

In this page, you can enable the Multisig feature by generating your Treasury KeyPair, which provides an additional layer of security for withdrawals initiated through your API/SDK KeyPair transactions. This feature acts as a secondary safeguard, ensuring that an extra verification step — using the Treasury KeyPair — is required to approve or deny withdrawals, enhancing the protection of your funds in your AkashicPay account.

### <mark style="color:blue;">Auto Multisig Threshold</mark>

<figure><img src="/files/yqVIqExP4E7LPsaF2fjk" alt=""><figcaption></figcaption></figure>

1. **Enable Multisig**: Navigate to the Treasury KeyPair section in the KeyPair Management page in your AkashicPay account and locate the Multisig feature. Generate your Treasury KeyPair to enable the feature.
2. **Set the Auto Multisig Threshold**: Enter a value for each of the tokens for the Auto Multisig Threshold. Transactions below this amount will be automatically processed using your API/SDK KeyPair without further authorisation. Withdrawals equal to or above this threshold will require approval using your Treasury KeyPair, adding an extra security step for larger transactions.
3. **Save Your Settings**: After configuring the threshold, save your changes. A signature request will appear, prompting you to sign using your Owner KeyPair. Complete the signature and confirm to save your settings.

> Note: If you decide to disable the Multisig feature, it will not remove your current Treasury KeyPairs and you will not need to generate a new one if you ever decide to use the Multisig feature again.

#### <mark style="color:blue;">Disabling and Enabling the Multisig Feature</mark>

<figure><img src="/files/kAOUISh2XO7tP8o1aE30" alt=""><figcaption></figcaption></figure>

You can disable the Multisig feature at any time, even if Treasury KeyPairs have already been generated. To disable it, simply click the red **“Disable Multisig”** button.

If you wish to enable Multisig again, you can do so by turning on the toggle for each token or selecting the specific tokens you want Multisig protection to apply to.

### <mark style="color:blue;">Customer Service KeyPair</mark>

<figure><img src="/files/95PMVogBozynaoQRofvd" alt=""><figcaption></figcaption></figure>

The Customer Service KeyPairs are an essential component of your operations. They enable your customer service staff to view transaction data without providing access to the funds in your Akashic account. The Customer Service KeyPairs are divided into two types: **CS Manager** and **CS General**. Both offer similar functionalities, with minor differences in access levels.

* **CS Manager:** Can review transaction data, add a missing reference ID to a transaction, and [retry sending callbacks](#allow-callback-retry).
* **CS General:** Can review transaction data only.

#### <mark style="color:blue;">How to use your Customer Service KeyPairs</mark>

1. **Share the Customer Service KeyPairs**: Provide the Customer Service KeyPairs to your customer service department. Instruct them to download the AkashicLink application, which is required for secure access to the approval process.
2. **Log in with Customer Service KeyPair**: Have the customer service department use the Customer Service KeyPair to log in to AkashicLink.&#x20;
3. **Retry callbacks**: To retry callbacks, log in and navigate to the "**History Record"** page. Locate the transaction missing callback data, then add the reference ID and initiate a retry for the callback.

### <mark style="color:blue;">Allow Callback Retry</mark>

If callbacks are not received, you can either allow your "**CS Manager**" logins to retry them, or add a `referenceId` in the Account’s [History Record](/dashboard/account.md#history-record).

<figure><img src="/files/VXJLA47o0ZE7MR6Yah7S" alt=""><figcaption></figcaption></figure>

## <mark style="color:blue;">Best Practices</mark>

For optimal use of the Settings features, we recommend:

* **Document KeyPair Changes**: When creating or refreshing your KeyPairs, ensure all team members are aware of the change to prevent integration issues.
* **Test After Changes**: After modifying any settings, verify that your integrations continue to function correctly.


---

# 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.akashicpay.com/dashboard/settings.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.