How can we help?

Click Create account anywhere on the site. The server generates a 16-digit account key, shows it once, and you're in — no email, password or documents. See the no-KYC page for why it works this way.

Without 2FA recovery codes a lost key is unrecoverable by design — we never store it in a recoverable form and have no email to reset against. Store it like cash. Enabling TOTP 2FA also gives you ten one-time recovery codes; keep those somewhere safe too.

Yes — turn on TOTP two-factor authentication in Settings → Security. Any authenticator app works, and you get ten single-use recovery codes. With 2FA on, withdrawals also require a fresh code.

None, at any volume, ever. There is no compliance tier, no document request and no review queue anywhere in the product — identity is simply never collected.

From Settings, once your balance is under $1 (withdraw the rest first). Closing removes the account's configuration; the append-only ledger record is retained for platform integrity.

You create an invoice — via the API, a no-code payment link, or a shop. The customer lands on a hosted checkout with a QR code and a dedicated address, pays from any wallet, and we watch the chain and credit you the moment it confirms.

Trust the signed webhook or an authenticated API read — never the browser redirect. The redirect URL is a convenience for the customer; it can be abandoned, repeated or forged, so it is not proof of payment. See webhooks in the docs.

Two snapshots — fiat→USD and crypto→USD — lock together the instant an invoice is created, sourced and cross-checked independently. Stale or anomalous rates fail closed: the invoice refuses to be created rather than mispricing your sale.

The invoice stays open and shows the exact remainder at checkout and in your dashboard — a quick nudge usually completes it. Underpayments never silently settle as paid.

The full received amount is credited and the invoice settles as paid. You keep the overage, or return it as a payout to the customer's address if you prefer.

After 30 minutes by default — you can set anything up to 24 hours. An expired invoice can't be paid; simply create a new one. Funds that already landed on-chain still credit.

There is no sandbox — the API is live-only. Test end-to-end with a small real amount on a fast, cheap chain such as Solana or Tron, which settle in seconds for fractions of a cent.

Twelve assets across seven networks — Bitcoin, Ethereum, Monero, Solana, Litecoin, Dogecoin, Tron, USDT (TRC-20 & ERC-20), USDC, DAI, SHIB and PEPE. The currencies page lists live confirmations and settlement times.

When it reaches its network's confirmation threshold — from seconds (Solana, Tron) to about 20 minutes (Bitcoin, Monero, Dogecoin). Once confirmed, settlement is final: crypto has no chargebacks.

Yes, first-class, on our own node infrastructure. Each invoice gets a unique subaddress, so payment IDs are handled automatically — nothing for your customer to paste or lose. See the Monero page.

A small per-asset minimum — typically around $0.50 to a few dollars, shown at checkout and via the API — keeps dust payments from being eaten by network fees.

1% flat per settled payment. Nothing else — no setup, monthly, per-invoice, conversion or chargeback fees. The fees page compares this honestly with BitPay, CoinGate and NOWPayments.

Your customer pays the network fee on their deposit, as in any wallet transfer. On withdrawal you pay only the payout transaction's network fee — shown live before you confirm, with no margin added by us.

No, deliberately. Every merchant pays the same flat 1% from the first invoice to seven figures a month — no rate cards, no sales calls, no opaque tiers.

No. Pricing in 30 fiat currencies and USD accounting are included, and the independently verified rate that locks at invoice creation is the rate you settle at — no spread is added.

Instantly from your dashboard, or automatically. Funds are reserved the moment you request and sent on-chain — usually within minutes. There is no approval queue and no way for anyone to freeze them.

Set a destination address and a balance threshold per asset; when a coin's balance crosses its threshold it sweeps itself to your wallet. It is off by default and you switch it on per account.

Automatic sweeps are capped at $1,000 per payout as a safety rail; anything above that is queued for you to release manually. Manual withdrawals have no such cap.

The asset your customer paid. Balances are shown in USD terms for clarity but withdrawn in kind to addresses you control.

If you have enabled TOTP 2FA, yes — every withdrawal, from the dashboard or the API, requires a fresh code. It is the one action a code is always asked for, because it moves money.

