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

# Payments

### Overview

*Payouts* and *Invoices* now appear together in one table. You create new records from two buttons at the top of the page:

* **Make a Payment**
* **Receive a Payment**

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FLVTEpbohWWtKX86JQzPu%2Fimage.png?alt=media&amp;token=b3f5b7e4-24df-4f9e-8bfb-51ad0268e1cb" alt=""><figcaption></figcaption></figure></div>

<table data-header-hidden><thead><tr><th width="169.83203125" valign="middle"></th><th width="153.3046875" valign="middle"></th><th valign="middle"></th></tr></thead><tbody><tr><td valign="middle"><strong>Button</strong></td><td valign="middle"><strong>Action</strong></td><td valign="middle"><strong>Description</strong></td></tr><tr><td valign="middle">Make a Payment</td><td valign="middle">Send funds out</td><td valign="middle">Creates a payout to a counterparty (previously the "Payouts" tab).</td></tr><tr><td valign="middle">Receive a Payment</td><td valign="middle">Request funds in</td><td valign="middle">Creates a payment link / invoice for a customer to pay (previously the "Invoicing" tab).</td></tr></tbody></table>

{% hint style="info" %}
Legacy Bill rows appear only for select legacy clients. Users can't create new Bills.
{% endhint %}

#### Payments table

This table lists every payment record created from "Make a Payment" and "Receive a Payment" into one unified view.

Columns: **Name**, **Nickname/Client Reference**, **Payment Type**, **Status**, **Currency,** **Amount**, **Created At**.<br>

**Search, filter, and group**

<table><thead><tr><th width="168.55859375">Control</th><th width="517.03515625">Behavior</th></tr></thead><tbody><tr><td>Search Payments</td><td>Dynamic search — matches against any field in the table (name, reference, currency, etc.) as you type.</td></tr><tr><td>Payment Type</td><td>Filter by Receive, Bill, or Payout.</td></tr><tr><td>Status</td><td>Filter by status. Statuses are grouped under their payment type (Receive / Bill / Payout) — see “Status reference” below.</td></tr><tr><td>Group by</td><td>Group the table by Name or Nickname/Client Reference. Grouping turns off pagination — all results load on one page — and each group shows a subheader with the group name and the number of payments in it. You can still search and filter further within a grouped view.</td></tr><tr><td>Timeframe</td><td>Quick presets: 1 week, 1 month (default), 3 months.</td></tr></tbody></table>

{% hint style="info" %}

* As the table combines three record types (payouts, invoicing, bills from legacy), only columns common to all three payment types are shown. Column-specific detail (e.g. **transaction hash**, **processing fee**) is available on the record's detail panel — see [Viewing payment details](#viewing-payment-details) below.
* Payments made toward an invoice/payment link no longer appear as their own row in the table. Instead, they show up inside the *Timeline* of their associated invoice's detail panel, including the received amount, the crypto asset used, the equivalent value in the invoice's fiat currency, and the transaction hash.
  {% endhint %}

The **Status filter** groups options under **Receive**, **Bill**, and **Payout**.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2Fs37i6cMrrjJD5DSiCxwo%2FScreenshot%202026-09-30%20at%2012.27.15%E2%80%AFPM.png?alt=media&amp;token=c7b44c2c-4256-4cb8-b02c-866eb49314a8" alt=""><figcaption></figcaption></figure></div>

\
Grouping by **Name** collapses the table into named groups with a payment count per group.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2F75u0zcjXfrqDQkAOm0H8%2FScreenshot%202026-09-30%20at%2012.28.18%E2%80%AFPM.png?alt=media&amp;token=83b7e645-7326-440b-b801-6b452440a851" alt=""><figcaption></figcaption></figure></div>

**Export Data**

1. Click the **Export** button at the top left of the table.&#x20;

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FDrMwoDiqgHWInbCEhsrw%2FScreenshot%202026-09-30%20at%2011.05.27%E2%80%AFAM.png?alt=media&amp;token=bca12b71-ef89-4b44-890a-8733da41ecf9" alt=""><figcaption></figcaption></figure></div>

