# Crypto Payment

Agency Handy’s Crypto Payment option lets you accept cryptocurrency from clients using simple wallet-based transfers. With customizable instructions, manual confirmation, and optional proof of payment, it’s ideal for agencies working with crypto-preferred clients.

### What You Can Do

* Enable Crypto Payment as a checkout option
* Add wallet details and network-specific instructions
* Choose whether to require proof of payment
* Accept Bitcoin, Ethereum, USDT, USDC, and more. (Right now, only USDC is acceptable.)
* Display instructions in email and invoice views
* Manually confirm payment before progressing the order
* Control visibility by workspace and service group

### Why It Matters

* Offer flexible, modern payment options
* Customize instructions for each wallet or currency
* Avoid missed payments with optional file uploads
* Keep invoices and orders aligned with payment verification
* Maintain control with manual confirmation flow

### Who Can Use This

To set up or manage crypto payments, users must:

* Have a Super Admin or Admin role
* Access Integrations and Workspace Settings
* Have permission to edit service payment options

***

### Getting Started

#### 1. Enable Crypto Payment

* Go to **Integrations**
* Click **Crypto Payment**
* A wallet setup screen opens with a rich text editor\ <br>

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

#### 2. Enter Wallet Details

Admins can enter:

* **Cryptocurrency Type** (e.g., Bitcoin, Ethereum, USDT, USDC. Right now, only USDC is acceptable.)
* **Wallet Address**
* **Network Type** (e.g., ERC-20, TRC-20, BTC)
* **Additional Instructions** (e.g., memo, tag, support contact, minimum amount)
* **Require Proof of Payment** toggle
  * If enabled: Clients must upload a file
  * If disabled: Payment can proceed without proof
* Click **Save** to store the setup
* Crypto Payment can be edited or disconnected anytime
* Input is XSS and HTML sanitized for safety\ <br>

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

***

### Client Checkout Flow

#### When Clients Choose Crypto Payment

* The system creates:
  * **Order** with status: *Pending*
  * **Invoice** with status: *Open*
* Clients are shown wallet info and instructions
* A file upload button appears in the invoice (if proof is required)
* In the **Catalog**, clients can upload payment proof
  * If required and no file is uploaded → no order/invoice
  * If not required → order and invoice are created regardless

***

### Manual Confirmation

Admins must manually verify off-platform payment.

* Once confirmed, mark the **Invoice as Paid**
* If invoice is marked Paid and order is *Pending* → order updates to *Ongoing*
* If order is already *Completed* or *Canceled* → no changes occur

***

### Email Notifications

#### After Order Creation

* Clients receive wallet transfer instructions via email
* Based on rich text editor content from crypto setup

***

### Proposal Integration

* If crypto is configured, “Pay with Crypto” will appear on accepted proposals
* Clients can pay in crypto from proposal invoice view

***

### Additional Notes

* Crypto Payment appears at checkout only if enabled in:
  * **Workspace Settings → Payment Methods**
  * **Service Grouping → Payment Availability**
* If disabled in Workspace Settings, crypto won’t appear—regardless of other settings
* **USDC** is now a supported currency
* If a service does not support USDC, crypto payment is hidden for that service
* File uploads are required only if “proof of payment” toggle is on
* Clients can view wallet details again from the invoice at any time


---

# 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://docs.agencyhandy.com/english/agencyhandy-user-guide-for-agency/integration/crypto-payment.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.