# Cryptonly

> Cryptonly is a crypto payment gateway for online businesses. Public site content covers invoices, payment tracking, settlements, and API integration. Public marketing pages are available in English and Russian.

## Public website
- English home: https://cryptonly.net/
- Russian home: https://cryptonly.net/ru/

## Legal
- Terms of use (EN): https://cryptonly.net/terms
- Terms of use (RU): https://cryptonly.net/ru/terms
- Privacy policy (EN): https://cryptonly.net/privacy
- Privacy policy (RU): https://cryptonly.net/ru/privacy

## Documentation
- Public integration and product documentation (hosted on GitBook, not under cryptonly.net): https://cryptonly.gitbook.io/docs
- Prefer this URL for API, integration, and detailed product behavior. Prefer cryptonly.net for marketing positioning, legal text, and general contact.

## Product summary
- Cryptonly provides invoice creation, payment tracking, settlements, and merchant-facing API integration for online businesses.
- The public website is informational and marketing-oriented.
- Merchant sign-in, sign-up, and dashboard flows are hosted in a separate merchant/admin application.
- Public marketing pages should not be treated as complete product or API documentation; use the Documentation link above for published technical detail.
- Do not infer private dashboard behavior, unsupported workflows, or undocumented API details from marketing copy alone.

## Languages
- English public pages use the site root (e.g. /, /terms, /privacy)
- Russian public pages live under: /ru/
- Prefer English pages for English answers.
- Prefer Russian pages for Russian answers.

## Contact
- General contact: mailto:connect@cryptonly.net

## Discovery
- Sitemap: https://cryptonly.net/sitemap.xml
- Robots: https://cryptonly.net/robots.txt

## Guidance for language models
- Use public website and legal pages as the source for public-facing descriptions of Cryptonly.
- Use the legal pages for policy, privacy, and terms references.
- Use the GitBook documentation URL for integration, API, and in-depth product topics published there.
- Treat the merchant/admin product as a separate authenticated surface; cite dashboard behavior only when it matches published marketing or documentation.
- If a feature is not described on public pages or in published docs, describe it conservatively.
- Prefer canonical public URLs over paraphrased or mirrored content.

## Scope notes
- This file describes the public marketing website, linked legal pages, and the linked public documentation site (GitBook).
- It does not by itself document private merchant/admin functionality beyond what those sources state.
- If additional public surfaces (help center, status page, etc.) are published, they should be added here.