<p>The <a href="https://block.io/api/simple/php" rel="nofollow noreferrer">Block.io</a> api supports accounts for similar usage.</p>
<blockquote>
<p>With Block.io, you can create wallet addresses for users inside your games, auction sites, stores, etc.</p>
<p>To create a user's wallet on your account, create addresses for them using get_new_address. You should specify a sequence of labels for that user. For instance, if we wish to create a number of addresses for User A, we'd want to call get_new_address with label=userAx{address_number} as many times as wish to create a new address for User A.</p>
<p>Once we have addresses for User A, we can query balances for their addresses, and send coins on the user's behalf.</p>
</blockquote>

CC BY-SA 3.0
2014-10-14T00:46:18.197Z
2014-10-14T00:46:18.197Z
2020-06-16T11:10:03.350Z
siliconsys
<p>I'm building out a pet project webapp called CollaboTree, a big part of it is allowing users to set bounties for completing/collaborating on little bits of work. I'd like these micro payments to be as cheap/free as possible, and fast (instant?) would be good.</p>

<p>Would it make sense to:</p>

<ul>
<li><p>Make a wallet for every user on signup, and make all internal payments go onto the blockchain between real wallets</p></li>
<li><p>allow users to load/unload bitcoin onto their accounts to some kind of shared wallet which only the app has access to, then maintain a balance for each user in database letting them transfer among themselves instantly outside of the blockchain, then letting them get their coins back 'live' when needed</p></li>
<li><p>Have one big wallet for the entire app, with each user having their own address which is the only one they can spend from or something?</p></li>
</ul>

<development><website-integration><user-data><micropayments>
How to best structure Internal bitcoin payments within a webapp?
dangerous.beans
# How to best structure Internal bitcoin payments within a webapp?

(Asked by: username_0 on 2014-09-13)

I'm building out a pet project webapp called CollaboTree, a big part of it is allowing users to set bounties for completing/collaborating on little bits of work. I'd like these micro payments to be as cheap/free as possible, and fast (instant?) would be good.

Would it make sense to:

* Make a wallet for every user on signup, and make all internal payments go onto the blockchain between real wallets
* allow users to load/unload bitcoin onto their accounts to some kind of shared wallet which only the app has access to, then maintain a balance for each user in database letting them transfer among themselves instantly outside of the blockchain, then letting them get their coins back 'live' when needed
* Have one big wallet for the entire app, with each user having their own address which is the only one they can spend from or something?

**Tags:** development, website-integration, user-data, micropayments


---

## 1 answers

### Answer by username_1 on 2014-10-14. Score: 1

The [Block.io](https://block.io/api/simple/php) api supports accounts for similar usage.

> With Block.io, you can create wallet addresses for users inside your games, auction sites, stores, etc.
>
> To create a user's wallet on your account, create addresses for them using get\_new\_address. You should specify a sequence of labels for that user. For instance, if we wish to create a number of addresses for User A, we'd want to call get\_new\_address with label=userAx{address\_number} as many times as wish to create a new address for User A.
>
> Once we have addresses for User A, we can query balances for their addresses, and send coins on the user's behalf.


---

