Accept Bitcoin and stablecoinsstraight to your own wallet

No, and not as a policy we could change — as an architectural fact. You give us an extended public key or a receiving address. Those can generate addresses and watch for payments, but they cannot sign a transaction. Funds move from your customer to your wallet without ever entering an account we control.

No. KYC exists because custodial processors handle other people's money and inherit the regulatory obligations that come with it. We never take custody, so that obligation does not arise. We ask for an email address and nothing else.

No, and that is deliberate. A free tier on a payment gateway attracts throwaway stores that consume node capacity and support time while never becoming customers, and the cost of carrying them lands on the people who do pay. Instead every plan opens with a 14-day trial with full Growth features, and paid plans start at $2 a month — low enough that the decision is not really about money.

We email you before it expires. If you do not pay, your stores stop accepting new payments but nothing is deleted, and any payment already made to your wallet is untouched because it was never ours to hold. Pick a plan whenever you are ready and everything resumes where it left off.

Because a USDT transfer costs the sender roughly a dollar or two in network fees. Invoicing you $2 would mean the fee is most of what you pay, which is a bad deal disguised as a cheap one. Selling the Starter plan in longer blocks keeps the fee a rounding error instead of a surcharge.

None. You pay a flat monthly or yearly price and keep 100% of every payment. The only cost per transaction is the blockchain network fee, which goes to miners or validators — never to us. On TRON that is typically a fraction of a cent.

Any wallet you already control. For Bitcoin, export a watch-only extended public key from Sparrow, Electrum, BlueWallet, or a hardware wallet such as a Ledger or Trezor. For stablecoins, any TRON or Ethereum address works, including an exchange deposit address. Never send anyone your seed phrase, including us.

Nothing happens to your money, because we never had it. Past payments are already in your wallet and remain fully spendable with your own keys. You would lose the dashboard and need another way to generate invoices — an inconvenience, not a loss. This is the single most important difference between self-custody and a custodial processor.

Yes, by connecting your own Lightning node or NWC connection. We deliberately do not offer a shared Lightning node: a shared node means we hold the keys to your channel funds, which would make us custodial for exactly the balance you are trying to keep control of.

Yes. The engine is BTCPay Server, which is open source and free to self-host. Your wallet is already yours, and your store configuration can be recreated on your own server. We keep customers by being cheaper than the effort of leaving, not by trapping them.

You send the refund directly from your own wallet, and record it in the dashboard against the original invoice. Because we never hold the funds, we cannot push a refund on your behalf — which also means no processor can ever reverse a settled payment against your will.

We publish the exact BTCPay Server version and container image digest we run on our trust page, so you can compare it against the official release. You can also independently verify every payment on the blockchain, because payments settle to addresses derived from your own key rather than to ours.