A refund is simply a withdrawal you send to the customer's address — there is no dispute process to fight, because crypto has no chargebacks. Stablecoin refunds are exact; for volatile assets, state in your terms whether you refund the crypto amount or the fiat value.

On-chain transactions are irreversible — funds sent to a wrong or mistyped address are lost. Always double-check; the withdrawal form warns you before you confirm.

A no-code hosted checkout for a single product or amount, shareable as a URL (on cryptopaylink.co) or a QR code — no integration required. Create one in the dashboard under Links.

Yes. Attach a message, a download/redirect link, or a pool of license keys (up to 10,000) handed out one per payment and never reused. The buyer sees the delivery on their receipt the moment payment confirms.

Yes — add custom fields such as a delivery email, in-game username or Discord handle. Answers attach to the payment and are visible only to you.

Yes — cap the number of uses, or let a key-backed link close automatically when its keys run out. You can also fix the price or let the buyer enter their own amount.

A hosted storefront that groups several products on one branded page — no code, two themes, live preview. Each product is a payment link under the hood, so delivery and keys work the same way.

Yes — storefronts live on the dedicated shopycrypto.com domain (separate from your checkout links), so customers see a clean, shop-specific URL.

Up to 10 shops per account, 50 products per shop, and up to 30 variant combinations per product (sizes, editions, tiers…), each with its own price and key inventory.

Yes. Mark a product physical and pick the countries you ship to; the checkout then collects a shipping address. Digital and physical items are bought in separate checkouts.

A payment link needs zero code. The REST API is essentially one endpoint to create a payment (POST /v1/payments) plus one webhook to receive settlement — most developers ship in an afternoon with the docs.

Bearer secret keys, up to 50 per account. Each key carries a fixed set of scopes chosen at creation — payments, links, shops, balance and payouts (read/write). Scopes can't be widened later; issue a new key instead. A call outside a key's grant returns 403 insufficient_scope.

Send an Idempotency-Key header (1–128 characters) when creating a payment. Replaying the same key returns the original payment; reusing it with a different body returns 409 idempotency_conflict.

Yes, per key and per IP. Every response carries X-RateLimit-Limit, -Remaining and -Reset; exceeding the limit returns 429 with a Retry-After, and the edge applies its own per-IP guard.

A consistent JSON envelope: {"error":{"type","message","request_id"}}. Types include invalid_request, invalid_parameter, insufficient_scope, rate_limited, idempotency_conflict and temporarily_unavailable. Quote the request_id in any support ticket.

Payments, payment links, shops with their products and variants, your balances, and withdrawals (with 2FA). GET /v1/account reports the calling key's scopes and your account limits.

Every event is signed with HMAC-SHA256 and timestamped; verify the signature against your endpoint secret before trusting it. Failed deliveries retry automatically with backoff. Verification snippets are in the docs.

The full payment lifecycle: payment.created, pending, confirming, completed, underpaid, overpaid, expired and failed — plus webhook.test. Make your handler idempotent; retries are expected.

Yes — up to 10 endpoints, either account-wide or tied to a specific API key, each with its own secret you can rotate. Every event fans out to all matching endpoints, and you can re-send any delivery from the dashboard.

An append-only double-entry ledger records every movement immutably — balances are explainable line by line and nothing is ever erased. TOTP 2FA guards login and withdrawals, and strict security headers, rate limits and an isolated, outbound-only network path protect the platform.

Balances accrue on the platform between settlement and withdrawal, as with any hosted gateway. Auto-withdraw thresholds let you keep that float as close to zero as you like — the destination is always a wallet you control.

For the same reason you trust a vending machine: the mechanism, not the paperwork. Rates verify independently and fail closed, the ledger never erases, webhooks are signed, and the fee is one transparent number. Identity was never part of that trust chain.

Anything unlawful under the law that applies to you or your customers — see the terms. No-KYC removes the paperwork about you, not the law about your product; you remain responsible for what you sell.

Yes. Crypto revenue is ordinary revenue in virtually every jurisdiction. Your USD-denominated ledger and CSV exports (Analytics → Export) keep bookkeeping straightforward.

Open a ticket from your dashboard (Support in the sidebar); tickets are answered by humans, with no account-manager tiers. Include a request_id for anything API-related.