# Confidential Treasuries Source: https://docs.business.near.com/confidential-treasuries Manage assets and payroll without exposing your financial data NEAR Business treasuries are **confidential**, meaning all financial data is **visible only to team members**: all transactions and actions remain private. Confidential treasury interface *** ## How Do Confidential Treasuries Work? Confidential treasuries are multisig wallet smart contracts deployed on a **private shard** on NEAR Protocol. This allows them to combine the security of battle-tested multisig smart contracts on NEAR with the privacy of confidential transaction processing. Confidential treasury architecture While NEAR Protocol is a single blockchain, it is actually composed of small chain instances called shards. Each shard executes in parallel, handling transactions for a set of accounts and contracts. In NEAR, all shards are public by default, meaning that anyone can see all their transactions. However, NEAR allows having private shards, which use the same technology as the public ones, but with the main difference of **not exposing any data to the public**. This makes private shards an ideal solution for confidential treasuries, as they provide all the security and functionality of a public shard, but with the added privacy of not exposing any financial data to the public. Your treasury holds assets as token balances on `near.com` smart contract - deployed within the private shard. `near.com` infrastructure manages non-custodial pools in multiple public chains. When you deposit assets on them, the corresponding token balances are credited to your treasury on the private shard. Swaps are reflected as changes in the token balances within your treasury on the private shard. For example, if you swap ETH for BTC, the ETH balance decreases while the BTC balance increases accordingly. When you withdraw assets from your treasury, the corresponding token balances on the private shard are redeemed, and the pooled assets on the destination chain are used to fulfill the withdrawal. This lets your treasury manage assets from multiple chains without maintaining a separate wallet on each chain. Your team controls the treasury's assets; the pooled accounts provide the backing and infrastructure for deposits and withdrawals. *** ## Deposits Because confidential treasuries run on a private shard, funding them and paying from them requires moving funds between the private shard and public blockchains. There are two ways to do this, depending on how your team wants to operate.
### Automatic Bridging Your treasury can receive funds from public blockchains through a temporary account and automatically bridge them to the private shard. Furthermore, using a unique deposit address for each transfer makes it harder for external observers to link multiple deposits, wallets, or counterparties to the same treasury, which provides additional privacy. Deposit through a temporary address Temporary deposit addresses are single-use and remain valid for 14 days. If the address expires, create a new one before sending funds.
### Using near.com If your team already uses a confidential account on [near.com](https://near.com/), you can fund the treasury by transferring assets directly to the treasury account ID. Read the detailed guide on how to [**fund confidential treasuries through near.com**](/guides/funding-confidential-treasuries). *** ## Proposals In a confidential treasury, external actors can see that a *proposal exists* and how members voted, but **only team members can see the proposal details**. For example, if a team member creates a proposal to pay `10 USDC` to `alice.near`, the public can see that a proposal was created and whether it was approved or rejected, but **only team members can see** that it was a *payment* proposal, as well as **the amount, token, and recipient**. *** ## Payments Confidential treasuries can create payments in all supported assets, and the recipient can be **either** a **confidential [near.com](https://near.com/) account** or a **public wallet address**. Payments to [near.com](https://near.com/) confidential accounts will be executed within the private shard, so the recipient will need to log in to [near.com](https://near.com/) to access and withdraw the funds. When making payments to public wallets, NEAR Business **automatically bridges** the funds from the private shard to the recipient's address on the selected chain. In this case, the public recipient will see the funds arriving from the *NEAR Intents account on the destination chain*, as that is the account used to bridge funds from the private shard to the destination blockchain. *** ## Frequently Asked Questions No, all treasuries created through NEAR Business are confidential. While NEAR Protocol is a single blockchain, it is actually composed of multiple small chain instances called shards, which run in parallel. Each shard is in charge of certain accounts and smart contracts and operates in parallel, with all shards aggregating to form the NEAR blockchain. Almost all shards on NEAR are public, which means that anyone can see all the funds and transactions happening on them. However, NEAR also allows the creation of private shards, which run on the same technology as the public ones, but with the added security of being private and encrypted. This is how confidential treasuries work: they are deployed on their own private shard, which is not accessible to anyone outside the team, thus keeping all financial data private. To deposit funds into a confidential treasury, you can either use [**near.com**](https://near.com/) and [fund the treasury's account](/guides/funding-confidential-treasuries) through a confidential account there, or let NEAR Business generate a temporary deposit address and bridge the funds for you. Yes, all payments from a confidential treasury are private, as they are executed within the private shard. This means that the details of the payment, such as the amount, recipient, and token, are only visible to team members and not to the public. Recipients of confidential payments can either [receive the funds in a near.com confidential account](/guides/confidential-payments) or receive them directly in their public wallet. For recipients who receive payments directly in their public wallet, the sender will appear as the general NEAR Intents account. Yes, all swaps from a confidential treasury are private, as they are executed within the private shard. This means that the details of the swap, such as the amount, tokens involved, and exchange rate, are only visible to team members and not to the public. *** ## Ready to Get Started? [Create your treasury now](https://business.near.com/) and start managing your team's crypto assets securely and collaboratively! # Handling Governance Requests Source: https://docs.business.near.com/governance/handling-requests Manage governance requests in your treasury Once a request is created—either to change a [team member's role](/governance/members-and-roles) or to [change a voting threshold](/governance/voting-settings)—it is listed as a **`Pending`** request in the **`Requests`** section of the left sidebar. Pending governance requests Navigate to the **`Requests`** section in the left sidebar to see all pending governance requests. You can filter and sort requests to find the one you want to review and vote on. *** ## Voting on a Request Click on a request to review its details, including the type of request, the proposed changes, and any comments added by the requester. After reviewing the request, you can cast your vote to either approve or reject it. Governance request details Only team members with the **[Governance](/governance/members-and-roles#governance) role** can review request details and cast a vote to either **approve** or **reject**. *** ## Filtering Governance Requests You can filter governance requests by the following fields: **`Request Type`**, **`Created Date`**, **`Recipient`**, **`Token`**, **`Requester`**, **`Approver`**, and **`My Vote Status`**. To filter governance requests, click the **`Filter`** icon: Governance request filters Then add as many filters as needed: Filtered governance requests To see only governance requests, filter by **`Request Type`** → **`Change Policy`**. # Members and Roles Source: https://docs.business.near.com/governance/members-and-roles Discover how to manage your treasury's team members and their roles Each treasury in NEAR Business is a shared multisig account whose members collectively control its assets and actions. No single member has unilateral control, and the team must reach consensus before performing any action. Treasury members screen You can manage team members and their roles in the **`Members`** section of the left sidebar. *** ## Members A treasury member represents a wallet address that can participate in the treasury. Each member: * Connects using their own wallet (e.g. a browser wallet, mobile wallet, or hardware wallet) * Signs proposals and votes using that wallet * Acts independently from other members This is the core multisig concept: multiple wallets collectively control one treasury. No single member has unilateral control over the treasury's funds, and to perform any action the team needs to reach consensus. Do not use `near.com` internal wallet addresses (e.g. `nearcom:...`) as treasury members *** ## Roles and Permissions Roles define what actions a member’s wallet is allowed to perform within the treasury. There are three roles in a treasury: [**Requestor**](#requestor), [**Finance**](#finance), and [**Governance**](#governance). Each role has specific permissions that determine what actions members can perform within the treasury. Members can have multiple roles and receive the combined permissions granted by each assigned role. *** ### Requestor Allows members to create requests related to the treasury's funds (e.g., treasury transaction requests). #### Can * **✅ Create payment requests** * **✅ Create staking, unstaking, and withdrawal requests** * **✅ Create asset exchange requests** * **✅ Delete their own pending requests** #### Cannot * **❌ Vote on any request** *** ### Finance Responsible for voting on treasury transaction requests—those created by [Requestors](#requestor). #### Can * **✅ Vote to approve or reject requests created by Requestors** #### Cannot * **❌ Create, edit, or delete requests** * **❌ Manage members or treasury settings** *** ### Governance Responsible for configuring the treasury's settings and membership. Exercise caution when assigning the Governance role, as it has extensive control over the treasury's settings. [Read more](#governance-is-the-highest-trust-role) #### Can * **✅ Create requests to add, edit, or delete members** * **✅ Create requests to update the voting duration** * **✅ Create requests to update the treasury's theme and logo** * **✅ Create requests to update the treasury's voting threshold** * **✅ Vote on any treasury configuration requests** * **✅ Delete their own requests** #### Cannot * **❌ Create financial requests (e.g., payments or staking)** * **❌ Vote on financial requests created by Requestors** *** ## Governance Is the Highest-Trust Role The Governance role controls who has power in the system. Because Governance controls membership and voting rules, it should be treated as the highest-trust role in the treasury. Governance is intentionally powerful and not meant for day-to-day use. Best practice is to: * Assign Governance to highly secure wallets * Use high voting thresholds * Share Governance across multiple trusted members when possible Treasury safety comes from isolating and sharing authority, not from weakening permissions. *** ## Permission Matrix The following table shows the actions each role can perform: | Action | Requestor | Finance | Governance | | - | - | - | - | | Create Payment Requests | ✅ | ❌ | ❌ | | Create Stake Delegation Requests (Stake/Unstake/Withdraw) | ✅ | ❌ | ❌ | | Create Asset Exchange Requests | ✅ | ❌ | ❌ | | Vote on Treasury Transaction Requests | ❌ | ✅ | ❌ | | Create Add/Edit/Delete Member Requests | ❌ | ❌ | ✅ | | Create Voting Duration Update Requests | ❌ | ❌ | ✅ | | Create Theme/Logo Update Requests | ❌ | ❌ | ✅ | | Create Voting Thresholds Requests | ❌ | ❌ | ✅ | | Vote on Configuration Requests | ❌ | ❌ | ✅ | | Delete Own Pending Requests | ✅ | ❌ | ✅ | | Delete Others' Pending Requests | ❌ | ❌ | ❌ | *** ## Best Practices When assigning roles and permissions within your treasury, consider the following best practices: * **Use least privilege**: Grant only the roles needed for each member’s responsibilities * **Separate duties**: Maintain a clear separation between financial operations and treasury configuration, do not assign the Governance role to Requestors or Finance members * **Use voting thresholds intentionally**: Higher-risk actions (like configuration changes) should require more approvals * **Do regular reviews**: Periodically review assigned roles and permissions to ensure they align with your treasury's current needs * **Governance caution**: Exercise caution when assigning the Governance role, as this role has extensive control over the treasury's settings # Voting Rules Source: https://docs.business.near.com/governance/voting-settings Keep your treasury secure through voting rules When creating a treasury, you can set the **`Voting Threshold`** for all requests. This threshold represents the minimum number of approvals required for a proposal to be approved. Voting threshold setup Voting thresholds prevent any single member from acting alone. Proceed with caution when setting up voting thresholds. *** ## Updating Voting Rules Once the treasury is created, team members with the [Governance](/governance/members-and-roles#governance) role can present proposals to change the treasury's configuration, including its voting thresholds and voting period. Only members with the [Governance](/governance/members-and-roles#governance) role can create proposals to update the treasury's voting settings. Governance proposals can change how decisions are made, significantly affecting the treasury's security and operations. Do not lower the governance threshold unless necessary. [Read more](/governance/members-and-roles#governance-is-the-highest-trust-role) *** ## Voting Settings There are two main configurations that can be updated through proposals: [Voting Thresholds](#voting-thresholds) and the [Voting Duration](#voting-duration). ### Voting Thresholds A voting threshold is the **minimum number of votes required for a proposal to be approved**. For example, if the treasury has a voting threshold of 2, it means that at least **2 votes in favor are needed for the proposal to pass**. Treasuries separately configure voting thresholds for Governance and Finance proposals, which means that the required number of votes for a proposal to be approved can differ based on the type of proposal being voted on. ### Governance Threshold How many [Governance](/governance/members-and-roles#governance) approvals are required for: * Editing team members * Updating voting settings ### Finance Threshold How many [Finance](/governance/members-and-roles#finance) approvals are required for: * Making payments * Swapping assets * Handling staked assets *** ### Voting Duration The voting duration is the **time period during which team members can cast their votes on a proposal**. For example, if the voting duration is set to 3 days, it means that team members will have 3 days to vote on a proposal after it has been created. If the required number of votes is reached within the voting duration, the proposal is approved and executed immediately. However, if not enough members vote in favor of the proposal within the voting duration, the proposal then expires and is automatically rejected by the system. In contrast to voting thresholds, which can be configured separately for Governance and Finance proposals, the voting duration is a single setting that applies to all proposals in the treasury, regardless of their type. *** ## What's Next? After a governance request is submitted, it is ready for team members with the [Governance](/governance/members-and-roles#governance) role to review and [vote on the request](/governance/handling-requests). Head to [Handling Governance Requests](/governance/handling-requests) to learn how to review and vote on governance requests. # Receiving a Payment on near.com Source: https://docs.business.near.com/guides/confidential-payments Withdraw payments received from a confidential treasury [Treasuries](/confidential-treasuries) can [send payments](/payments/single-payment) in all [supported assets and chains](/what-is#chains--assets). This guide explains how to access and withdraw a confidential payment received through a [near.com](https://near.com/) account and transfer it to an external wallet. *** ## Accessing and Withdrawing a Confidential Payment Navigate to [near.com](https://near.com/) and log in with the **wallet where you received the payment**. near.com supports a wide range of wallets from multiple ecosystems. near.com Send screen Click **`Send`** and select the token, destination network, and recipient address, then confirm the transfer. Selecting a token and network for withdrawal You can swap the funds to any other asset supported by [near.com](https://near.com/) before withdrawing them. The same asset can also be sent across multiple networks, so you can choose the option that best fits your needs. Once the transfer completes, you will see the funds available in your selected external wallet. Completed withdrawal in near.com # Funding Through near.com Source: https://docs.business.near.com/guides/funding-confidential-treasuries Learn how to fund a confidential treasury using near.com [Confidential treasuries](/confidential-treasuries) run on a private shard on NEAR, so assets need to be bridged from public blockchains to the private shard through [near.com](https://near.com/). For teams that want to manage the bridging process themselves, this guide explains how to fund a confidential treasury through [near.com](https://near.com/). If you do not want to interact with [near.com](https://near.com/) or manage private accounts, you can use the automatic bridging flow in NEAR Business. Use the **`Receive`** button in your confidential treasury's dashboard to generate a temporary deposit address, then send the funds from any external wallet to that address. Temporary deposit addresses are single-use and remain valid for 14 days. Create a new one if the address expires before you send the funds. *** ## Get Your Address Click **`Receive`** in your confidential treasury's [dashboard](https://business.near.com/), then select **`From confidential user`**. NEAR Business Receive screen You will see a deposit address for your confidential treasury. Copy this address, as you will need it to send funds from your [near.com](https://near.com/) account. NEAR Business confidential treasury address *** ## Deposit Funds in near.com Navigate to [near.com](https://near.com/) and connect with any of the supported wallets. Once connected, you will see the main dashboard where you can deposit and manage your assets. Use the **`Receive`** option to deposit funds into your account. You can deposit from any external wallet. Receive funds screen [near.com](https://near.com/) allows you to log in with multiple wallets across different chains and supports multiple popular assets. *** ## Transferring to the Treasury Once the deposit is complete, return to the home screen and send the funds to the treasury. Click **`Send`** and select **`another near.com account`** as the network destination. Sending funds to another near.com account Select the token you want to send and enter the treasury's account ID as the destination. Once it completes, you will see the funds in your confidential treasury's [dashboard](https://business.near.com), ready to use for payments and swaps. Because [confidential treasuries](/confidential-treasuries) are deployed on [near.com](https://near.com/)'s private shard, they are effectively near.com accounts. Select **`another near.com account`** on the **`Send`** screen. Funds sent to other networks might be lost, and there is no way to recover them. # Using a Ledger Source: https://docs.business.near.com/guides/ledger Learn how to set up and use a Ledger hardware wallet with NEAR Business Hardware wallets are one of the most secure ways to manage your account. While a hardware wallet is not required to use NEAR Business, it is highly recommended for your most critical operational roles, such as [Finance](/governance/members-and-roles#finance) and [Governance](/governance/members-and-roles#governance). Learn more about keeping your treasury safe with a Ledger device in the [**Ledger security blog post**](https://trezu.org/blog/how-to-use-ledger-hardware-wallet). *** ## Setting Up Ledger with NEAR 1. Download and install [Ledger Live](https://www.ledger.com/ledger-live). 2. Connect your Ledger via USB or Bluetooth. 3. Open the **Ledger Live** application and ensure your device firmware is up to date. 4. In **Ledger Live**, install the **NEAR app** from the **`App Catalog`**. 5. Open the NEAR app on your Ledger device. The screen should display **`Application is ready`**. NEAR app installed in Ledger Live

