Quote from: xyzabc on November 19, 2016, 02:49:20 PM

Quote from: mexicantarget on November 19, 2016, 02:26:17 PM

Quote

Users on my website are not sent payouts instantly on faucet claim. They accumulate the payout till they at least 1000 satoshi and then upon request payout is instantly sent via Faucetbox.
What would happen if I'm using Faucethub API and a member withdraws his balance but he has not yet created account on Faucethub. Where does the satoshi go? Please add a feature to save this balance to the address even if users has not created account and when the users creates account and link that bitcoin address, the balance shows in his account.

Satoshi go no where and the API responds with a code which isn't 200

I second Ahmed on this.

I have a android game where user accumulated Satoshis and I want to send them to their FaucetBox/FaucetHub account , using API.
So that users can anytime check their balance using the address checker on the website.

It would be really troublesome redirecting people from my android app to Faucethub registration and explaining them whole thing.
With making it necessary to register on FaucetHub, I need my users to register for a wallet provider (XAPO, COINBASE etc.) Then to FaucetHub , then to my game/app . I can already imagine how troublesome it becomes for those who may be new to the Bitcoin world.

With this necessity to register I believe the scope of FaucetHub would get limited only to faucets, instead of becoming a micro payment service which can be used well beyond faucet and faucet scripts. If it is only for security maybe you can give faucet owners an option to have this.

May be you can give second thoughts to this feature , although I totally understand this is your decision finally.

I'm limiting this myself and I'm aware of it. I want to keep this a microwallet for sites I run and other admin sites who might find what I provide useful.

I'm just a guy, running way too many projects to expand faucethub into a giant microwallet site (for now)

Although, I could save you from the trouble and have a "how to register" or whatever page needed, so all users can understand how to use the service completely.

Those aren't my final words. I could expland faucethub to something much bigger if needed, but I don't see the need to do it on launch Sad

I already bit more than I can chew.

Also, I could do some exceptions to apps, but I couldn't guarantee security if your users don't secure themselves