2. In the **Export payments** popup that displays, select the relevant checkbox depending on the fields that you wish to include in the .CSV file.
   * **Files**: Choose which record types to include: **Payment links**, **Bills**, **Payouts** (all unchecked by default).
   * **Date range**: a From / To date picker. The range defaults to, and cannot exceed, 90 days back from today (the underlying API rejects longer ranges).

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FfOJ4SXp1aGkNkVlMSRgW%2FScreenshot%202026-09-30%20at%2011.16.58%E2%80%AFAM.png?alt=media&amp;token=22353568-f889-4c1e-8069-656b3ab0ea73" alt="" width="563"><figcaption></figcaption></figure></div>

2. Click **Export** to generate the files.&#x20;

The Excel files (*in .CSV format*) are downloaded accordingly.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FUt3UXGWUg807HtNLwuoT%2FScreenshot%202026-09-30%20at%2011.19.51%E2%80%AFAM.png?alt=media&amp;token=e3fc0a66-1131-4bc4-b0c5-d9f9ec508e1e" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Each selected file type downloads as a separate .CSV (Excel)file, named with the file type and the export date, e.g. \`payment-links-2026-09-23.csv\`, \`bill-payments-2026-09-23.csv\`, \`payouts-2026-09-23.csv\`. You can now select a custom date range from the .CSV file. A notification confirms the export and the downloads appear in your browser's download tray.&#x20;
{% endhint %}

