Set up BTCPay Server
Run your own BTCPay server
This chapter is about how to set up and administer your own BTCPay server. It is about the setting options of the BTCPay Payment Server via the web backend. This guide is helpful if you want to know how to set up and administer your own BTCPay server.
If you don’t want to set up and run your own BTCPay server, but use a third-party solution, you can skip this chapter and go directly to the chapter Administering BTCPay Shop.
Set up BTCPay server
If you want to set up and run your own BTCPay server, we recommend the article BTCPay Server Hosting. For instructions on how to set up your own BTCPay server at LunaNode, see the article Hosting a BTCPay Server at LunaNode.
If you have set up a BTCPay server, this chapter will tell you how to set up and administer a BTCPay server.
Set up BTCPay Server
After the BTCPay server has been set up, you can set up the BTCPay server. After logging in as an administrator, the Server Settings menu item is displayed in the navigation bar. This menu item does not appear if you have logged in with a user account.
After you have clicked on Server Settings, you will get to the User Administration:
BTCPay Server User Management
In the user administration all users logged on to the server are administered. A distinction is made between the normal users who are assigned to the respective stores and admin users.
Rates from Bitcoinaverage
The menu item Rates contains the settings for the exchange rates.
Up to now, the provider Bitcoinaverage was deposited here. Bitcoinaverage has calculated an average price of all major exchange and provided these prices in real time. This service was free of charge until the beginning of 2020. Meanwhile, this has become a paid service, starting at $12 per month.
Those who want to do without this issue can do so without any problems. When setting at the store level, free alternatives can be selected, which provide the exchange rates.
We recommend to do without the paid services of Bitcoinaverage, because the alternative offers, which can be set on store level, are a very good and free alternative.
Configure email server
A central email address can be stored here, which is used for communication with the users. This is useful, for example, when a user wants to reset a password.
The Policies section defines the way in which the Payment Server is used.
If you want to use the payment server exclusively for your own business, no changes are made to the basic settings.
The BTCPay server is suitable for multi-shop. This means that an unlimited number of stores can be used for different users.
If you want to offer other users the possibility to run their own Bitcoin store on this server, some functions have to be enabled.
By default, registering from the home page is disabled. As an admin, new users can then be created manually via the User setting. If you deactivate the button, new users can log in directly.
This makes sense if you want to make the multi-shop function available to other store operators. If these new users are to verify the email address, “Requires a confirmation mail for registering” must be set.
If search engines are to be prevented from indexing the page, “Discourage search engines from indexing this site” must be activated.
If you operate several online stores and want to offer the Lightning payment option to all of them, activate the function “Allow non-admins to use the internal lightning node in their stores”.
The Lightning payment option is reserved for the operator of the own server, as all Lightning payments go only to a Lightning wallet. If you operate several stores, the sales can be collected in one wallet. This makes no sense if the other stores have no economic connection with the payment server operator. This makes no sense if the other stores have no economic connection with the payment server operator.
The same applies to the item “Allow non-admins to create hot wallets for their stores”. Normal users are referred to as non-admins. If you want to allow the operators of your own store to send the Bitcoin sales to your own wallet, this item is activated.
Services – Crypto Services
This section is about the settings for using Lightning. As already written above, the payment by Lightning can be offered exclusively by the operator of the payment server to its customers.
Anyone running a store on this server as a non-admin can only accept Bitcoin payments, but not Lightning payments.
When installing the BTCPay server, there was an option to choose the Lightning variant from the provider LND or C-Lightning.
Those who have chosen the LND variant will then be presented with this view:
If you have chosen the C-Lightning variant, you will see this view:
With this, the following applications can be used, which were presented under application examples.
For more information about Lightning and the different applications under LND and C-Lightning, please refer to the chapter Lightning
In the Theme chapter you can customize the look of the BTCPay server. At this point, we are not talking about the design of the individual stores and applications. The design of the stores or the payment page is administered under Stores.
At this point the login page to the BTCPay server can be changed.
If you have set up your own payment server, then this server runs at a hoster or on a different computer than the online store. If you want to run the payment server on a unique url, you can specify the domain here.
In DNS management, you then generate an A record and enter the name of the sub-domain. For example, this can be demo for the address https://demo.coincharge.io.
Then, in addition to the DNS entry, the sub-URL must also be entered here.
The log file of the server is located here and documents the activities on the server.
In the Files area, you can store additional data that is needed to use the server. This can be logos or images for the visual appearance of the server and stores. Likewise, the files can be placed here if you want to sell files, images, software or downloads.
In order to be able to use the storage space, this function must first be enabled in the Services area.
If this function is enabled, then the storage of files can be used under Files.