> 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/about-pay/introduction.md).
# Introduction
.png)
Pay enables digital asset processing functions for payments service providers, handling the conversion between cryptocurrency and fiat currencies. This product is offered by Aquanow, a leading digital assets liquidity and infrastructure provider trusted by the world’s fastest-growing financial institutions, internet platforms, and progressive businesses. Pay users benefit from cryptocurrency conversions executed with deep liquidity consolidated across global markets through the Aquanow infrastructure.
Fiat can be settled efficiently into preferred currencies and service provider bank accounts through our global banking network. We work closely with our clients to optimize settlement times through banking and inter-company processes.
Settlement is offered in three convenient ways:
* **Request** – withdrawal instruction made through Aquanow Platform or client support
* **Schedule** – withdrawal processed on a predetermined schedule (ex: daily, weekly)
* **Threshold** – withdrawal processed when your balance exceeds a set amount
### Payment Facilitation
For more information, please reach out to to set up a test account.
---
# 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/about-pay/introduction.md?ask=&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.
%20(1).png?alt=media&token=9f630035-9da0-452a-9586-0b6581f87d26)