Author

Topic: API wallet bitcoin (Read 807 times)

member
Activity: 148
Merit: 45
https://bitaps.com/
November 07, 2016, 12:02:10 PM
#4
Hello everybody !

As part of the realization of an MVP, I have two main questions regarding the use of the API of a bitcoin wallet (for example that of taking blockchain.info).
]

I can propose to use https://bitaps.com/api/
It's free, easy and convenient RESTful API. No registration. No limits. No restrictions.
newbie
Activity: 9
Merit: 0
October 11, 2016, 11:43:09 AM
#3
Don't use a service, you'll regret it, especially for a realtime customer driven application like what you're building. The 3rd party services can go offline or subject to denial of service attack. You're better off running a couple of bitcoin nodes on your backend servers or on amazon/azure.

You don't really need to code a wallet application, just make API/RPC calls to a wallet/node.
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

Let customers run their own mobile wallet, you'd be asking for trouble in creating your own wallet for mobile devices.

Security is huge too, I have an earlier post on securing back end services and code.

thank you @cloverme

Technically you describe what could be my product.

In the specifications I would especially need the API/RPC call to a wallet/node is done in a graphical interface to our brand.
(If I'm not mistaken this is technically feasible ?)

In parallel I allow myself to send you a message.

legendary
Activity: 1512
Merit: 1057
SpacePirate.io
October 10, 2016, 12:21:55 PM
#2
Don't use a service, you'll regret it, especially for a realtime customer driven application like what you're building. The 3rd party services can go offline or subject to denial of service attack. You're better off running a couple of bitcoin nodes on your backend servers or on amazon/azure.

You don't really need to code a wallet application, just make API/RPC calls to a wallet/node.
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

Let customers run their own mobile wallet, you'd be asking for trouble in creating your own wallet for mobile devices.

Security is huge too, I have an earlier post on securing back end services and code.
newbie
Activity: 9
Merit: 0
October 10, 2016, 09:38:39 AM
#1
Hello everybody !

As part of the realization of an MVP, I have two main questions regarding the use of the API of a bitcoin wallet (for example that of taking blockchain.info).

The MVP is for testing a mobile payment concept.
It will be implemented and its restricted only in a fast food outlet.
Technically, the merchant will have a tablet and a application installed previously.
And customers will have a mobile app to download.

Feed Specifications :
Both applications (customer and merchant) will be able to send and receive payments between them.
No applications will have the ability to make withdrawals and convert bitcoins in €.


Specifications of the actors :
The merchnat application is intended for a single trader.
The client application is provided for a maximum number of 1500 customers.
Only the address of the trader and the respective addresses of 1500 customers can interact, an unknown address and therefore another bitcoin wallet can interact with any of the two applications.

Network Requirements :
Since we operate in a closed circuit in order not to be affected by price fluctuations, we do wish to establish a price fixed in advance in the network.
The minimal costs of remuneration of minors will be at our expense.


My questions :

1) Is it possible to create a bitcoin wallet white label from this API while respecting the specification mentioned?
The reason is commercial: we will not pass on the use of blockchain protocol in our product.
Then financial: I think that the development cost can be significantly more interesting compared to a solution built from scratch.

2) In your opinion what are the APIs and web services that best fit?
For web services I particularly refers to startups like www.blockcypher.com
To complete this question I possibly specifications available.

Best regards,
Jump to: