> For the complete documentation index, see [llms.txt](https://apidocs.onekeypayments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.onekeypayments.com/api-documentation/deposits-api/endpoints/transactional-account-endpoint/understanding-the-solution.md).

# Understanding the Solution

This solution allows having a transactional account, and an proprietary account, managing different balances, and also a bank account check solution.

## Proprietary Account and Transactional Account

With the transaction account Solution, you're going to have 2 accounts tied to your merchant account.\ <br>

<figure><img src="https://1595349702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7aIgg5dys0yN8otrASQq%2Fuploads%2FRi3dSZPgW1H1IqSEZoOq%2Fimage.png?alt=media&amp;token=f733ea55-1d58-4fc5-aa44-b6ccab4a6722" alt=""><figcaption></figcaption></figure>

**Proprietary account**\
\
The first is the proprietary (or owner) account, which is the account where you can utilize all the funds as you desire to do so.\
\
This account should include all the funds that no longer belong to the final clients, and cannot be altered.\
\
These funds will be used to pay fees and create settlements to your own bank account.\
\
**Transactional account**\
\
You will also have a transactional account.\
\
All funds from completed deposits would go here and should remain in this account until the funds can no longer be altered by the players.\
\
These funds cannot be used for anything until they are moved to your proprietary account.\
\
**Basic Deposit Flow**

<figure><img src="https://1595349702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7aIgg5dys0yN8otrASQq%2Fuploads%2FpGGVtI461GeQpJl32n69%2Fimage.png?alt=media&amp;token=3a3ae770-24aa-4a93-8feb-74fdb0b5a18b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

* First, the user creates a deposit, and we get notified by you, the merchant.&#x20;
* After this, we send the payment information to the user.
* Once the user completes the deposit, the funds get added to your transactional balance account
  {% endhint %}

#### Basic Cashout Flow

<figure><img src="https://1595349702-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7aIgg5dys0yN8otrASQq%2Fuploads%2F7PU9kYwVf1jZzkuUJAgx%2Fimage.png?alt=media&amp;token=fc08fe73-9d9f-4136-9647-4f937a4fe5f5" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

* First, the user wants to create a cashout, once we receive all the information from you, we go to the next step.
* If your transactional account has enough balance in order to process the cashout, we'll remove the balance from there
* Otherwise, we'll utilize the funds directly from your proprietary's account.
* After this, the cashout is processed, and the funds are sent to the customer's bank account.
  {% endhint %}

If you want to learn more about the endpoints used in this solution, you can check them out here:

{% content-ref url="/pages/uvPyxXZ7OELAWQJURIvt" %}
[Transactional Account Endpoint](/api-documentation/deposits-api/endpoints/transactional-account-endpoint.md)
{% endcontent-ref %}