<p>First, Electrum relies on Electrum servers, which are essentially a third party SaaS for SPV proofs. It's a fine thing to use for most people and as long as you aren't concerned that the server may compromise your privacy, you should be fine. But that said, you can say that about any SaaS service, so Electrum is probably not the solution you're looking for.</p>

<p>If you want to do everything yourself, you will have to run a full node at a minimum. You can create a wallet using a library like pycoin (<a href="https://github.com/richardkiss/pycoin" rel="nofollow noreferrer">https://github.com/richardkiss/pycoin</a>) but that's much more work than using a full-node wallet like Armory.</p>

<p>There's actually webshop code written for processing bitcoin payments yourself (<a href="https://github.com/goatpig/BitcoinArmory/tree/master/webshop" rel="nofollow noreferrer">https://github.com/goatpig/BitcoinArmory/tree/master/webshop</a>). The main benefit here is that only the public key is on the server so even if you get hacked, your bitcoins can't move without your say-so. Full disclosure: I wrote that code.</p>

<p>Another option may be using bitcoind, but that will require you to keep your private key on the server (NOT A GOOD IDEA).</p>

CC BY-SA 3.0
2017-02-26T15:19:08.150Z
bitcoind supports watch-only addresses since 0.10, removing the meed to have your keys online
Pieter Wuille
CC BY-SA 3.0
2017-01-23T15:29:21.290Z
2017-01-23T15:29:21.290Z
Jimmy Song
<p>You could build a bespoke solution for accepting Bitcoin by using a bitcoind server - it's not that hard to be honest even though I never found a complete foolproof guide.</p>

<p>Few things to keep in mind - some may be obvious but when put together you need to pay particular attention to them:</p>

<ol>
<li>Never credit an account with at the very least 1 confirmation - taylor it the way you want but 4 confirmations is good</li>
<li>Transactions could contain payments to 2 different users on your site - using different addresses</li>
<li>Use <strong>walletnotify</strong> to get transactions notification - it will occur the first time the transaction is seen on the network and once more when it received 1 confirmation</li>
<li>Use <strong>blocknotify</strong> to get block notification - when you get this, you can go through all the unconfirmed transactions in your system and increase the confirmation number - then if it crosses your threshold, the payment is deemed complete.</li>
<li>Just as a precaution and to complement the above 2 points, I set up a cron job running every 30 min to check I have not missed anything since the last block. I have fait un the notifications but better be safe than sorry</li>
</ol>

<p>The infastructure is fairly straight-forward and then it all depends on your environment and preferred coding language. There are various sites that can give you pointers on how to connect to a running bitcoind node and pull data from it.</p>

<p>Good luck - I have been down that path several times and learnt as I went along.</p>

CC BY-SA 3.0
2017-01-22T12:56:41.377Z
2017-01-22T12:56:41.377Z
Alex
<p>I want to be able to accept and process bitcoins on my website only by mysefl. With no 3rd party bitcoin services. How can I do that? One way is to use Electrum. But its documentation regarding merchant is really bad. Does anyone have experience with that?
It doesn't have to be Electrum, though, and any bitcoin software will.
I'm a programmer, I'm ok implementing a neccesary part, it if I have to, by myself.</p>

<electrum><merchants><payment-processors>
Processing bitcoins on my website completely by myself, with no third-party bitcoin SaaS services
Gaji
# Processing bitcoins on my website completely by myself, with no third-party bitcoin SaaS services

(Asked by: username_0 on 2017-01-21)

I want to be able to accept and process bitcoins on my website only by mysefl. With no 3rd party bitcoin services. How can I do that? One way is to use Electrum. But its documentation regarding merchant is really bad. Does anyone have experience with that?
It doesn't have to be Electrum, though, and any bitcoin software will.
I'm a programmer, I'm ok implementing a neccesary part, it if I have to, by myself.

**Tags:** electrum, merchants, payment-processors


---

## 2 answers

### Answer by username_1 on 2017-01-23. Score: 2

First, Electrum relies on Electrum servers, which are essentially a third party SaaS for SPV proofs. It's a fine thing to use for most people and as long as you aren't concerned that the server may compromise your privacy, you should be fine. But that said, you can say that about any SaaS service, so Electrum is probably not the solution you're looking for.

If you want to do everything yourself, you will have to run a full node at a minimum. You can create a wallet using a library like pycoin (<https://github.com/richardkiss/pycoin>) but that's much more work than using a full-node wallet like Armory.

There's actually webshop code written for processing bitcoin payments yourself (<https://github.com/goatpig/BitcoinArmory/tree/master/webshop>). The main benefit here is that only the public key is on the server so even if you get hacked, your bitcoins can't move without your say-so. Full disclosure: I wrote that code.

Another option may be using bitcoind, but that will require you to keep your private key on the server (NOT A GOOD IDEA).

> **Comments:**
> **username_2**: bitcoind supports watch-only addresses since 0.10, removing the meed to have your keys online  

---

### Answer by username_3 on 2017-01-22. Score: 1

You could build a bespoke solution for accepting Bitcoin by using a bitcoind server - it's not that hard to be honest even though I never found a complete foolproof guide.

Few things to keep in mind - some may be obvious but when put together you need to pay particular attention to them:

1. Never credit an account with at the very least 1 confirmation - taylor it the way you want but 4 confirmations is good
2. Transactions could contain payments to 2 different users on your site - using different addresses
3. Use **walletnotify** to get transactions notification - it will occur the first time the transaction is seen on the network and once more when it received 1 confirmation
4. Use **blocknotify** to get block notification - when you get this, you can go through all the unconfirmed transactions in your system and increase the confirmation number - then if it crosses your threshold, the payment is deemed complete.
5. Just as a precaution and to complement the above 2 points, I set up a cron job running every 30 min to check I have not missed anything since the last block. I have fait un the notifications but better be safe than sorry

The infastructure is fairly straight-forward and then it all depends on your environment and preferred coding language. There are various sites that can give you pointers on how to connect to a running bitcoind node and pull data from it.

Good luck - I have been down that path several times and learnt as I went along.


---

