<p>Mycelium Gear fixed the issue (almost two weeks after I reported it) and now they send a webhook for 0 and for 6 confirmations, exactly the way I want it and the way I think everyone wants it.</p>

<p>I've implemented, tested and never deployed a workaround that uses three different block chain exploring APIs to manually confirm transactions.</p>

CC BY-SA 3.0
2017-01-27T21:46:19.720Z
2017-01-27T21:46:19.720Z
Z.T.
<p>As I understand, you need callbacks for 0,1,2+ confirmation. AFAIK, there are two options. Both work in similar ways and you can use your own HD wallet to receive similar to mycelium gear</p>

<ul>
<li>Blockchain.info <a href="https://blockchain.info/api/api_receive" rel="nofollow noreferrer">Receive API</a></li>
<li>Blockonomics <a href="https://www.blockonomics.co/views/api.html#payments" rel="nofollow noreferrer">payment API</a></li>
</ul>

<p>Note that if you are running an online store, you still need to use websocket API on browser in addition to the callbacks. This is to let the browser know that the payment is done, and then redirect to server to confirm the payment (without doing busy polling).</p>

CC BY-SA 3.0
2017-01-17T04:16:53.020Z
2017-01-17T04:16:53.020Z
dark knight
<p>If you would like to monitor a btc address and receive a webhook notification when that address sends or receives funds, you can use this <a href="https://cryptocurrencyalerting.com/wallet-watch.html" rel="nofollow noreferrer">Wallet Watch</a> tool.  In addition to webhook, a number of other methods are supported as well (SMS, Email, Telegram, etc).</p>

<p>Disclaimer: I am affiliated with a co-founder of this service.</p>

CC BY-SA 4.0
2019-06-08T00:39:16.867Z
2019-06-08T00:39:16.867Z
swirlybuns
<p>I'm running an online store. I added the option to pay using bitcoin, using Mycelium Gear.</p>

<p>Gear can be configured to wait for 0-6 confirmations and up to 48*60*60 seconds from the moment the payment address was generated for a transaction to be paid/confirmed.</p>

<p>There are three potentially interesting moments in the life of a transaction when someone might like to be notified:</p>

<ol>
<li>A transaction with an output that is being watched has been transmitted on the p2p network.</li>
<li>The transaction has been included in a block.</li>
<li>The transaction is fully confirmed (is 6 blocks deep).</li>
</ol>

<p>With regular bitcoins, I see that when I configure gear to wait for 6 confirmations and 24h, Gear sends two notifications. One for event #2 (transaction included in block) and one for event #3 (transaction confirmed).</p>

<p>With testnet, when configured the same way it behaves the same way, only the testnet blocks are tiny and sometimes happen frequently. But when configured to not wait for confirmation (and only wait for 15 minutes), Gear sends a single notification, after event #1 (transaction transmitted).</p>

<p>What I actually want is to be notified as soon as possible after the customer has transmitted a transaction (event #1), and be notified within minutes of the transaction being fully confirmed (event #3).</p>

<p>If no transaction was transmitted within the first 15 minutes, consider the order abandoned (and the payment address eligible for reuse).</p>

<p>I think what I want is reasonable. But I don't see how to get it from Gear.</p>

<p>Is there a way to get this from Mycelium Gear? If not, is there an alternative service that does the same thing Gear does, but can send the two notifications I need (event #1 and event #3)?</p>

<p>Alternatively, how do other people do it, without using coinbase/braintree/bitpay and without running a full node client on the server?</p>

<p>My best idea currently is to configure Gear to not wait for confirmation to get the first notification, and then follow up the transaction manually using some blockchain explorer API to find out whether it got included in a block and how many blocks deep, until it's fully confirmed and then I can generate the second notification. But if I have to use a second service (some kind of blockchain exploration API), Gear will be a disappointment.</p>

<transactions><unconfirmed-transactions>
How to find out as soon as possible about a transaction to my payment address?
Z.T.
# How to find out as soon as possible about a transaction to my payment address?

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

I'm running an online store. I added the option to pay using bitcoin, using Mycelium Gear.

Gear can be configured to wait for 0-6 confirmations and up to 48\*60\*60 seconds from the moment the payment address was generated for a transaction to be paid/confirmed.

There are three potentially interesting moments in the life of a transaction when someone might like to be notified:

1. A transaction with an output that is being watched has been transmitted on the p2p network.
2. The transaction has been included in a block.
3. The transaction is fully confirmed (is 6 blocks deep).

With regular bitcoins, I see that when I configure gear to wait for 6 confirmations and 24h, Gear sends two notifications. One for event #2 (transaction included in block) and one for event #3 (transaction confirmed).

With testnet, when configured the same way it behaves the same way, only the testnet blocks are tiny and sometimes happen frequently. But when configured to not wait for confirmation (and only wait for 15 minutes), Gear sends a single notification, after event #1 (transaction transmitted).

What I actually want is to be notified as soon as possible after the customer has transmitted a transaction (event #1), and be notified within minutes of the transaction being fully confirmed (event #3).

If no transaction was transmitted within the first 15 minutes, consider the order abandoned (and the payment address eligible for reuse).

I think what I want is reasonable. But I don't see how to get it from Gear.

Is there a way to get this from Mycelium Gear? If not, is there an alternative service that does the same thing Gear does, but can send the two notifications I need (event #1 and event #3)?

Alternatively, how do other people do it, without using coinbase/braintree/bitpay and without running a full node client on the server?

My best idea currently is to configure Gear to not wait for confirmation to get the first notification, and then follow up the transaction manually using some blockchain explorer API to find out whether it got included in a block and how many blocks deep, until it's fully confirmed and then I can generate the second notification. But if I have to use a second service (some kind of blockchain exploration API), Gear will be a disappointment.

**Tags:** transactions, unconfirmed-transactions


---

## 3 answers

### Answer by username_0 on 2017-01-27. Score: 1 | Accepted answer

Mycelium Gear fixed the issue (almost two weeks after I reported it) and now they send a webhook for 0 and for 6 confirmations, exactly the way I want it and the way I think everyone wants it.

I've implemented, tested and never deployed a workaround that uses three different block chain exploring APIs to manually confirm transactions.


---

### Answer by username_1 on 2017-01-17. Score: 1

As I understand, you need callbacks for 0,1,2+ confirmation. AFAIK, there are two options. Both work in similar ways and you can use your own HD wallet to receive similar to mycelium gear

* Blockchain.info [Receive API](https://blockchain.info/api/api_receive)
* Blockonomics [payment API](https://www.blockonomics.co/views/api.html#payments)

Note that if you are running an online store, you still need to use websocket API on browser in addition to the callbacks. This is to let the browser know that the payment is done, and then redirect to server to confirm the payment (without doing busy polling).


---

### Answer by username_2 on 2019-06-08. Score: 0

If you would like to monitor a btc address and receive a webhook notification when that address sends or receives funds, you can use this [Wallet Watch](https://cryptocurrencyalerting.com/wallet-watch.html) tool. In addition to webhook, a number of other methods are supported as well (SMS, Email, Telegram, etc).

Disclaimer: I am affiliated with a co-founder of this service.


---