{% hint style="info" %}
For Bills exports, records only appear under Bills if they were created through the legacy "create payment bill" / request-payment-address flow. New (V2) invoices created through Receive a Payment are separate records and are exported under Payment links, not Bills. Once a V2 invoice is paid, the payment itself does not create a duplicate row — it's recorded in the invoice's own Timeline (see [Viewing payment details](#viewing-payment-details) above).
{% endhint %}

### **Make a Payment**

You can use **Make a Payment** to send funds to a counterparty. This is a 3-step process.

**Step 1 — Select recipient**

Search for the recipient by name or **Nickname/Client Reference**. Only people already saved in your *Address Book* (as a counterparty) will appear in suggestions.

* If the recipient isn't saved yet, select Add a counterparty to run through the standard **Address Book add-counterparty** flow before continuing.

{% hint style="info" %}
*You can refer to the* [Address Book](https://app.gitbook.com/o/-MiexXFAgJWKsPoKe3J0/sites/site_DjRkZ/s/q8XmiPQ5qSiPF9SGTCz7/user-guide/account-management/address-book) and [Adding a Counterparty pages](https://app.gitbook.com/o/-MiexXFAgJWKsPoKe3J0/sites/site_DjRkZ/s/q8XmiPQ5qSiPF9SGTCz7/user-guide/account-management/address-book/adding_a_counterparty) *for more details on how to add a counterparty.*
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FUqP242Gk1c0JuMH2DWYT%2Fimage.png?alt=media&amp;token=a1a96061-53bf-4b16-ad69-9ce9056f3b09" alt=""><figcaption></figcaption></figure></div>

**Step 2 — Payout amount**

Choose the **Destination address** for the selected recipient (or **Add a new address**); this opens the same popup used in *Address Book*), then enter the amount and currency you are sending. The fiat drop down only shows fiats for which you currently have a balance.

{% hint style="info" %}
You can either choose to:

* enter the amount which you want to send&#x20;
* or enter an amount that the recipient is supposed to receive.&#x20;

Depending on your choice, the corresponding amount is calculated automatically.
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FWq84NL6pRL5EwYy9lIiX%2Fimage.png?alt=media&amp;token=1f57e722-3946-432d-8f05-3dca04e7549a" alt=""><figcaption></figcaption></figure></div>

**Step 3 — Confirm and get quote**

Once both sides of the amount are filled in on Step 2, the **Get quote** button becomes active. Click it to move to Step 3.

Review the locked-in quote for **You send**, **Recipient receives**, **Rate**, **Recipient**, **Sent from**, **Network**, **Nickname/Client Reference** and **Destination address**, before the quote expires. A live countdown is shown (e.g. “Quote expires in 21s”). Enter your 2FA code and select **Confirm**. You can also select **Edit amounts** to go back and adjust the quote.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2F093IXYgYyTiY4IkeLXjU%2FScreenshot%202026-09-30%20at%205.02.35%E2%80%AFPM.png?alt=media&amp;token=ca458e76-4866-4ec1-96d0-fb5eda205a40" alt="" width="563"><figcaption></figcaption></figure></div>

Once confirmed, a **Payout submitted** confirmation is shown with a status badge (**Processing**) and an **Order ID**.&#x20;

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2F8iazj8EvUB1ArfQoq9fP%2Fimage.png?alt=media&amp;token=51c348bf-a321-4ade-9482-c4ec34a75f91" alt=""><figcaption></figcaption></figure></div>

Select **Close window** — the payout appears as a new row in the **Payments** table.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FZ3U4aItBwabh7yyQtH49%2Fimage.png?alt=media&amp;token=a87c7e2d-af67-45aa-b35d-4ae6b0ee3e5e" alt=""><figcaption></figcaption></figure></div>

### Receive a Payment

Use **Receive a Payment** to request funds from a customer via a *shareable payment link*. This opens a popup with two options, depending on whether the customer's information is already on file or if the customer is new

* **Select customer** – You use this option when your customer's information is already on file (i.e., they exist in your Address Book). You search for them by name or by their **Nickname/Client Reference**, enter the **Billable Amount** and **Currency**, and choose who pays the fee. Because their info is already on file, the checkout flow skips KYC for the payer — when they open the link, they just pick what they want to pay with and go straight through checkout.
* **New customer** – You use this when the person is not in your Address Book yet. You can either enter the payee’s details, which saves them as a counterparty in your Address Book, or add an **Nickname/Client Reference** to identify them easily later. The **Nickname/Client Reference** is optional and can be left blank.&#x20;

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FdbnXXL86MswLlyowPlUL%2Fimage.png?alt=media&amp;token=0bb60249-935b-412b-991f-ebc011c51b8c" alt="" width="563"><figcaption></figcaption></figure></div>

#### **Select customer**

1. Choose the **Select customer** tab and search for the customer by name or **Nickname/Client Reference**.
2. Enter the Billable Amount and Currency.
3. Choose the relevant option from the **Who pays the fee** toggle.
   * **Merchant pays fee**: The customer pays only the original listed price, and the transaction fee is taken out of the business's final payout.
   * **Customer Pays Fee***:* The payment fee is added to the checkout total, so the buyer pays the extra cost and the business gets the full price of the item.&#x20;
4. Click the **Create payment** link button&#x20;

<figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FFuao6anoS5sZCMLLQJJ0%2Fimage.png?alt=media&amp;token=276680ee-5165-4c08-89b5-49caa8e22134" alt="" width="563"><figcaption></figcaption></figure>

#### **New customer**

1. Select the **New customer** tab.
2. Select the relevant option from the **Who provides customer details** dropdown.

* **Customer will provide their information at checkout**: In this case, you do not need to provide your customer's KYC. You just create and send the link, and when the customer opens it, *they* fill out their own KYC info as *Step 1* of the hosted checkout page (Payer information → Payment method → Pay).
* **I will provide the information**:  This opens the same *add-a-counterparty* popup used in *Address Book*. Completing it saves the person as a counterparty in your *Address Book* automatically.

<figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FPFIDYQ6q9wAP35oLHS7i%2FScreenshot%202026-10-08%20at%2010.07.40%E2%80%AFAM.png?alt=media&amp;token=8e52da3a-4c05-4331-9d0c-6a2b6df81ae9" alt="" width="563"><figcaption></figcaption></figure>

3. Enter the Billable amount, Currency and choose the relevant option from **Who pays the fee** tab.
4. Click the **Create payment link** button

### Payment Link Created

Once a payment link is created, a confirmation popup shows the shareable link and a pre-filled, editable message.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2Fj3LIuiRCrTLq0rTuL6IR%2Fimage.png?alt=media&amp;token=55ee8e36-d14c-40ee-8674-319552a81ef7" alt=""><figcaption></figcaption></figure></div>

The newly received payment (the invoice) is added to the **Payments** table.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2Fn1CM7sxUJW2vHRO5CSlf%2Fimage.png?alt=media&amp;token=72f7d1ae-3279-490d-97ae-4b146d2c239a" alt=""><figcaption></figcaption></figure></div>

#### Previewing the payment link

You have an option to preview a payment before sharing the payment link. To do so, click the **Preview payment** **link** to see how the payment details look like before you send it. \
\
The following details are observed on the payment link:

* Payer (your customer) information dropdown with the following options:
  * **Individual (I’m paying this invoice for myself)**
  * **Business (I’m paying this invoice on behalf of a business)**
* Invoice amount and its details

<figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FScceDRDRPGkT5CUzttDb%2Fimage.png?alt=media&amp;token=2d3b042d-7511-431b-a352-a59660978a96" alt=""><figcaption></figcaption></figure>

#### Sharing the payment link

Once you are satisfied with what you see in the payment preview, you can share the payment link via:

* **Email**: Opens your default mail app with the subject and message pre-populated. The message can be updated as per your preference.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FZNLIYIOpaZYDM3iYJOoN%2FScreenshot%202026-10-05%20at%209.37.41%E2%80%AFAM.png?alt=media&amp;token=abb6cfd2-98b5-4c0c-b93e-612e03e68663" alt=""><figcaption></figcaption></figure></div>

* **Send link**: Copies the link to your clipboard and you can share it via a message.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FID0TRLvGV810f1ZCdjEX%2Fimage.png?alt=media&amp;token=867d6e0a-2f49-4751-84f2-f549f5fdd7ef" alt=""><figcaption></figcaption></figure></div>

* **WhatsApp**: Opens WhatsApp’s own **Share on WhatsApp** page with the message pre-filled, with options to **Open app** or **Continue to WhatsApp Web**.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2Fuxsaxnl6l7cfVCsWvSLY%2Fimage.png?alt=media&amp;token=a0474adc-c347-4d91-be0a-c5ac3acbdc3e" alt=""><figcaption></figcaption></figure></div>

* **Telegram**: Opens Telegram’s share flow with the link.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FntMSUzPQiGqlUpd7CTLT%2Fimage.png?alt=media&amp;token=e58fe9da-c876-403e-a87b-2067163d798d" alt=""><figcaption></figcaption></figure></div>

The new request appears in the **Payments** table as a **Receive row**.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2F2hC7fDQ6RGjfM58lBL4C%2FScreenshot%202026-09-30%20at%2010.52.18%E2%80%AFAM.png?alt=media&amp;token=a7e975a1-11ad-4316-9a5c-b27e7353e1bb" alt=""><figcaption></figcaption></figure></div>

#### What the customer sees

The link opens a hosted Aquanow-powered checkout page for the payer.\
\
It has the following steps:&#x20;

* Payer/Customer information (Optional - depending on how you created the link)
* Payment method: The customer is asked about the crypto asset they want to pay with (e.g. BTC, ETH, USDT, etc.) and relevant wallet details. They also see a breakdown of the amount due, the fee, and the total invoice amount.

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FcraUUAPUFH5EqYp8XZln%2Fimage.png?alt=media&amp;token=7d13aab4-1ab8-4364-8511-dbd5fbcf79d0" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
In the **Wallet type** dropdown, there are two payment options for your customer to select from:

* **SELF\_HOSTED**: The wallet is controlled directly by the end customer (or the originating party) without an intermediary custodian — the user holds their own private keys.&#x20;

* **Managed by a VASP (Virtual asset service provider)**: The wallet is held and controlled on behalf of the user by a regulated or licensed third-party custodian (such as an exchange, broker, or custodian) rather than by the user directly.
  {% endhint %}

* Pay Details: The customer is shown the crypto address along with the amount of crypto that needs to be deposited

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2Fl5ne0WrN7Pr2yUeLQUQE%2Fimage.png?alt=media&amp;token=91915e05-4303-497c-a4cc-09b308bcc0c2" alt="" width="563"><figcaption></figcaption></figure></div>

### **Viewing payment details**

Select any row in the **Payments** table to open its detail panel on the right. The panel is broken into three sections:

* **Header**: Amount requested, current status badges (e.g. Open/Closed and payment status such as Not Paid/Paid), a progress bar, the amount received, and the outstanding amount.
* **Details**
  * **Who & When**: Name, Nickname/Client Reference, Created At, Expires At.
  * **Payment**: Payable Amount (total the payer must pay, fees included), Status, Billable Amount (what your business actually receives before fees), Payment Status, Received Amount, Customer Pays Fee (Yes/No), Processing Fee, Net Deposit.
  * **Transaction**: Payment Link ID and Payment Link (copyable).
* **Timeline**: A chronological log of events on the record (created, payments received, status changes), including the crypto amount, fiat-equivalent value, and transaction hash for each payment received.

At the bottom of the panel: **Copy payment link** and **Download** (exports a single CSV — \`payment-link.csv\` — for that record).

<div data-with-frame="true"><figure><img src="https://1474347080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIHDM5kXVLHS3COkFRZYu%2Fuploads%2FxdyGydaPkq32ChtHPdCr%2FScreenshot%202026-09-30%20at%2010.59.36%E2%80%AFAM.png?alt=media&amp;token=8b44750a-12a1-42bc-b48a-a72a1d205346" alt=""><figcaption></figcaption></figure></div>

**Reading the amount breakdown ("Paid example" above)**

* **BILLABLE AMOUNT**- The fiat amount you requested.
* **PAYABLE AMOUNT** - What the customer owes at checkout.
  * If you pay the fee: Payable Amount = Billable Amount.
  * If the customer pays the fee: Payable Amount = Billable Amount + Processing Fee
* **RECEIVED AMOUNT** - What the customer actually paid.
* **NET DEPOSIT** - What lands in your account; = Received Amount – Processing Fee

  In other words, what your business actually keeps. This layout lets you see at a glance, e.g., "paid a total of $101, minus a $1 processing fee, net deposit $100."

### Status reference

Statuses are grouped by payment type.

#### Receive (invoices / payment links)

<table data-header-hidden><thead><tr><th width="144.80859375" valign="middle"></th><th valign="middle"></th></tr></thead><tbody><tr><td valign="middle"><strong>Status</strong></td><td valign="middle"><strong>Meaning</strong></td></tr><tr><td valign="middle">Not Paid</td><td valign="middle">No payment received yet.</td></tr><tr><td valign="middle">Partially Paid</td><td valign="middle">A payment still in progress because crypto is sitting unconverted. Once the leftover crypto converts, a short invoice becomes Underpaid.</td></tr><tr><td valign="middle">Underpaid</td><td valign="middle">A finished payment that came up short.</td></tr><tr><td valign="middle">Overpaid</td><td valign="middle">More than the amount due was received.</td></tr><tr><td valign="middle">Paid</td><td valign="middle">Full amount received; record is Closed.</td></tr></tbody></table>

#### Bill (legacy)

<table data-header-hidden data-search="false"><thead><tr><th width="214.45703125" valign="middle"></th><th valign="middle"></th></tr></thead><tbody><tr><td valign="middle"><strong>Status</strong></td><td valign="middle"><strong>Meaning</strong></td></tr><tr><td valign="middle">Open</td><td valign="middle">Payment address is active and awaiting payment.</td></tr><tr><td valign="middle">Awaiting Confirmation</td><td valign="middle">Payment has been submitted and is awaiting blockchain confirmation.</td></tr><tr><td valign="middle">Overpaid</td><td valign="middle">More than the billed amount was received.</td></tr><tr><td valign="middle">Underpaid</td><td valign="middle">Less than the billed amount was received.</td></tr><tr><td valign="middle">Complete</td><td valign="middle">Bill has been paid in full.</td></tr><tr><td valign="middle">Not Converted</td><td valign="middle">Received funds have not yet been converted.</td></tr><tr><td valign="middle">Expired</td><td valign="middle">The bill link expired before payment was made.</td></tr><tr><td valign="middle">Awaiting Compliance</td><td valign="middle">Record is pending a compliance review. (Renamed from “Suspicious Transaction” — this is a front-end label change only, requested to align with AML terminology; the underlying pending-compliance / compliance-rejected states are unchanged.)</td></tr></tbody></table>

#### Payout

<table data-header-hidden><thead><tr><th width="138.92578125" valign="middle"></th><th valign="middle"></th></tr></thead><tbody><tr><td valign="middle"><strong>Status</strong></td><td valign="middle"><strong>Meaning</strong></td></tr><tr><td valign="middle">Processing</td><td valign="middle">Payout has been submitted and is in progress.</td></tr><tr><td valign="middle">Completed</td><td valign="middle">Payout has been successfully sent.</td></tr><tr><td valign="middle">Failed</td><td valign="middle">Payout did not complete.</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aquanow.io/pay/features/payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.