# Product Documentation

#### 3.1 Supported Social Platforms

HandlPay supports account authentication through the following platforms:

* Google
* X
* Instagram
* WhatsApp
* Telegram

These platforms are used for secure sign-in and account access only.

#### 3.2 Supported Payment Methods

HandlPay supports multiple payment methods and routes funds to the receiver’s connected wallet automatically.

**Sender-side payment methods include:**

* $USDC
* $CC
* Credit and debit cards
* Apple Pay

Coming:

* More crypto assets such as $CBTC, $USDCX, $USDT, Bitcoin, and memecoins
* Local wallets or payment rails (availability varies by region)

The sender does not need a HandlPay account to complete a payment.

**Receivers do not need to match the sender's payment method:**

* Funds are routed and delivered to the receiver’s connected wallet
* Conversion and routing are handled automatically by HandlPay
* The ability to link your bank account as a receiving option will be enabled soon

#### 3.3 Supported Blockchains

HandlPay currently supports the following blockchain networks:

* Polygon
* Ethereum
* Avalanche
* Base
* BNB Chain
* Soneium
* Canton Network

When a wallet is connected, supported assets for that network appear automatically in the dashboard.

HandlPay aims to make peer-to-peer payments completely interoperable, thus additional networks will become available soon.

#### 3.4 Supported Asset Types

Supported assets depend on the connected network and wallet.

**Assets Currently Included:**

**On all chains:**

* $USDC (for payments)

**On Polygon & Base:**

* $HANDL

**On Canton Network:**

* $CC
* $CBTC
* $USDCX

**When an asset is supported:**

* It appears automatically under the connected wallet
* Balances are shown per asset
* Asset-specific actions (send, receive, swap) become available

Asset availability may change based on network support and product updates.

#### 3.5 Swaps and Asset Conversion

HandlPay supports asset conversion where available.

For example:

* When in the app: Users may swap USDC to HANDL using the Swap action
* When sending a payment: Swap availability depends on asset type, wallet, and network

#### 3.6 Fees and Limits

**Fees and limits may vary depending on:**

* Payment method used by the sender
* Asset type
* Network conditions
* Routing path selected by Handl

All applicable fees are shown transparently in the app before a transaction is finalized. HandlPay does not apply hidden fees. Handl does not currently charge a platform fee for transaction usage.

**Limits may apply to:**

* Minimum transaction sizes
* Swap amounts
* Certain payment methods or regions

#### 3.7 HandlPay vs. The Rest

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

#### 3.8 Regional Availability and Restrictions

HandlPay is designed for global use, but on/off-ramp and bank account availability will vary based on:

* Local regulations
* Payment provider support

Some features, assets, or payment methods may not be available in all regions. Always refer to the app interface for the most up-to-date availability.

#### 3.9 Wallet Requirements and Best Practices

**When connecting a wallet:**

* Use a wallet address that does not require a memo or destination tag
* Avoid using centralized exchange deposit addresses
* Ensure the wallet supports the selected network

HandlPay routes payments to the wallet address exactly as provided. Users are responsible for ensuring the wallet is compatible.


---

# Agent Instructions: 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:

```
GET https://handlpay.gitbook.io/handl-lightpaper/overview/product-details/product-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.