> For the complete documentation index, see [llms.txt](https://debitllama.gitbook.io/debitllama/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://debitllama.gitbook.io/debitllama/comparing-account-types.md).

# Comparing Account types

### Choose Virtual Account If

* You need to spend Native tokens. Currently there is no other way to do it for connected wallets, the native token would need to be wrapped into an ERC-20 first, like WETH to spend with a connected wallet.
* You want to create a separate account for each subscription payment. This lets you add balance for them separately while using the same tokens.
* You want to share passwords with your family. Sharing is not recommended, but if you share accounts with somebody else you should create a separate virtual account for them to spend from.

### Chose Connected Wallet If

* You only make payments using ERC-20 tokens.
* You have a Cold wallet you want to keep secure while making payments from it.
* You can control the allowed spending balance with ERC-20 allowance, optionally you can approve a large spend and top up the cold wallet as you go!
* You don't mind using a single account for multiple subsciptions. Wallet accounts can't be duplicated with the same EOA, token and chain. This means if you have a USDT Connected Wallet with EOA address X on BTTC, than that account can't be created twice. It can be however closed and recreated

### Do you regurarly use Metamask?

Then maybe virtual accounts are better.

### Do you want to set it and forget it and keep the wallet offline?

Then a Connected wallet will do!


---

# 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://debitllama.gitbook.io/debitllama/comparing-account-types.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.