# Overview

> Explore the Paymos Merchant API for invoices, token balances, signed webhooks, and withdrawals on 11 payout networks, to whitelisted wallets by default.

## How it works

:::steps
### You create an invoice
Your server posts to the Paymos API with the amount and currency.

### Customer pays
Redirect to `payment_url`, embed the same checkout in an iframe with `?embed=true`, or drop in the Low-Code SDK to open it as a modal. On a Telegram-bot project that same link opens the Paymos bot, and the payer never leaves Telegram.

### Paymos watches the chain
Paymos detects the payment on-chain and confirms it once it reaches the number of confirmations that network requires.

### Webhook fires
Your server receives the signed event with the payment details.

### Balance credited
The asset lands in your Paymos balance, ready to withdraw on your schedule.
:::

## Why Paymos

| What you get | How it works |
|---|---|
| **No chargebacks** | On-chain payments are final at confirmation depth. No card-rail reversal 60 days later. |
| **Per-merchant pricing** | 1.0% all-in standard rate for everyone. Enterprise is 0.3%, on request. No monthly fee. Your current tier is on the dashboard. |
| **Withdraw on your schedule** | Balance credits at confirmation. Withdraw daily, hourly, never — your call. We don't lock funds. |
| **Stablecoins and XAUT only** | 4 fiat-pegged stablecoins (USDT, USDC, USD1, DAI) plus gold-backed XAUT. No volatile altcoins, no surprise settlement values. |
| **13 production networks** | A curated set with redundant RPC providers for each supported chain. |
| **HMAC-signed REST** | One canonical signing scheme; one auth pipeline; same security model your customers' APIs already use. |
| **Hosted checkout** | Send a `payment_url`, embed it with `?embed=true`, open it as a modal with the Low-Code SDK, or build your own UI on the REST endpoints. All of it applies to every project except a Telegram-bot one. |
| **Telegram bot checkout** | A project set to Telegram bot returns `payment_url` as a deep link into the Paymos bot. The payer picks asset and network and pays inside Telegram, without a Paymos account. |
| **Invoices or channels** | An invoice is one payment request with an amount and an expiry. A payment channel is one payer's permanent address that keeps accepting — no amount, no expiry, no address rotation. |

## Who uses Paymos

:::dash-list
- **E-commerce** — accept stablecoins at checkout alongside cards
- **SaaS & digital services** — bill international customers that card rails decline, without geographic gates
- **Donations & creators** — accept tips and contributions in stablecoins
- **iGaming / high-risk** — categories card processors refuse, on a payment rail that doesn't care
- **Freelancers and agencies** — receive cross-border payments without correspondent-bank fees
:::

## Getting started

:::dash-numbered
- [Quick start](/docs/quick-start.md) — first real mainnet payment in about 10 minutes
- [Hosted checkout](/docs/hosted-checkout.md) — redirect and iframe embed modes
- [Supported currencies](/docs/supported-currencies.md) — networks, tokens, fiat pricing
- [Payment flow](/docs/payment-flow.md) — the full invoice lifecycle
- [Payment channels](/docs/payment-channels/create.md) — permanent per-payer deposit addresses
:::