*NEAR app (v2.4.3) installed in Ledger Live*

Your Ledger is now set up, so you can use it when joining or creating a treasury. *** ## 1. Sign In to NEAR Business Open [NEAR Business](https://business.near.com) and click **`Login`**. 1. Select the **`Ledger`** option. 2. Choose a **`USB`** or **`Bluetooth`** connection, depending on your device. 3. When your device prompts you to **confirm the connection**, approve it on the device. *** ## 2. Select a Derivation Path At this point, you will be prompted to select a **`Derivation Path`**, which determines which private key the Ledger uses when signing transactions through NEAR Business. Derivation path selection If you are unsure which option to select, choose the first one (**`Account 1`**). Approve the selection on your Ledger device before proceeding to the next step. *** ## 3. Select an Account Now that you have selected which private key to use, manually enter the account ID you want to use to log in: Account ID selection You can either use the implicit account derived directly from the selected derivation path or enter another account ID. If you are unsure which account ID to use, choose the implicit account. After confirming, you will see one of the following outcomes: 1. **Logged in successfully**—the account exists and matches the selected Ledger private key. 2. **Create account option**—the account does not exist yet, so you can create it immediately. 3. **Error message**—the account exists, but it is linked to a different Ledger private key. To avoid key mismatch errors, use the same derivation path that was originally used with that account ID. **Advanced** In NEAR, you can add your Ledger public key to an existing account. However, you will need to use an external tool, such as the [NEAR CLI](https://docs.near.org/tools/near-cli). *** ## 4. You're In You are now signed in to NEAR Business using your Ledger hardware wallet. You do not need funds in the account yet—treasury creation and proposal interactions are sponsored. You can now use NEAR Business as usual, with the added security that every action requires physical confirmation on your Ledger device. You can now [create a new treasury](https://business.near.com/app/new) or ask your team to add you as a member to an existing one. # Login Methods Source: https://docs.business.near.com/login Find all the ways in which you can access the Treasuries Near Business offers multiple ways to log in and access your treasuries, depending on your needs and preferences. Login modal with passkey and crypto wallet options Those familiar with crypto wallets can readily connect their accounts using any NEAR wallet, or login with a Ledger device. For those needing another safe and easy way to access, the platform offers passkeys, which allow you to securely access Near Business using your device’s biometric authentication. Near Business is a non-custodial solution, which means that your funds are always under your control. Both passkeys and crypto wallets gives you access to all features, so you can safely choose whichever fits your needs best. *** ## Comparison of Login Methods | | 🫆 Passkeys | 🌐 Crypto Wallets | | - | - | - | | Easy to secure | ✅ Yes, kept safe by your device | ⚠️ Need to secure a recovery phrase offline | | Grants access to all features | ✅ Yes | ✅ Yes | | Can use and create **confidential treasuries** | ✅ Yes | ✅ Yes | | Can be used to log in to other blockchain apps | 🔒 No, your passkey is for Near Business only | ✅ Yes, can be used in other crypto apps | | Can be used on other devices | ⚠️ [Depends on where it is saved](#passkey-storage-and-recovery) | ✅ Yes, using the recovery phrase | | Can I regain access if I lose my device? | ⚠️ [Only if the passkey is still available](#passkey-storage-and-recovery) | ✅ Yes, using the recovery phrase | *** ## Passkeys Passkeys are a secure authentication method that allows you to access Near Business using your own device's authentication method, such as fingerprint or facial recognition. To start using passkeys, select `Sign Up` in the login modal. You will then be prompted to create a passkey on your device, and a new on-chain account will be automatically created for you. Passkey sign-up option in the login modal Once created, you can use the `Sign In` option to login using your passkey. There is no need to fund your account, as Near Business covers the cost of creating and using a treasury. ### Passkey Storage and Recovery Depending on the service or device you use to store your passkeys, the recovery options and device specificity may vary: | Service | Stored in | Device specific? | Can it be recovered? | | - | - | - | - | | [Apple Passwords](https://support.apple.com/en-eg/guide/iphone/iph82d6721b2/ios) | iCloud Keychain. | No; it syncs to your approved Apple devices. | Yes. Set up iCloud Keychain on another device. If all your devices are lost, follow [Apple's recovery steps](https://support.apple.com/en-eg/guide/iphone/iph82d6721b2/ios). | | [Google Password Manager](https://support.google.com/chrome/answer/13168025) | Google Password Manager. | No; it syncs to your other devices using Google Password Manager. | Yes. Use your Google Password Manager PIN to access synced passkeys on a new device. [Google's instructions](https://support.google.com/chrome/answer/13168025). | | [Chrome profile](https://support.google.com/chrome/answer/13168025) | The Chrome profile on that computer. | Yes; the passkey stays on that computer. | No, if the computer or Chrome profile is lost. [Google says these passkeys cannot be recovered](https://support.google.com/chrome/answer/13168025). | | [Microsoft Password Manager](https://support.microsoft.com/en-us/accounts-billing/security/manage-your-saved-passkeys) | Microsoft Password Manager. | No; it syncs to devices where you use the same account. | Yes. Sign in to Edge with the same account on another device. Work or school accounts may have restrictions. [Microsoft's instructions](https://support.microsoft.com/en-us/accounts-billing/security/manage-your-saved-passkeys). | | [Windows Hello](https://support.microsoft.com/en-us/accounts-billing/security/create-save-passkey) | That Windows device. | Yes; the passkey is saved locally. | No, if the device is lost, unless you also saved another copy. [Microsoft explains device-bound passkey recovery](https://support.microsoft.com/en-us/accounts-billing/security/what-are-passkeys-why-they-matter). | | [1Password](https://support.1password.com/lost-device/) | Your 1Password account. | No; passkeys sync with your account. | Yes, if you can sign in to 1Password on another device. [1Password's lost-device guidance](https://support.1password.com/lost-device/). | Near Business does not store your passkeys or offer a way to recover them. Keep your passkey manager and its recovery methods secure. *** ## Crypto Wallets To connect with your wallet, simply select the `NEAR Wallet` option from the login modal. Crypto wallet selection options in the login modal There is no need to fund your NEAR account, as Near Business covers the cost of creating and using a treasury. *** ## Hardware Wallets Near Business supports Ledger, a popular hardware wallet that allows you to securely store your crypto assets offline. You can connect using your Ledger device and use it to manage your treasuries. Learn more about how to use Ledger in our [Ledger Guide](/guides/ledger) *** ## Frequently Asked Questions Use passkeys if you are new to crypto wallets, or if you want to create a separate account that is secure and easy to use. Otherwise, you can use your wallet if you already have one. Yes, all login methods have access to the same features and functionality. The only difference is the way in which you authenticate and access your treasuries. How private each method is depends on your usage. Using a passkey provides the same level of privacy as using a completely new on-chain account, and since NEAR Business covers the cost of creating and using a treasury, you do not even need to fund it. Using an existing crypto wallet is generally less private, as it might have a history of transactions that can be linked to your identity. Depends on where your passkey was stored (see [table above](#passkey-storage-and-recovery)). In devices with syncing passkey managers - such as Apple Passwords or Google Password Manager - you should be able to recover it by logging into a new device. If it was stored only on the lost device and you did not have any recovery options, you may lose access to your Near Business account. Near Business cannot recover the passkey for you. Both your funds and your treasuries' funds are always under your control. Near Business is a non-custodial solution, which means that we do not hold your keys or funds, and never have access to them. *** ## Ready to get started? [Create your treasury now](https://business.near.com/) and start managing your team's crypto assets securely and collaboratively! # Proposing Multiple Payments Source: https://docs.business.near.com/payments/bulk-payment Request payments for multiple recipients at once You can create bulk payment requests to pay multiple recipients at once instead of creating separate [single-payment requests](/payments/single-payment). This is especially useful when you need to pay a large number of recipients with the same token, as it allows you to request all payments in a single request, saving you from having to create them separately. Payment requests can only be created by team members with the [Requestor](/governance/members-and-roles#requestor) role, and they require approval from team members with the [Finance](/governance/members-and-roles#finance) role before they can be executed. *** ## Bulk Payment Request Navigate to the **`Payments`** section in the left sidebar, then click **`Bulk Payments`**. Bulk payment button Specify which token you want to use—all recipients will be paid in the same token. Then, manually enter the payment details for each recipient or upload a `.csv` file containing the information. Bulk payment request form
The expected format is a list of recipients with their wallet addresses and payment amounts. For example, to pay `10.50 USDC` to `alice.near` and `21.34 USDC` to `bob.near`, enter the following data in the **`Provide Data`** section: ``` alice.near, 10.50 bob.near, 21.34 ``` Alternatively, download the template, fill in the payment details, and upload the file in the **`Upload File`** section. *** ## Reviewing the Request Review the bulk payment request before submitting it. You can add a comment to provide more context to the approvers. Bulk payment review After the bulk payment is approved and executed, you can generate a [receipt](/payments/handling-requests). Verify the blockchain and wallet addresses before submitting the request, as payments are irreversible. *** ## What's Next? After submitting the payment request, it will be ready for team members with the [Finance](/governance/members-and-roles#finance) role to review and vote on. Head to [Handling Payment Requests](/payments/handling-requests) to learn how to review and vote on payment requests. # Handling Payment Requests Source: https://docs.business.near.com/payments/handling-requests Manage payment requests in your treasury Once a payment request is created—either for a [single payment](/payments/single-payment) or to pay [multiple recipients at once](/payments/bulk-payment)—it is listed as a **`Pending`** request in the **`Requests`** section. Pending payment requests Navigate to the **`Requests`** section in the left sidebar to see all pending payment requests. You can filter and sort requests to find the one you want to review and vote on. Only team members with the **[Finance](/governance/members-and-roles#finance) role** can review request details and cast a vote to either **approve** or **reject**. *** ## Voting on a Request Click on a request to review its details, including the recipient, the amount, the token, and any comments added by the requester. After reviewing the request, you can cast your vote to either approve or reject it. Payment request details Only team members with the **[Finance](/governance/members-and-roles#finance) role** can review request details and cast a vote to either **approve** or **reject**. If the treasury does not have enough funds to cover the payment request, you will need to top up the treasury with the required tokens before the request can be approved. *** ## Receipts Once a payment request is approved and executed, you can generate a PDF receipt to share with the recipient as proof of payment. Select the payment for which you want to generate a receipt, then click **`Generate PDF Receipt`**. Generate PDF receipt option *** ## Filtering Payment Requests You can filter payment requests by the following fields: **`Request Type`**, **`Created Date`**, **`Recipient`**, **`Token`**, **`Requester`**, **`Approver`**, and **`My Vote Status`**. To filter payment requests, click the **`Filter`** icon: Payment request filters Then add as many filters as needed: Filtered payment requests To see only payment requests, filter by **`Request Type`** → **`Payments`**. # Proposing a Payment Source: https://docs.business.near.com/payments/single-payment Request a payment to an external account The treasury funds can be used to send payments to an external account. You can request payments to any wallet address on any blockchain, even if the treasury does not have the required tokens to cover the payment—your team can top up the treasury with the required tokens later. Need to request multiple payments at once? Check the [Proposing Multiple Payments](/payments/bulk-payment) section. Payment requests can only be created by team members with the [Requestor](/governance/members-and-roles#requestor) role, and they require approval from team members with the [Finance](/governance/members-and-roles#finance) role before they can be executed. *** ## 🔒 Private Payments Treasuries can create payments to [near.com](https://near.com/) accounts, or directly to public wallet addresses. Both types of payments are executed within the private shard, so they are inherently private. Payments sent to [near.com](https://near.com/) accounts require the recipient to [log in to near.com](/guides/confidential-payments) to access and withdraw the funds. In this case, the sender appears as the confidential treasury's account on [near.com](https://near.com/). Payments sent directly to public wallet addresses redeem the corresponding tokens held by your treasury on the private shard and release the funds to the recipient on the selected chain. The recipient sees the funds come from the `near.com` account on that chain. Learn more about [how assets are held and transferred](/confidential-treasuries#how-do-confidential-treasuries-work). *** ## Requesting a Payment Navigate to the **`Payments`** section in the left sidebar, then enter the required details: the recipient's **wallet address**, the **token** and **amount** you want to send, and the recipient's **network**. Payment request form You can create a payment request even if the treasury does not have the necessary tokens. This allows you to request payments, and the team can top up the treasury with the required tokens later. Use the [Address Book](#address-book) to save frequently used wallet addresses and easily select them when creating payment requests. *** ## Reviewing the Payment Request After entering the payment details, review the request before submitting it. You can add a comment to provide more context to the approvers. Payment request review After the payment is approved and executed, you can generate a [receipt](/payments/handling-requests). Verify the blockchain and wallet address before submitting the request, as payments are irreversible. *** ## Address Book The address book lets you save frequently used wallet addresses, making it easier to select the correct recipient when creating payment requests. Address Book Addresses can be linked to multiple blockchains, so you can save a recipient's wallet address once and use it for payments across different networks. Navigate to the **`Address Book`** section in the left sidebar, then click **`Add Recipient`** to save a new wallet address. *** ## Frequently Asked Questions The following questions cover common issues when creating payment requests. No, once a payment request is submitted, it cannot be edited. If you need to make changes to a payment request, you will need to delete the existing request and create a new one with the correct details. If the payment request is approved and executed with an incorrect wallet address, the funds will be sent to the wrong address and may be unrecoverable. Always double-check the wallet address before submitting the payment request to avoid any mistakes. *** ## What's Next? After submitting the payment request, it will be ready for the [Finance](/governance/members-and-roles#finance) team members to review and [vote on the request](/payments/handling-requests). Head to [Handling Payment Requests](/payments/handling-requests) to learn how to review and vote on payment requests. # Swapping Assets Source: https://docs.business.near.com/swap Swap assets across blockchains without leaving NEAR Business If your team needs to [make a payment](/payments/single-payment) in a token that the treasury does not currently hold, or if you want to rebalance the treasury's portfolio, you can create a swap request to exchange one token for another. Asset swap overview You can swap assets directly in NEAR Business, making it easy to manage your treasury's portfolio and access liquidity when needed. *** ## Creating a Swap Request To swap assets, navigate to the **`Exchange`** section in the left sidebar. Select the assets you want to swap from and to, enter the amount, and review the details before confirming the request. Swap request review Only team members with the [Requestor](/governance/members-and-roles#requestor) role can create swap requests. ### Swap Fee NEAR Business charges a 0.35% fee on the amount being swapped. This fee is included in your quote and covers the costs of the underlying swap protocol—NEAR Intents—and the NEAR Business fee. Swaps in NEAR Business are built on NEAR Intents, a platform for multi-chain asset swaps that provides competitive rates and low fees across different blockchains. *** ## Voting on Swap Requests Members with the [Finance](/governance/members-and-roles#finance) role can vote on swap requests while they are open - determined by the treasury's [voting configuration](/governance/voting-settings). If the request does not receive enough votes — as defined by the voting threshold - it will be automatically rejected. # What is a Treasury? Source: https://docs.business.near.com/what-is Treasuries can help teams to manage all their assets securely and privately A treasury lets teams manage crypto assets across multiple chains while keeping their financial data private. Only treasury members can view this information. Under the hood, each treasury is a multisig wallet in which members have specific roles. Every action starts as a proposal. In the NEAR Business interface, proposals are shown as requests. Eligible members review and vote on them before execution. NEAR Business is non-custodial and does not have access to your private keys or funds. Your team retains full control over your assets. *** ## Confidential Treasuries In NEAR Business, all **treasuries are confidential**. Unlike classic public treasuries, their financial data is **visible only to team members**. | Feature | Public Treasuries | NEAR Business | | - | - | - | | Team members | 🌐 Visible to anyone | 🌐 Visible to anyone | | View the treasury funds | 🌐 Visible to anyone | 🔒 Only the team | | View payment requests (current and historical) | 🌐 Visible to anyone | 🔒 Only the team | | View swap requests (current and historical) | 🌐 Visible to anyone | 🔒 Only the team | | How transactions are handled | 🌐 Through public chains | 🔒 Through a private shard | Learn more in the [Confidential Treasuries section](/confidential-treasuries). *** ## Chains and Assets Treasuries can hold crypto assets on multiple chains, allowing teams to manage their funds from a **single platform** without using multiple wallets. New chains and assets are added regularly. If you do not see a specific chain or asset, contact the NEAR Business team to request support for it. *** ## Team Members and Roles A treasury is composed of multiple members, and each member can be assigned multiple [roles and permissions](/governance/members-and-roles). There are three main roles in a treasury: Manages team members and configuration, without handling day-to-day fund requests Creates fund-related requests, such as payments and swaps, with no voting power Reviews and votes on fund-related requests, but cannot manage governance settings Team members can be assigned multiple roles, for example a member can be both Governance and Finance, which means they can manage team members and also vote on proposals. *** ## Governance and Proposals In a treasury, nobody can make unilateral decisions regarding the management of funds or team members. Instead, each treasury defines a minimum number of members who need to agree before performing an action—this is called the voting threshold. All actions—whether making a payment, swapping tokens, or managing team members—must be **proposed first**, and relevant team members can vote on them. If a proposal reaches the required voting threshold, the system executes it automatically. This way, treasuries ensure that all decisions are made collectively, thus minimizing risks and maximizing security. *** ## Security Model NEAR Business secures treasuries through three mechanisms: 1. **Multiple members** – actions require approvals from more than one wallet 2. **Roles** – limit what actions each wallet can perform 3. **Voting thresholds** – define how many approvals are required for an action to be executed *** ## Frequently Asked Questions A treasury is a wallet on its own, so you would need to deposit funds into the treasury to be able to use them. Once the funds are in the treasury, they can be managed by the team according to the defined roles and voting rules. The funds are controlled by the treasury, which is a multisig wallet smart contract on NEAR. The treasury is controlled by your team members through governance. The NEAR Business team does not custody your keys or funds, nor does it have access to them. Your treasury holds and controls its assets as token balances on NEAR's private shard, so it does not need a separate wallet on every chain. The tokens backing those balances on each chain are held in non-custodial pools managed by the near.com infrastructure. Learn more about [where assets are held and how deposits and withdrawals work](/confidential-treasuries#how-do-confidential-treasuries-work). Your funds remain on-chain and under the treasury control. Team members can use alternative interfaces or command-line tooling to keep managing the treasury. *** ## Ready to Get Started? [Create your treasury now](https://business.near.com/) and start managing your team's crypto assets securely and collaboratively!