as I never see that transaction hitting our side in either my wallet or logs / database? 
Topic: blockchain.info wallet API - transactions not forwarded to main wallet (Reward) (Read 1907 times)
September 28, 2013, 09:49:23 AM
Hmm - Thanks for the quick response, but can you dumb it down for me as I never see that transaction hitting our side in either my wallet or logs / database?
as I never see that transaction hitting our side in either my wallet or logs / database? 
September 28, 2013, 08:41:57 AM
From how our deposit application works, this would disrupt how we would properly credit our customer's accounts.
You could fetch the users receiving address e.g. https://blockchain.info/address/17FcpJFGAT8NkcKtMsnvpcjnzrMnezGzT1?format=json
and extract the transaction hashes and amounts from there.
Here's another recent example of us not receiving the 'forwarded' transaction: https://blockchain.info/tx/0b872095382829d55b7cd2132132f60dd93bd91f464d6e17a9a4d201023b72ce
Seems like it was forwarded correctly to me: https://blockchain.info/tx/ac22686c4cf8bd6ce04aa0aa05aa81064c473015fe44a98687b018957de2141d
https://blockchain.info/address/1Fq7RxSgZ6sRNFNZumYGSrHDr2jVmNrohu
Your server is correctly responding with the *ok* message.
September 28, 2013, 07:18:30 AM
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Tim,
The above two transactions were combined and forwarded in one transaction - https://blockchain.info/tx/eea53810936c07020522b279f263495a62349a5f9977c418c2a682ddef6d3d1b. Inputs can be combined to save on transaction fees, but the total amount received at your end should be the same. You will receive one notification for the total amount rather than separate notifications for each input.
I assume 1GC6ucWxo5stow6U8A1gUaptK77n7E6FhQ your receiving address?
Yes - that's correct... So how would we know when many transactions are grouped together and forwarded to the main address? From how our deposit application works, this would disrupt how we would properly credit our customer's accounts.
Here's another recent example of us not receiving the 'forwarded' transaction: https://blockchain.info/tx/0b872095382829d55b7cd2132132f60dd93bd91f464d6e17a9a4d201023b72ce
September 27, 2013, 06:17:05 AM
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Tim,
The above two transactions were combined and forwarded in one transaction - https://blockchain.info/tx/eea53810936c07020522b279f263495a62349a5f9977c418c2a682ddef6d3d1b. Inputs can be combined to save on transaction fees, but the total amount received at your end should be the same. You will receive one notification for the total amount rather than separate notifications for each input.
I assume 1GC6ucWxo5stow6U8A1gUaptK77n7E6FhQ your receiving address?
September 26, 2013, 10:28:14 PM
It's probably because Mandrik isn't a blockchain.info representative. From his post history, there is nothing to indicate that he is a support personnel for any site.
I've only been with Blockchain.info for a couple weeks, so yeah. My post history isn't going to show it. It's much easier for me to keep track of issues via our ticketing system, but I still want to keep an eye on Reddit & the forums.
I'm hoping to get some more information on your issue very soon. Again, sorry for the delays.
September 26, 2013, 08:38:23 PM
Hey Everyone!
Sorry if this is the wrong place for this; however - I create a ticket with blockchain.info a while ago that was never answered.
Here's your situation - we leverage the blockchain.info APIs for deposits and withdrawals on our site, works great 99% of the time; however - there are a few instances where customers will send bitcoin to their designated receiving address and it doesn't show up on our side for hours, even after it's confirmed. Below are 2 such examples which were generated today.
In this case the user's receiving address is "17FcpJFGAT8NkcKtMsnvpcjnzrMnezGzT1"
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Any and all help is appreciated and will be rewarded with a bounty!
Thanks,
Tim
Sorry if this is the wrong place for this; however - I create a ticket with blockchain.info a while ago that was never answered.
Here's your situation - we leverage the blockchain.info APIs for deposits and withdrawals on our site, works great 99% of the time; however - there are a few instances where customers will send bitcoin to their designated receiving address and it doesn't show up on our side for hours, even after it's confirmed. Below are 2 such examples which were generated today.
In this case the user's receiving address is "17FcpJFGAT8NkcKtMsnvpcjnzrMnezGzT1"
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Any and all help is appreciated and will be rewarded with a bounty!
Thanks,
Tim
Just from the title.
If you imported a wallet you created locally on BC, then you might have reached the 100 address limit.
I guess any new local address after the 100 first were used would not receive any notification from BC, as it would not be associated to you.
September 26, 2013, 08:16:06 PM
No problem!
We haven't received any further guidance on this issue - any help is appreciated.
I've only been with Blockchain.info for a couple weeks, so yeah. My post history isn't going to show it. It's much easier for me to keep track of issues via our ticketing system, but I still want to keep an eye on Reddit & the forums.
I'm hoping to get some more information on your issue very soon. Again, sorry for the delays.
September 20, 2013, 10:31:33 PM
No problem!
We haven't received any further guidance on this issue - any help is appreciated.
September 20, 2013, 06:50:38 AM
No problem!
We haven't received any further guidance on this issue - any help is appreciated.
September 17, 2013, 03:46:56 PM
No problem!
September 17, 2013, 03:44:40 PM
Hey, Tim! I just wanted to let you know that I do see your ticket, and I'm escalating the issue. I'm going to keep further correspondence within the ticket, and I request you do the same so we have all the information in one place. Thanks!
Will do - thanks for responding!
September 17, 2013, 03:38:56 PM
Hey, Tim! I just wanted to let you know that I do see your ticket, and I'm escalating the issue. I'm going to keep further correspondence within the ticket, and I request you do the same so we have all the information in one place. Thanks!
September 17, 2013, 10:14:04 AM
It actually looks like the payments received are not forwarded to our main wallet, which is why we aren't seeing them when we login, nor is our callback URL being triggered. Anyone have any guidance on this? Very strange issue that we can't seem to troubleshoot.
September 17, 2013, 09:18:14 AM
We don't want to host the wallet on our servers because of security concerns; further blockchain.info provides a fantastic callback feature where we are securely notified of a payment (in or out). The challenge is the transactions above, blockchain.info is not adding to our wallet (yet), so the callback URL hasn't been triggered.
September 17, 2013, 09:12:19 AM
Use cron jobs to check payments and notifications.
September 17, 2013, 08:50:07 AM
Hey Everyone!
Sorry if this is the wrong place for this; however - I create a ticket with blockchain.info a while ago that was never answered.
Here's your situation - we leverage the blockchain.info APIs for deposits and withdrawals on our site, works great 99% of the time; however - there are a few instances where customers will send bitcoin to their designated receiving address and it doesn't show up on our side for hours, even after it's confirmed. Below are 2 such examples which were generated today.
In this case the user's receiving address is "17FcpJFGAT8NkcKtMsnvpcjnzrMnezGzT1"
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Any and all help is appreciated and will be rewarded with a bounty!
Thanks,
Tim
Sorry if this is the wrong place for this; however - I create a ticket with blockchain.info a while ago that was never answered.
Here's your situation - we leverage the blockchain.info APIs for deposits and withdrawals on our site, works great 99% of the time; however - there are a few instances where customers will send bitcoin to their designated receiving address and it doesn't show up on our side for hours, even after it's confirmed. Below are 2 such examples which were generated today.
In this case the user's receiving address is "17FcpJFGAT8NkcKtMsnvpcjnzrMnezGzT1"
https://blockchain.info/tx/bad177cec74f748b60ee5b1eb49e2bd7811aa1e31e084f61920ad79e234a294c
https://blockchain.info/tx/5997236a51bc51a2f5f5fc803752106460ad9fc93e9af9f90f7a5b57aa9022d9
Any and all help is appreciated and will be rewarded with a bounty!
Thanks,
Tim
Jump to: