And the best solution is to run my own node with bitcoin core where I directly interact with Bitcoin core to get all the data I need, right? Is it really recommended to interact with Bitcoin core directly or do you guys can suggest any other tool for it?

Thanks @DannyHamilton for the answer. It also feels good to be hit with such clear words. So thank you for that! However, I must remain stubborn and unfortunately cannot be persuaded to use anything but a single deposit address. And the matter with the userID is not a problem either, I just don't want to reveal exactly how I do it. It's not so relevant anyway. The assignment to users would then be a different topic.

It can be thought of as a donation address. And this address remains the same. I would like to now record the donations that come in into my database. But it's also good to hear that it's indeed not so simple. I do know quite a bit about cryptocurrencies, as long as it doesn't get too specialized (like with Bitcoin Core development). It's therefore good to read that I haven't overlooked a simple solution for my problem and that it actually presents a challenge, which I'm happy to take on.

It's not about the wallet, it's about my project concept. There can only be one deposit address for it. So this won't work with BTCpay, because BTCpay always generates new addresses?


Oh, I see, then I am dependent on a specific client. I thought I could just make a regular API call to request transaction data. That's not so nice. But it could be noted as a temporary solution.


I wonder how Bustabit or Luckybit processes or processed deposits. I'm probably imagining it too simply to process deposits. All I want is to save new deposits into my database and keep checking them until they have 6 confirmations.

What do you mean with "they have the option to add bitcoin"? So I can tell them I want to use their Bitcoin API and then they enable it for me? But why don't they offer it regularly?

Unfortunately, they do not offer Litecoin. Many other unknown coins, but no Litecoin, which is used extremely often for payments. Very strange.


Thanks. So with BTCpayserver I can process deposits through Litecoin and Ethereum as well? Without fees? I will look into it. But its strange that the name is btcpayserver, when its not just for Bitcoin.

And I know, but I have to run everything via one payment address. There's no other way. Thanks!

I don't understand why it's so complicated. Cryptocurrencies are meant to be used for payments. So why is it so hard to process them? Even the API providers on the market don't seem to offer really optimal solutions. That's strange. I'm going to take a look at BTCpayserver. However, I also need a solution for Ethereum and Litecoin. And I definitely want to use only one deposit address. I don't want new addresses to be generated all the time.

It's very disappointing and incomprehensible that it's so complicated. But if I run my own node, then it's much easier to process deposits, right? Or does it also require a lot of makeshift solutions?

Thank you for your help!

Hello!

I would like to process deposits, but I am not quite sure how to best go about it. Unfortunately, I cannot and do not want to operate my own node at the moment (because then I have to download the entire blockchain and it is complicated to work directly with the node), to process deposits, so only an external API comes into question.

Here's the scenario: I have only one address to which all deposits should go. My service works without accounts and the sender's address is the UserID. The user should be directly shown on the website that the transaction has been received. In addition, the confirmations of the transactions should be updated and displayed promptly. But only up to 6 confirmations. After that, the deposit is successful, and we do not need to query the additional confirmations. It is important to me that if my web server goes offline, the system also processes the deposits during the time the server was offline.

My solution with which I am not quite satisfied and I hope there is a better and more efficient solution: I query all transactions of my deposit address every 2 minutes. But this also gives me the old deposits that have already been processed. Therefore, the server must first look at which deposits are new to include them in the database. Then I still run a websocket, which immediately informs me when there is a new block. And if that is the case, I query the transaction details for all deposits that still do not have 6 confirmations, to get the current number of confirmations. And I only do that whenever a new block was calculated, since no new confirmation can happen before that. And then I query all transactions of my deposit address again every 2 minutes and look for the new deposits that are not yet in the system. And again and again.

My problem with my solution: The API I currently use only outputs the last 10,000 transactions. This means that as soon as 10,001 transactions come in new within 2 minutes, then one transaction is lost. Although that is already a very unrealistic scenario to receive that many deposits in such a short time. However, it also bothers me that it is not really efficient. Because I always query all transactions and then have to sort out again and again, although I only need the new transactions. I hope that there might be a better way. I thought I could ask Blockchair for transactions within a certain period of time. So if the last query was for the period 12:04:00 to 12:06:00, then I query the transactions in the time between 12:06:00 to 12:08:00 in the next API call. And if there is ever downtime, then I just take the time of the last retrieval and the current time. But Blockchair somehow does not allow filtering by date. And other providers do not offer that either...

My question: How would you proceed? What is the best and most efficient way to process deposits? Deposits should always go to just one address and be booked as successful at 6 confirmations. In addition, users should always be promptly informed about new confirmations. Maybe you also know directly a provider with a good and affordable API... I would be very grateful. I'm still a bit new to the topic.

Many, many thanks and have a good day!