# Cryptonly ## Documentation - [Welcome](https://cryptonly.gitbook.io/docs/readme.md) - [Choosing a payment method](https://cryptonly.gitbook.io/docs/guides/choosing-a-payment-method.md): A quick comparison of Invoices, Deposits, Address provision, and Withdrawals to help you pick the right building block. - [Invoices](https://cryptonly.gitbook.io/docs/guides/invoices.md) - [Processing Lifecycle](https://cryptonly.gitbook.io/docs/guides/invoices/processing-lifecycle.md): This page explains how Cryptonly processes invoices from the moment a merchant creates a payment request to the moment funds are settled internally. - [Statuses](https://cryptonly.gitbook.io/docs/guides/invoices/statuses.md): Invoice statuses describe where an invoice is in the payment flow, from creation to final settlement. - [Deposits](https://cryptonly.gitbook.io/docs/guides/deposits.md): Standalone crypto top-ups to a merchant account balance. - [Processing Lifecycle](https://cryptonly.gitbook.io/docs/guides/deposits/processing-lifecycle.md): This page explains how Cryptonly processes standalone deposits from address assignment to balance crediting. - [Statuses](https://cryptonly.gitbook.io/docs/guides/deposits/statuses.md): Deposit statuses describe where a standalone top-up is in the payment flow, from creation to final settlement. - [Address provision](https://cryptonly.gitbook.io/docs/guides/address-provision.md): A reusable deposit address for repeat top-ups from the same customer. - [Processing Lifecycle](https://cryptonly.gitbook.io/docs/guides/address-provision/processing-lifecycle.md): This page explains how Cryptonly reserves a pool address and processes each inbound payment during an address provision session. - [Statuses](https://cryptonly.gitbook.io/docs/guides/address-provision/statuses.md): Address provision session statuses; per-payment outcomes use deposit statuses. - [Withdrawals](https://cryptonly.gitbook.io/docs/guides/withdrawals.md): Withdraw funds from your Cryptonly merchant balance via the API or admin panel. - [Withdrawals lifecycle](https://cryptonly.gitbook.io/docs/guides/withdrawals/withdrawals-lifecycle.md): This page explains the withdrawal flow, webhook notification behavior. - [Auto converting](https://cryptonly.gitbook.io/docs/guides/withdrawals/auto-converting.md): Cover a withdrawal shortfall by converting other balances into the requested currency. - [Statuses](https://cryptonly.gitbook.io/docs/guides/withdrawals/statuses.md): Withdrawal statuses describe where a payout is in the process, from commit to final settlement. - [Onchain confirmations](https://cryptonly.gitbook.io/docs/guides/onchain-confirmations.md): Onchain confirmation requirements - [Supported currencies](https://cryptonly.gitbook.io/docs/guides/supported-currencies.md): Supported cryptocurrencies, networks, and fiat settlement currencies, and how to fetch them via the API. - [Fees and commissions](https://cryptonly.gitbook.io/docs/guides/fees-and-commissions.md): Where commissions and network fees apply across deposits, invoices, withdrawals, and auto-converting. - [Balances, transfers, and conversions](https://cryptonly.gitbook.io/docs/guides/balances-transfers-and-conversions.md): How merchant balances work across accounts, and the Transfer and Conversion entries you'll see in Transaction History. - [Sandbox environment](https://cryptonly.gitbook.io/docs/guides/sandbox-environment.md): Cryptonly provides a sandbox environment for testing merchant flows before going live. - [Testing your integration](https://cryptonly.gitbook.io/docs/guides/testing-your-integration.md): Two admin panel tools for verifying your integration: Transaction History and Test webhooks. - [Webhooks](https://cryptonly.gitbook.io/docs/integration/webhooks.md) - [SDK](https://cryptonly.gitbook.io/docs/integration/sdk.md): Official JavaScript / TypeScript SDK for the Cryptonly merchant API. - [API reference](https://cryptonly.gitbook.io/docs/integration/api-reference.md) - [Accounts](https://cryptonly.gitbook.io/docs/integration/api-reference/accounts.md) - [Currencies](https://cryptonly.gitbook.io/docs/integration/api-reference/currencies.md) - [Withdrawals](https://cryptonly.gitbook.io/docs/integration/api-reference/withdrawals.md) - [Webhooks](https://cryptonly.gitbook.io/docs/integration/api-reference/webhooks.md) - [Deposits](https://cryptonly.gitbook.io/docs/integration/api-reference/deposits.md) - [Address Provision](https://cryptonly.gitbook.io/docs/integration/api-reference/address-provision.md) - [Invoices](https://cryptonly.gitbook.io/docs/integration/api-reference/invoices.md) - [Zapier Integration](https://cryptonly.gitbook.io/docs/integration/api-reference/zapier-integration.md) - [Models](https://cryptonly.gitbook.io/docs/integration/api-reference/models.md) - [Idempotency](https://cryptonly.gitbook.io/docs/integration/idempotency.md): Cryptonly supports idempotent creation of invoices, deposits, and withdrawals. - [Authorization](https://cryptonly.gitbook.io/docs/integration/authorization.md) - [HTTP status codes](https://cryptonly.gitbook.io/docs/integration/http-status-codes.md) - [CMS Plugins](https://cryptonly.gitbook.io/docs/integration/cms-plugins.md) - [WooCommerce](https://cryptonly.gitbook.io/docs/integration/cms-plugins/woocommerce.md) - [Zapier](https://cryptonly.gitbook.io/docs/integration/cms-plugins/zapier.md) - [WHMCS](https://cryptonly.gitbook.io/docs/integration/cms-plugins/whmcs.md) - [Medusa](https://cryptonly.gitbook.io/docs/integration/cms-plugins/medusa.md): Accept cryptocurrency payments in Medusa v2 through Cryptonly hosted checkout. --- # 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, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on a page URL with the `ask` query parameter: ``` GET https://cryptonly.gitbook.io/docs/readme.md?ask= ``` 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.