Author

Topic: Coinbase callback (Read 2150 times)

legendary
Activity: 1890
Merit: 1000
Landscaping Bitcoin for India!
October 13, 2013, 05:53:10 PM
#5
Please help me with coinbase callback please.
Callback is sent only once at the time of transfer bitcoins. There 0 confirmations. More callback is not sent. How to make a callback at 6 confirmations? After all, with 0 meaning no evidence of enrollment to make money as bitcoins may never come. Support is not responsible

I have had issues with Coinbase like this as well, they never admit it is their fault but I usually get callbacks around the 12th confirmation.

I would recommend using bitpay.com, they charge 1% (or as little as $30 a month + 0%) but they allow you to get a callback at 3 different levels, I believe something like 0, 3 or 6 confirms.

Coinbase payment processing is free, but you get what you pay for Wink

A better alternative would be to make RPC calls to a bitcoin daemon you control.
Thanks for the reply. Bitpay does not suit me. Coinbase send a callback immediately after payment (0 confirmations) and then do not send anything.

You can get the paid status here: https://coinbase.com/api/doc/1.0/transactions/show.html

Check if the payment is Pending or complete and proceed. I do know that complete is the status after 6-7 confirmations.

Alternatively, you can use blockchain.info or Bitcoin RPC itself to get this information nice and easy. No other site can be checked for Coinbase confirmations as Coinbase uses an offchain network.
copper member
Activity: 3948
Merit: 2201
Verified awesomeness ✔
October 11, 2013, 08:38:12 AM
#4
Why don't you use the BlockChain's API? Their callback fires every 10 minutes for a week and sends back how many confirms a transaction has. You can stop the callback by displaying "*ok*" on the callback page.
full member
Activity: 212
Merit: 101
October 11, 2013, 08:33:21 AM
#3
Please help me with coinbase callback please.
Callback is sent only once at the time of transfer bitcoins. There 0 confirmations. More callback is not sent. How to make a callback at 6 confirmations? After all, with 0 meaning no evidence of enrollment to make money as bitcoins may never come. Support is not responsible

I have had issues with Coinbase like this as well, they never admit it is their fault but I usually get callbacks around the 12th confirmation.

I would recommend using bitpay.com, they charge 1% (or as little as $30 a month + 0%) but they allow you to get a callback at 3 different levels, I believe something like 0, 3 or 6 confirms.

Coinbase payment processing is free, but you get what you pay for Wink

A better alternative would be to make RPC calls to a bitcoin daemon you control.
Thanks for the reply. Bitpay does not suit me. Coinbase send a callback immediately after payment (0 confirmations) and then do not send anything.
member
Activity: 79
Merit: 10
October 10, 2013, 02:28:11 PM
#2
Please help me with coinbase callback please.
Callback is sent only once at the time of transfer bitcoins. There 0 confirmations. More callback is not sent. How to make a callback at 6 confirmations? After all, with 0 meaning no evidence of enrollment to make money as bitcoins may never come. Support is not responsible

I have had issues with Coinbase like this as well, they never admit it is their fault but I usually get callbacks around the 12th confirmation.

I would recommend using bitpay.com, they charge 1% (or as little as $30 a month + 0%) but they allow you to get a callback at 3 different levels, I believe something like 0, 3 or 6 confirms.

Coinbase payment processing is free, but you get what you pay for Wink

A better alternative would be to make RPC calls to a bitcoin daemon you control.
full member
Activity: 212
Merit: 101
October 08, 2013, 02:03:52 AM
#1
Please help me with coinbase callback please.
Callback is sent only once at the time of transfer bitcoins. There 0 confirmations. More callback is not sent. How to make a callback at 6 confirmations? After all, with 0 meaning no evidence of enrollment to make money as bitcoins may never come. Support is not responsible
Jump to: