Answers, before you have to write to us.

Payaries is a multi-chain crypto payment gateway. Your backend creates an invoice through the API, Payaries returns a one-time deposit address, and your ledger is credited as soon as the customer's payment reaches its required confirmations. You can then withdraw any amount to any address, on demand.

Payaries, spelled P-A-Y-A-R-I-E-S. It is the crypto payment gateway at payaries.com. "Prairie" is an ordinary English word for a grassland and a different thing; search engines often autocorrect "payaries" to "prairies", and people looking for the gateway often type "Prairie". If you were looking for a crypto payment gateway, you are in the right place.

Engineering and finance teams that want to accept and move crypto without running blockchain infrastructure themselves — online stores, SaaS products, marketplaces and other businesses that take payments in stablecoins or native coins.

You can sign up, create a test API key and run a real invoice in the same sitting — test keys work immediately, with no approval step. Live API keys are available once your account has been approved.

Ethereum, BNB Smart Chain, Polygon, Arbitrum, Tron and Bitcoin, with native coins (ETH, BNB, POL, TRX, BTC), stablecoins such as USDT and USDC, and other major tokens such as DAI and WBTC. More chains and assets are being added. Deposits and on-chain withdrawals are supported on every chain except Bitcoin, which currently supports deposits only. The live list is always available from the public GET /v1/chains endpoint.

Yes. USDT is supported on Ethereum (ERC-20), BNB Smart Chain (BEP-20), Polygon, Arbitrum and Tron (TRC-20), and USDC on Ethereum, BNB Smart Chain, Polygon and Arbitrum. Coverage keeps growing — check the live GET /v1/chains endpoint for the current list.

No. Payaries runs on real mainnet networks only. Test-mode API keys transact on the same real chains as live keys — "live mode" only means your account has been approved — so integration testing uses a small real payment.

You can request a custom ERC-20, BEP-20 or TRC-20 token for your account: you supply the chain and contract address, the platform reads the symbol and decimals from the chain, and an admin reviews it. Once approved and active, you can create invoices (in token units, since there is no fiat price) and withdrawals in it; the fee is a flat USD amount paid from your fee wallet.

Yes. Each merchant can disable any chain or asset for their own account in the dashboard; creating an invoice for a disabled chain or asset is then rejected.

Payaries holds the funds for you. Each merchant gets a dedicated Payaries wallet per chain — never pooled with other merchants' funds — and you can check its live on-chain balance against a public block explorer at any time.

Your ledger is credited immediately when an invoice reaches its required confirmations. That amount becomes withdrawable once Payaries's sweep of the deposit address to your Payaries wallet confirms on-chain, which is usually quick.

Not as a routine matter — there is no review queue or lock-up period on your balance. In extreme cases only, to protect against fraud or a security threat, Payaries can place a temporary hold on part or all of a balance. The held amount stays yours, is shown in your dashboard as a separate frozen figure, and nothing leaves your Payaries wallet on-chain because of it.

You can withdraw to any address on demand. Withdrawals made from the dashboard execute immediately and require two-factor authentication to be enabled. Withdrawals created by your API key execute immediately below your auto-approve threshold and wait for your own approval above it. Bitcoin withdrawals are not supported yet. Where Payaries's gas station covers a chain you pay no gas yourself — it is recovered as a network fee inside the transaction; elsewhere your Payaries wallet needs a little of the chain's native currency to pay network gas.

Fees are configured per merchant as percentage or flat rules, optionally scoped to a chain, an asset or an amount tier — so pricing depends on your account. Contact sales@payaries.com for a quote.

Through a REST API and a Node SDK. Your backend signs each request with HMAC-SHA256 using your API key and secret, creates an invoice, shows the customer the deposit address, and listens for signed webhooks. The Integration Guide in the merchant dashboard documents every endpoint and can be downloaded as a PDF.

Payaries sends a signed webhook on every invoice and withdrawal status change. Verify the X-Gateway-Signature header — an HMAC-SHA256 over the timestamp and raw request body. Failed deliveries are retried on a schedule that spans up to six hours: immediately, then after 1 minute, 5 minutes, 15 minutes, 1 hour and 6 hours.

An underpayment is flagged as underpaid, with the shortfall shown so you can refund or ask for the balance. A payment made on time but noticed late still moves an expired invoice to detected or underpaid; one mined after the deadline is held for review rather than credited automatically, and is either refunded or settled (a settled one carries latePayment: true in the webhook). Money that doesn't fit an invoice is recorded as an unclaimed deposit rather than dropped.

Every API request is HMAC-SHA256 signed with a timestamp and rejected past five minutes of clock skew; signatures are single-use for state-changing requests; and API keys can be restricted to specific IP addresses. Key management, webhook secrets, withdrawal approvals and threshold changes are dashboard-session-only, so a leaked API key cannot change them. Two-factor authentication is available for merchant accounts.

Yes. Partners onboard and manage their own merchants, set those merchants' fee rules (at or above the partner's own commission rate) and earn a commission share on the merchants' transactions, withdrawing earnings through a separate partner console. Partner accounts are created by Payaries — there is no self-service partner signup. Contact sales@payaries.com to discuss it.

No. Transactions are irreversible once confirmed on-chain, and crypto assets are volatile. Payaries locks the fiat-equivalent rate when an invoice is created, but any refund to a customer has to be sent by you as a separate transaction.