> For the complete documentation index, see [llms.txt](https://docs.paymento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paymento.io/overview/wallet-options.md).

# Wallet Options

Every Paymento store uses one of two wallet methods:

* **Bring Your Own Wallet**
* **Paymento Embedded Wallet**

You select the wallet method before adding each store. A Paymento account can have stores using different wallet methods.

Both options are non-custodial. Paymento provides payment processing, checkout, blockchain monitoring, and merchant tools, but it cannot independently authorize transfers or move merchant funds.

### Bring Your Own Wallet

Bring Your Own Wallet allows you to receive payments directly in an external wallet you already control.

Depending on the blockchain, Paymento asks for:

* An extended public key, or **xPub**, for supported UTXO-based networks
* A public wallet address for supported account-based networks

Paymento uses this public wallet information to prepare payment instructions and monitor transactions. An xPub or public address cannot be used to sign transactions or spend your funds.

Paymento never asks for your external wallet’s:

* Private key
* Seed or recovery phrase
* Wallet password
* Signing credential

#### Where funds arrive

Customer payments arrive directly in the external wallet you configured. Paymento does not receive or forward the funds.

Because the payment is already in your wallet, Bring Your Own Wallet does not require a settlement step.

#### Customer checkout

On supported UTXO-based networks, customers receive a payment address and QR code.

On supported account-based networks, customers generally need to connect a compatible wallet to Paymento’s checkout. This allows Paymento to associate the transaction with the correct payment request.

Customers paying from an exchange account, custodial application, or wallet that cannot connect may be unable to complete these payments.

#### Your responsibilities

With Bring Your Own Wallet, you are responsible for:

* Securing your wallet
* Backing up its recovery information
* Confirming that your wallet supports the required address format
* Ensuring that your wallet can discover addresses derived from the supplied xPub
* Sending refunds
* Protecting the destination wallet from unauthorized access

Paymento cannot recover an external wallet because it never possesses its private keys or recovery credentials.

#### Can I use an exchange deposit address?

A public deposit address from an exchange may work for some supported account-based assets, but it is not recommended.

Exchange addresses may change, require destination tags or memos, reject unsupported assets, or be controlled by withdrawal and compliance policies outside Paymento’s control. For reliable non-custodial payment acceptance, use a wallet whose keys you control.

#### Choose Bring Your Own Wallet if:

* You already have a wallet setup you trust
* You want payments to arrive directly in that wallet
* You do not want a settlement step
* Your customers can use a compatible connected wallet when required
* You need an asset that Embedded Wallet does not currently support
* You prefer the lowest Paymento processing cost

#### Where funds arrive

Customer payments arrive in receiving addresses associated with your merchant-controlled store wallet.

Funds remain on-chain in the store wallet until you authorize settlement to the configured destination wallet.

### Paymento Embedded Wallet

#### Customer checkout

On supported EVM and Solana assets, customers receive a payment address and QR code. They can pay using a compatible wallet or exchange account without connecting a wallet to Paymento.

This can provide a simpler checkout experience for customers who:

* Do not use browser-extension wallets
* Prefer scanning a QR code
* Pay from an exchange account
* Are unfamiliar with wallet connections

Tron and TRC-20 payments are a current exception and still require a compatible connected wallet.

#### Settlement

Embedded Wallet payments require settlement when you want to consolidate funds into your configured destination wallet.

During settlement:

1. Paymento prepares the transaction request.
2. You review the settlement details.
3. You authorize the request using your passkey.
4. The blockchain processes the transaction.
5. Funds move to the configured destination wallet.

Paymento uses network-specific settlement workflows, but merchant authorization is required regardless of the blockchain.

Blockchain network fees apply when settlement is performed.

#### Your responsibilities

With Embedded Wallet, you are responsible for:

* Protecting your passkey and devices
* Configuring available backup or recovery methods
* Verifying the settlement destination
* Reviewing settlement details before approval
* Maintaining access to your authenticators
* Securing the external destination wallet

Paymento does not hold a recovery credential capable of bypassing your wallet authorization.

> **Important:** If you lose every registered authenticator and available backup method, Paymento may be unable to restore wallet access.&#x20;

#### Choose Embedded Wallet if:

* You want address-and-QR checkout on supported account-based networks
* Your customers may pay from exchange accounts or non-connectable wallets
* You do not want to configure an existing wallet for every asset
* You want each store’s received funds kept separate
* You are comfortable authorizing settlement when you want to consolidate funds
* You want Paymento to handle more of the payment-address infrastructure

### Tron and TRC-20

Tron and TRC-20 assets, including USDT-TRC20, currently require a connected-wallet checkout under both wallet methods.

Embedded Wallet does not currently provide a plain address-and-QR checkout for Tron. This is a limitation of Paymento’s current Tron payment and settlement implementation and cannot be changed through store settings.

If customers must be able to pay a stablecoin using a plain address or QR code, consider a supported stablecoin on an EVM or Solana network with Embedded Wallet.

Refer to [Supported Networks and Assets](/overview/supported-networks-and-assets.md) for current availability.

### Compare wallet methods

|                                        | Bring Your Own Wallet                  | Paymento Embedded Wallet                                               |
| -------------------------------------- | -------------------------------------- | ---------------------------------------------------------------------- |
| Wallet ownership                       | External wallet controlled by merchant | Store wallet controlled through merchant authorization                 |
| Wallet information provided            | xPub or public address                 | Passkey registration                                                   |
| Private key available to Paymento      | No                                     | No                                                                     |
| Can Paymento independently move funds? | No                                     | No                                                                     |
| Where payments arrive                  | Directly in the external wallet        | In the merchant-controlled store wallet                                |
| UTXO-based checkout                    | Address and QR code                    | Address and QR code                                                    |
| Supported EVM and Solana checkout      | Connected wallet generally required    | Address and QR code                                                    |
| Tron and TRC-20 checkout               | Connected wallet required              | Connected wallet currently required                                    |
| Settlement                             | Not required                           | Merchant-authorized settlement                                         |
| Settlement network fees                | Not applicable                         | Actual blockchain network fee                                          |
| Refunds                                | Sent manually from the external wallet | Merchant-authorized through Paymento where supported, or sent manually |
| Backup and recovery                    | Managed through the external wallet    | Based on registered authenticators and available recovery options      |
| Paymento fee                           | 0.5% per successful payment            | 0.5% + $0.20 per successful payment                                    |
| Embedded store fee                     | Not applicable                         | First store included; additional stores are $10 one-time               |
| Bitcoin Cash                           | Supported                              | Not currently supported                                                |

See the [Paymento pricing page](https://paymento.io/fees-and-pricing/) for current fees.

### Can I use both wallet methods?

Yes. The wallet method applies to each store, not the entire Paymento account.

For example, you could use:

* An Embedded Wallet store for customers who need a simpler checkout
* A Bring Your Own Wallet store for higher-volume payments that should arrive directly in your treasury wallet

Store and plan limits may apply. Refer to [Fees and Pricing](/company/fee-and-pricing.md) for current details.

### Can I change a store’s wallet method?

A store’s wallet method is fixed after the store is created.

To use a different method:

1. Create a new store.
2. Select the new wallet method.
3. Complete its wallet configuration.
4. Test the new store.
5. Replace the API credentials or store configuration used by your integration.
6. Disable the old store only after confirming the new integration works.

Creating a new Embedded Wallet store does not automatically move funds from an existing store. Settle or otherwise manage any remaining funds before discontinuing the old store.
