How to Set Up BTCPay for Self-Hosted Crypto Payment Processing
Learn how to take control over your own crypto payment processing with BTCPay.
Publish date: 3/1/2025
Learn how to take control over your own crypto payment processing with BTCPay.
Publish date: 3/1/2025
If you want to accept Bitcoin (and many more kinds of crypto, such as Ethereum, Litecoin, or Monero) payments without depending on third parties, BTCPay is your answer.
The challenge, though? A full Bitcoin node consumes over 600GB of storage at the time of writing — which can be a significant expense when paying for hosting (and this is only Bitcoin). The solution? Running a pruned node, which gives you the same validation benefits while using as little as 60GB of space, depending on what crypto currencies you want to support. Quite a bit less space to say the least.
That said, in this guide, I'll walk you through how to set up a pruned BTCPay server. Let's dive in.
BTCPay Server is an open-source, self-hosted payment processor that lets you accept Bitcoin and other cryptocurrencies directly, without intermediaries taking fees or controlling your funds. When you run BTCPay Server, payments go straight to your wallet—no middlemen, no permission needed.
By default, Bitcoin nodes download the entire blockchain history (over 600GB and growing). Pruning is a Bitcoin Core feature that discards older transaction data after verification, keeping only recent blocks and the UTXO set (unspent transaction outputs). This dramatically reduces storage requirements.
For a pruned BTCPay server, you'll need a server or VPS with:
xTom's V.PS platform is perfect for this. You can grab a plan here, such as our "Premium" package that'll work perfectly for self-hosting a BTCPay server. Otherwise, make sure you have a server with the minimum specs above.
Also:
Now let's set up your BTCPay server.
For my server, I've picked Ubuntu 22.04 LTS, as it's currently the officially recommended Linux distribution by BTCPay, but anything that supports Docker should work.
If you’re using another distribution, you’ll need to adjust certain commands (like changing apt to dnf/yum etc.). There may be minor differences for Debian as well.
Connect to your server using SSH as root:
ssh root@your_server_ip
apt update && apt upgrade -y
apt install -y apt-transport-https ca-certificates curl gnupg software-properties-common ufw
ufw allow ssh
ufw allow http
ufw allow https
ufw enable
BTCPay uses Docker for easy deployment.
On Ubuntu, you can install Docker with:
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] \
https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" \
| tee /etc/apt/sources.list.d/docker.list > /dev/null
apt update
apt install -y docker-ce docker-compose
systemctl enable --now docker
For Debian 12, we have a guide here. Other distributions are similar but may require different commands.
Still as root, do the following:
mkdir -p ~/btcpay
cd ~/btcpay
git clone https://github.com/btcpayserver/btcpayserver-docker
cd btcpayserver-docker
export BTCPAY_HOST="btcpay.EXAMPLE.com"
export NBITCOIN_NETWORK="mainnet"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_ADDITIONAL_FRAGMENTS="opt-save-storage-s"
export BTCPAYGEN_REVERSEPROXY="nginx"
export BTCPAYGEN_LIGHTNING="clightning"
export BTCPAY_ENABLE_SSH=true
Note: The
opt-save-storage-sfragment enables pruning, using about 60GB for Bitcoin’s blockchain data. For additional BTCPay settings available, such as enabling additional crypto currencies, view their documentation here.
In your domain registrar or DNS provider, create an A record pointing to your server’s IP:
Type: A
Host: btcpay (or any subdomain you like)
Value: Your_Server_IP
TTL: 3600
After DNS propagation (1-24 hours), BTCPay will automatically configure SSL using Let’s Encrypt when you access your domain.
The setup script must be sourced (not simply executed) so that its environment exports persist in your current shell.
Run:
. ./btcpay-setup.sh -i
(The leading . is crucial—it means "source this script.")
This process will take some time as it downloads Docker images, configures containers, and starts synchronizing the Bitcoin blockchain in pruned mode.
Once installation is complete and DNS has propagated:
https://your-domain.comTo verify your node is pruned:
cd ~/btcpay/btcpayserver-docker
./bitcoin-cli.sh getblockchaininfo
Look for:
"pruned": true — Confirms pruning is enabled"pruneheight" — Oldest block stored"size_on_disk" — Current blockchain data usageCheck BTCPay services:
./btcpay-status.sh
Update BTCPay:
./btcpay-update.sh
Even with a pruned node, regular backups are essential.
Create backups of:
cp ~/btcpay/btcpayserver-docker/.env ~/backups/env-$(date +%Y%m%d).backup
cd ~/btcpay/btcpayserver-docker
./bitcoin-cli.sh backupwallet ~/backups/wallet-$(date +%Y%m%d).backup
Bitcoin initial synchronization can take days.
To check progress:
./bitcoin-cli.sh getblockchaininfo
Compare "blocks" with "headers" to see how far along you are.
If you run out of space despite pruning:
grep BITCOIN_PRUNE ~/btcpay/btcpayserver-docker/.env
If you can't connect to your BTCPay Server:
sudo ufw status
cd ~/btcpay/btcpayserver-docker
docker-compose ps
Setting up a pruned BTCPay server gives you the perfect balance of sovereignty and efficiency. You maintain full control over your payment processing, it's easy to setup, and just works. What more is there to want out of a payment processor?
As mentioned above our VPS line will work great for a BTCPay server, but if you're looking to expand beyond a VPS, xTom offers a full range of solutions to support your growth, from dedicated servers with abundant storage for full nodes to colocation services for your own hardware. Check out xTom's services page to explore all options.
Thanks for reading, and here's to control over your own payment processing! ;-)
A full Bitcoin node stores the entire blockchain history (over 600GB), while a pruned node only keeps recent blocks and the UTXO set after validating the entire chain. Pruned nodes provide the same security benefits while using significantly less storage.
A pruned BTCPay Server can run comfortably on a 80GB NVMe VPS from xTom's V.PS platform. The Bitcoin blockchain data will use approximately 60GB (depending on your pruning settings), with the rest available for the BTCPay Server application, database, and future growth.
No. A pruned BTCPay Server can process payments just as effectively as one running on a full node. The pruning process only removes historical data after validation, not information about current unspent outputs needed for payment processing.
With xTom's high-performance NVMe storage and reliable network, initial Bitcoin synchronization typically takes less than one day with pruning enabled. This varies based on network conditions, and your chosen VPS specifications. Higher-tier V.PS plans with more CPU cores will synchronize faster.
Yes, but you'll need to start synchronization from scratch. If you anticipate needing a full node in the future, consider xTom's dedicated servers with larger storage capacities instead of a VPS solution.
Absolutely. A pruned node validates the entire blockchain just like a full node — it simply discards older blocks after verification. Your pruned BTCPay server maintains the same security properties as a full node for current transactions.
Basic Linux command line skills are helpful for maintenance and troubleshooting. However, once set up, a BTCPay server requires minimal intervention, mostly consisting of occasional updates.