<p>In case anyone else faces this decision I decided to go with the Blockchain.info API (<a href="https://blockchain.info/" rel="nofollow">https://blockchain.info/</a>).</p>

<p>Primary factors:</p>

<ul>
<li>Easy to use ruby gem and interface - I was able to create wallets and transactions through invoking a few simple methods within my Sinatra app</li>
<li>Blockchain.info provide and utilise a stable wallet, recipient address which is easier and more intuitive to work with when starting out (e.g. easy to track senders and recipients against IDs)</li>
</ul>

<p>Drawbacks:</p>

<ul>
<li>I couldn't find a way to link in the Testnet blockchain so had to experiment with real Bitcoins</li>
<li>I was totally reliant on the Blockchain.info wallet and transaction structure. This was fine for a prototype/ experiment but for an actual MVP you would want to be able to integrate a wide range of wallet providers.</li>
</ul>

CC BY-SA 3.0
2015-06-07T09:40:04.560Z
2015-06-07T09:40:04.560Z
AlexHandy1
<p>Take a look at Coinkite's API <a href="https://coinkite.com/developers" rel="nofollow">https://coinkite.com/developers</a> and also the payment buttons and payment processing options <a href="https://coinkite.com/faq/pay" rel="nofollow">https://coinkite.com/faq/pay</a></p>

CC BY-SA 3.0
2015-07-07T20:51:35.190Z
You need to state your affiliation with CoinKite if you are going to post commercial messages like this. It may be a valid solution, but you are not being forthcoming regarding that you are an employee of that company.
Claris
CC BY-SA 3.0
2015-07-07T17:54:22.667Z
2015-07-07T17:54:22.667Z
nvk
<p>My question relates to the use case of trying to build a simple payment flow where one user (a donor) can donate directly to another user (a recipient) with Bitcoin.
To begin with, I would like to manually load up and input 2 addresses that respond to a Donate button and ideally get processed from test accounts on the Testnet blockchain.</p>

<p>I am new to bitcoin development and want to understand the underlying mechanics rather than immediately implementing a more sophisticated and abstracted plugin (e.g. Stripe).
Additionally, my preferred language is Ruby so I have been favouring APIs with Ruby SDKs.</p>

<p>So far I have a shortlist of the following APIs: </p>

<ul>
<li>Chain.com (<a href="https://chain.com/docs/ruby#bitcoin-transaction-overview" rel="nofollow">https://chain.com/docs/ruby#bitcoin-transaction-overview</a>) </li>
<li>Blockcypher (<a href="http://dev.blockcypher.com/#payments" rel="nofollow">http://dev.blockcypher.com/#payments</a>) >> provide direct access to Testnet, not clear how would implement with others</li>
<li>Blockchain.info (can't link with current rep points) >> may force you to use their wallets</li>
</ul>

<p>Has anyone worked with these and can provide guidance on which is best to implement the above use case? Other suggestions welcome. Appreciate this could be interpreted fairly broadly but I can try and specify further if you have questions. </p>

<transactions><api>
Setting up a basic test transaction for p2p donation web app - API recommendation
AlexHandy1
# Setting up a basic test transaction for p2p donation web app - API recommendation

(Asked by: username_0 on 2015-06-01)

My question relates to the use case of trying to build a simple payment flow where one user (a donor) can donate directly to another user (a recipient) with Bitcoin.
To begin with, I would like to manually load up and input 2 addresses that respond to a Donate button and ideally get processed from test accounts on the Testnet blockchain.

I am new to bitcoin development and want to understand the underlying mechanics rather than immediately implementing a more sophisticated and abstracted plugin (e.g. Stripe).
Additionally, my preferred language is Ruby so I have been favouring APIs with Ruby SDKs.

So far I have a shortlist of the following APIs:

* Chain.com (<https://chain.com/docs/ruby#bitcoin-transaction-overview>)
* Blockcypher (<http://dev.blockcypher.com/#payments>) >> provide direct access to Testnet, not clear how would implement with others
* Blockchain.info (can't link with current rep points) >> may force you to use their wallets

Has anyone worked with these and can provide guidance on which is best to implement the above use case? Other suggestions welcome. Appreciate this could be interpreted fairly broadly but I can try and specify further if you have questions.

**Tags:** transactions, api


---

## 2 answers

### Answer by username_0 on 2015-06-07. Score: 0 | Accepted answer

In case anyone else faces this decision I decided to go with the Blockchain.info API (<https://blockchain.info/>).

Primary factors:

* Easy to use ruby gem and interface - I was able to create wallets and transactions through invoking a few simple methods within my Sinatra app
* Blockchain.info provide and utilise a stable wallet, recipient address which is easier and more intuitive to work with when starting out (e.g. easy to track senders and recipients against IDs)

Drawbacks:

* I couldn't find a way to link in the Testnet blockchain so had to experiment with real Bitcoins
* I was totally reliant on the Blockchain.info wallet and transaction structure. This was fine for a prototype/ experiment but for an actual MVP you would want to be able to integrate a wide range of wallet providers.


---

### Answer by username_1 on 2015-07-07. Score: 0

Take a look at Coinkite's API <https://coinkite.com/developers> and also the payment buttons and payment processing options <https://coinkite.com/faq/pay>

> **Comments:**
> **username_2**: You need to state your affiliation with CoinKite if you are going to post commercial messages like this. It may be a valid solution, but you are not being forthcoming regarding that you are an employee of that company.  

---

