Question 1

What is Paychainly?

Accepted Answer

Paychainly is crypto payment infrastructure for merchants and developers. It detects USDT payments on BNB Smart Chain in real time, automatically sweeps funds to your wallet, and fires HMAC-signed webhooks to your backend — all without custody of your funds.

Question 2

How quickly are deposits detected?

Accepted Answer

Deposits are detected within 3–6 seconds of a transaction being confirmed on-chain. Your webhook fires automatically as soon as the deposit is detected.

Question 3

Is there a sandbox mode for testing?

Accepted Answer

Yes. Sandbox mode uses BSC testnet and a separate test token (sUSDT), so you can test the full payment flow without spending real funds. Switch between production and sandbox from the top of any dashboard page.

Question 4

Do I need to install anything to integrate?

Accepted Answer

No software installation required. You use the REST API with your API key. We provide code samples for Node.js, Python, PHP/Laravel, and curl. The Getting Started guide walks you through your first integration in under 10 minutes.

Question 5

What networks and tokens are supported?

Accepted Answer

Paychainly currently supports USDT (Tether BEP-20) on BNB Smart Chain. This provides one of the highest-liquidity stablecoins with near-zero gas fees. Multi-chain and multi-token support is on the roadmap.

Question 6

Which address should I use as my receive wallet?

Accepted Answer

Your Binance USDT deposit address works perfectly. Go to Binance → Wallet → Deposit → USDT → select BEP-20 network → copy that address and paste it in the Receive Wallet page.

Question 7

When will funds arrive in my receive wallet?

Accepted Answer

Usually within 1–5 minutes after a customer pays. The system detects the payment automatically and sweeps the funds from the customer deposit address to your receive wallet.

Question 8

Do I need to create a new wallet?

Accepted Answer

No. You can paste your existing Binance BEP-20 deposit address directly — there is no need to create a separate wallet unless you prefer one. You can also use the "Generate address" option to create a fresh wallet whose private key you hold.

Question 9

Can I change my receive wallet address later?

Accepted Answer

Yes. Revoke the current address and add a new one. The old address moves to history and can be reactivated at any time. Only deposits after the change go to the new address.

Question 10

What happens if I forget to set a receive wallet?

Accepted Answer

Customer deposits are still collected and held at the deposit address, but the system cannot sweep them to your wallet until a receive address is configured. Set it up before going live to avoid any delay.

Question 11

Which network format must the address use?

Accepted Answer

Always select BEP-20 (BNB Smart Chain) when copying your Binance deposit address — not ERC-20 (Ethereum) or TRC-20 (Tron). Sending on the wrong network will result in lost funds that cannot be recovered.

Question 12

Why does the withdrawal wallet need to hold a balance?

Accepted Answer

When a withdrawal is triggered, the system sends USDT from this wallet to the recipient. If the balance is empty or too low, the withdrawal will fail. Keep a reasonable buffer based on your expected withdrawal volume.

Question 13

How do I fund the withdrawal wallet?

Accepted Answer

After adding the wallet, copy its address from the table and send USDT (BEP-20) to it from Binance or any other wallet. You can check the current balance at any time using the "Show balance" button.

Question 14

Can I use my Binance address as the withdrawal wallet?

Accepted Answer

No. The withdrawal wallet must be one you fully control with its private key, because the system needs to sign transactions from it. Use the "Generate wallet" option to create a fresh wallet, or import one you already have the private key for.

Question 15

What happens if the withdrawal wallet balance runs out?

Accepted Answer

New withdrawal requests will be rejected with an insufficient-balance error. Top up the wallet with USDT and retry failed withdrawals. We recommend keeping a buffer and monitoring the balance regularly.

Question 16

Is my withdrawal wallet private key safe?

Accepted Answer

Yes. Private keys are encrypted at rest using AES-256 and are never returned via the API. You can export it once from the dashboard to keep an offline backup. Treat it with the same care as any crypto wallet key.

Question 17

Is there a monthly fee or setup cost?

Accepted Answer

No. Paychainly has zero upfront cost and no monthly subscription. You pay only when you receive a payment or process a withdrawal. Setup, dashboard access, API key generation, and sandbox mode are all free.

Question 18

What is the deposit fee structure?

Accepted Answer

Deposit fees are tiered by payment size: free for payments under $10; $0.30 flat for $10–$60; 0.50% for $60–$200; 0.75% for $200–$1,000; 1.00% for $1,000–$5,000; and a $50 flat cap for payments above $5,000. A small gas reimbursement is also charged at sweep time to cover the on-chain transaction cost.

Question 19

What are the withdrawal fees?

Accepted Answer

Withdrawal fees are also tiered: free under $20; $0.30 flat for $20–$120; 0.25% for $120–$500; 0.20% for $500–$5,000; and a $20 flat cap above $5,000. Gas reimbursement applies when the system sends the on-chain transaction.

Question 20

What is gas reimbursement and how is it calculated?

Accepted Answer

Gas reimbursement covers the BNB network fee for the on-chain USDT transfer. It is calculated at sweep time using the live BNB/USDT price via PancakeSwap, so it reflects real network costs rather than a fixed estimate. On BSC this is typically $0.10–$0.50.

Question 21

Can I negotiate a custom fee structure?

Accepted Answer

Yes. High-volume platforms and institutional clients can contact us for custom fee tiers. We also support per-user fee overrides for businesses running multi-tenant setups.

Question 22

Is Paychainly non-custodial?

Accepted Answer

Yes. Paychainly never holds your funds. Customer payments go to HD-derived deposit addresses that belong to you, and sweeps happen automatically to your configured receive wallet. At no point do we control your master wallet keys.

Question 23

How are webhooks secured?

Accepted Answer

Every webhook is signed with HMAC-SHA256 using your secret key. The signature is included in the X-Webhook-Signature header. Always verify this signature on your server before processing any event — do not trust webhook payload without verifying.

Question 24

How are API keys stored?

Accepted Answer

API keys are hashed before storage and are never retrievable after creation. If you lose an API key, revoke it and generate a new one from the API Keys page. Keys can be scoped and revoked individually.

Question 25

What happens during RPC downtime?

Accepted Answer

Paychainly runs a multi-RPC failover pool. If one provider returns errors or rate-limits requests, the system automatically falls back to the next available endpoint. Blocks are also backfilled on startup so no payments are missed during brief outages.

Frequently asked questions

Getting Started

Receive Wallet

Withdrawal Wallet

Fees & Billing

Security

Still have questions?