I cant directly deposit BTC into my blockchain wallet anymore..anyone have any ideas why. I goes through BITINSTNT but is keep saying INVALID EXCHANGE. any thoughts ?
Because they have removed the cash deposit -> bitcoin address option. None of the owners have chimed in to tell us how long this will be broken (if not forever). |
|
|
|
Any idea on how long until Bitinstant's service straight to bitcoin address will be fixed? Thanks for working hard to resolve all issues.
I really need to know this as well....BTC has been removed as a remote exchange from the API documentation. Does this mean that this feature is not coming back? I really need to know, as this feature went down hours before I was about to launch a project using it combined with the API. |
|
|
|
so the conclusion is that you needed to be posting a mandatory field, d.o.b., yet the error message was too vague.
Actually, no. It does come back with a proper error message saying the format that the DOB must be in once you get to the point where it will accept the data. I haven't yet analyzed it enough to tell the functional differences between my code and the working code, so I don't have a conclusion yet as to what was going wrong. They were incredibly similar. |
|
|
|
I got it working here try this code <!DOCTYPE HTML>
<html>
<head>
<title></title>
</head>
<body>
<?php
$data_string = "{\"pay_method\":\"zipzap\",\"amount\":80.00,\"dest_exchange\":\"btc\",\"dest_account\":\"1FqWCdCdFeok2ifsfYbcFxwiC8pE7h9xhC\",\"notify_email\":\"test@example.com\",\"fName\":\"John\",\"lName\":\"Doe\", \"dob\":\"1985-01-01\"}";
$ch = curl_init('https://www.bitinstant.com/api/json/GetQuote');
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST");
curl_setopt($ch, CURLOPT_POSTFIELDS, $data_string);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, array(
'Content-Type: application/json',
'Content-Length: ' . strlen($data_string))
);
$result = curl_exec($ch);
echo $result;
?>
</body>
</html>
and it returns {"NotifyEmail": "test@example.com", "ReferID": "None", "FirstName": "Doe", "DestExchange": "btc", "PayMethod": "zipzap", "LastName": "1985-01-01", "ZipZapCustomerLang": "en", "ExchangeName": "Bitcoin Address", "ZipZapCustomerCountry": "John", "ZipZapMerchantOrderID": "7c3c13a8-fbfa-49db-9e4d-a181343aec87", "DestAccount": "1FqWCdCdFeok2ifsfYbcFxwiC8pE7h9xhC", "eventtype": "Quote for new transaction", "ExpectedMaxDeliveryTime": "240.0", "ZipZapMerchantCustomerID": "3610", "OurRate": "3.99%%", "SneakPreviewUser": "129.49.21.91", "AmountPaidByClientUSD": "80.0", "expires": "1360823739.58", "GuaranteedDeliveryTime": "3600.0", "EventID": "ac10fa24-daaf-461f-9b70-1b8737be95af", "QuoteID": "ece8fa32-724b-4145-bfa4-fbeaa3592e83", "AmountCreditedToClientAccountUSD": "76.808", "dob": "", "EventSentAt": "1360820139.58", "ZipZapPassthru": "ece8fa32-724b-4145-bfa4-fbeaa3592e83"}
I just realized the same thing. Thank you so much for the help! BitInstant, for the love of god, fix your docs. |
|
|
|
|
Seems to be working now...will post sample code based on the help in this thread in a few minutes. Thanks guys!
|
|
|
|
Did you make sure to set the header as "application/json" for the content type? Also make sure your not sending it as a post parameter but your actually write it to the url
I am using application/json but could you clarify what you mean by "make sure your not sending it as a post parameter but your actually write it to the url"? Thanks for the help. So instead of sending an array you send the data like curl_setopt($ch, CURLOPT_POSTFIELDS,"{\"pay_method\":\"zipzap\",\"amount\":80.00,\"dest_exchange\":\"btc\",\"dest_account\":\"1FqWCdCdFeok2ifsfYbcFxwiC8pE7h9xhC\",\"notify_email\":\"test@example.com\"}");
Yes then, it appears that I'm sending it correctly. It just doesn't work. |
|
|
|
Did you make sure to set the header as "application/json" for the content type? Also make sure your not sending it as a post parameter but your actually write it to the url
I am using application/json but could you clarify what you mean by "make sure your not sending it as a post parameter but your actually write it to the url"? Thanks for the help. |
|
|
|
what do you mean by "post body" ?
how are you encoding it?
are you using curl?
I've tried it in the above format with both cURL and in a Delphi program. Doesn't matter, same result. You would think they would ask for a named Post field, like "jsondata={json stuff}" but the documentation disputes that and doesn't list any field name. |
|
|
|
Why is your amount a string it should be {"pay_method":"zipzap","amount":80,"dest_exchange":"btc","dest_account":"1FqWCdCdFeok2ifsfYbcFxwiC8pE7h9xhC","notify_email":"test@example.com"}
Forgot to mention that. I've tried it both ways, and it doesn't matter. Returns the same error message. I was grasping at straws when I did that. |
|
|
|
I started building a php wrapper a while ago but the documentation was so confusing I abandoned it. Let me know what calls you are looking to make and I'll see if I can dig it up.
The documentation is atrocious, and if anyone is successfully using their API and can answer my question, I'd be forever grateful. Blockchain.info's implementation of the Bitinstant API (the "Deposit With Cash" function) has been broken for 3 days, which is probably a bad sign. To get a quote, we're supposed to send along the user's birthday, and the documentation says "User's birthday in the following format:" and ends there. The format isn't specified. I could probably guess the proper format if the server would accept anything at all, but unfortunately I can't get that far. When I send a properly-encoded JSON request to: https://www.bitinstant.com/api/json/GetQuote/ (to get a quote) With a post body of: {"pay_method":"zipzap","amount":80,"dest_exchange":"btc","dest_account":"1FqWCdCdFeok2ifsfYbcFxwiC8pE7h9xhC","notify_email":" test@example.com"} It returns: {"error": "Update your code - pass parameters as the POST body, JSON encoded"} No matter what you do. Can anyone shed any light on this? |
|
|
|
Important Update: - Overnight ACH (not to be confused with normal ACH) will be discontinued. The last day to request payout by Overnight ACH will be 1/17. After 6PM EST on 1/17 the overnight ACH option will be removed from the sell page. At this time Bank Of America was our only provider of Overnight ACH services. None of our other banking partners currently offer this service and we are unsure if we will be able to offer it in the future.
Overnight ACH is still an option on the sell pages. Did you find another provider for this, or was it mistakenly left on as an option? |
|
|
|
|
Since no one's participating, it's closed.
|
|
|
|
Hey, I don't understand where the confusion is here.
Select Bitcoin Address, enter the address on our website and wait for the coins. Why is that hard to understand?
I'm not trying to be harsh, I just feel like a quick $20 test is faster then even creating this thread.
Did you actually do a test before posting here?
1- Create Slip
2- Hand cash to teller
3- Check your bitcoin wallet
While you are correct that a $20 test would have cleared up the confusion, a much easier and customer friendly solution would be to change the text on your own site to be accurate for the method chosen. The confusion stemmed from the fact that when someone starts the Cash Deposit -> Bitcoin Address function, at the very top of the next page, you place the following statement: Within 60 minutes of your payment, an equivalent amount of Bitcoin will be purchased at the current market price, automatically. These coins will then be sent to you via our partner, Coinapult.com. The email will come from Coinapult with instructions on how to send your coins wherever you'd like.
The bold part is apparently entirely inaccurate according to your response here. Your own page explicitly states that there is an extra step after the money is sent, but thankfully, there is not. I would suggest changing or removing that language when sending to a Bitcoin address. Something like: Within 60 minutes of your payment, an equivalent amount of Bitcoin will be purchased at the current market price, automatically. These coins will then be sent to the Bitcoin address you specified automatically via our partner, Coinapult.com.
Interestingly, Coinapult.com actually replied to my support request, and they told me that the extra step of receiving the email, going to their site, and then sending the coins out to the address would be required. So apparently I'm not the only one that is confused. |
|
|
|
You wouldn't happened to be in Macau this week?  Us BitInstant guys are in HK and Macau this week... if any Bitcoiners wanna meet up for coffee or drinks or similar, send me an email (erik@bitinstant)
No, but if it would get my question answered, I'd happily fly to Macau  . Maybe play some baccarat too lol. |
|
|
|
|
Well, if anyone can shed any light on this, I'd appreciate it. I am holding up development of a software sales module I'm writing until I can find out if the bitcoins will go straight to an address after the Moneygram is sent or not. Users won't necessarily have the email address of the developer to send it to, so if it's not possible that will kill my idea. I began development just assuming that Bitinstant's own site was offering services they could actually deliver, which now appears not to be the case. I've submitted this question to both Bitinstant and Coinapult customer support and have received no response.
|
|
|
|
|
OK, so their confirmation page was basically just wrong then when it says that Coinapult.com is involved?
|
|
|
|
|
OK, so once you entered the order details, got the info to put on the moneygram form, and sent the Moneygram, you didn't have to do anything else? You didn't have to do anything via Coinapult.com? That's the only thing that concerns me....the steps after the money is sent to Bitinstant. Their confirmation page says you have to do something with Coinapult.com.
|
|
|
|
|
Hi Guys,
I was playing with BitInstant and wanted to test a Cash Deposit to Bitcoin Address transaction. Unfortunately, on the confirmation screen it says:
"These coins will then be sent to you via our partner, Coinapult.com. The email will come from Coinapult with instructions on how to send your coins wherever you'd like."
The problem is that Coinapult doesn't offer an option for sending straight to a bitcoin address. Why does Bitinstant bother even saying that they can send to a bitcoin address when they can't? I realize that the purchaser can take delivery of the coins via email, then use the bitcoin software or a wallet service to send them from there, but that is a significant additional step that I don't want customers to have to take. Does anyone have experience with this? Maybe the page is just making a general statement about other types of transactions they do, and the coins will automatically go to a bitcoin address?
|
|
|
|
Fair warning, running the QT client begins to get sluggish after about 15k addresses, and is nearly unusable after 120k or so.
I haven't noticed any sluggishness with the newest version of the QT client, and I now have a wallet with 50K addresses in it. Also the wallet is only around 7MB. The real problem with the official client is the amount of time it takes to sync after install. That by itself will hamper the adoption of bitcoin by the general population. Although alternatives are available that make the use of the official software unnecessary, a casual user that goes to the bitcoin main site and downloads the software will be immediately turned off and may not bother or even understand that alternatives are available. |
|
|
|
for i in `seq 1 5000`; do bitcoind getnewaddress; done >addresses.txt That command will generate 5000 addresses on your wallet using bitcoind(no import needed) and save the addresses to a text file. Change 5000 to any other number you like. Sorry to bump an old thread, but just thought I'd post a step-by-step equivalent for Windows, since I had a need for it recently. 1) Open a command prompt, go to the bitcoind directory (your bitcoin directory\daemon) 2) Type "bitcoind -daemon". Keep this window open for as long as the batch below is running. 3) Open another command prompt. Navigate to the bitcoind directory again. Enter the code below at the prompt and press enter: for /l %x in (1, 1, 5000) do bitcoind getnewaddress >> newaddrs.txt If you want to put the above code in a batch file, use 2 '%' symbols in front of the x instead of 1. Replace the 5000 in the code above with the number of addresses you'd like to generate. All addresses created will be dumped to newaddrs.txt, and bitcoind happily stores them in your official client wallet automatically. Theoretically you can enter that same command above in multiple command prompts simultaneously and generate new addresses faster. |
|
|
|
|
Show Posts
