Products
Built around how you actually get paid
Three ways to collect crypto, each mapping to one object in the API. Use the one that matches your business, or all three. Looking for your industry instead? See solutions by industry.
Checkout
Take a single payment at the moment of purchase
Create a Payment Intent, send the buyer to hosted checkout, and release the goods when the signed webhook confirms the payment on-chain.
Explore the flow →Subscriptions
Recurring crypto billing with a native Subscription object
Native subscription billing: trials, coupons, and automatic per-cycle invoicing your customer approves and pays.
Explore the flow →Invoicing
Send crypto invoices your clients can pay in one click
Email itemized invoices with a hosted payment page, automatic paid status on confirmation, PDF download, and overdue tracking.
Explore the flow →White-label · Self-hosted
Or run the entire gateway in your own infrastructure, holding your own keys
All three products above, deployed inside your environment and under your brand. Self-custodial like BTCPay Server, but multi-chain from day one and with the commerce layer included. And because you hold the keys, the payout policy is yours to set. That is what makes marketplace settlement and unattended player withdrawals workable.
See how a deployment works →Not sure which one you need?
Charge once and you want Checkout. Charge on a repeating cycle and you want Subscriptions. Bill first and collect later and you want Invoicing. They share the same settlement, the same webhooks, and the same dashboard, so combining them is normal rather than exceptional. If custody, data residency, or payout control are the constraint rather than the payment shape, start with white-label instead.