Jump to content
DenariusTalk

Recommended Posts

Introducing: CryptoPayAPI

So a thought occurred to me the other day when I was looking at the wallet daydreaming about all the uses of cryptocurrencies when I realize that apps and games on platforms such as Google Play could accept them as credits instead of USD or other government currencies. Such as in Life of Jaxon to buy level packs, instead of using Google's in-app purchases API we could write one for DNR. It would not be too hard to do. Just ask the users to send coins to an address and set the note as a key, then ask for the TX ID. If I'm missing anything here let me know! I think this could be an excellent way to boost the use of DNR.

Current Release: Alpha 2
GitHub Linkhttps://github.com/Roxas240/CryptoPayAPI

Edited by Jaxon
Fancy Looks
  • Like 2

Share this post


Link to post
Share on other sites

Change Log:

Version 0.0.2: Alpha 2

  • The server now has a UI to monitor transactions
  • The node_config.prop files has all startup parameters
  • The server now updates the database with confirmation count
  • The code is now more organized and complete
  • The server and example code have been separated.

Version 0.0.1: Alpha 1

  • The first release, the server can be run on any platform with apache2, MySQL, and Java capabilities.
  • Payments can be requested using any language that supports POST requests.

If you guys have any suggestions for the API, or simply just comments please post them below.

Edited by Jaxon
  • Like 1

Share this post


Link to post
Share on other sites

Progress Update: 08-18-2017

Thanks to @Carsen, @buzzkillb and @KawaiiCrypto, I have been able to test transactions being performed and received for purchases. As it stands, the code can look for payments that are listed with a note as a sort of key, enabling verified but not tracked transfers. The GitHub repo posted in the second reply has gotten a new commit. Next step tomorrow is to make a demo app and add the PHP script filter between the wallet and the application. The API is making progress guys! I'm excited for what is gonna come!

  • Like 4

Share this post


Link to post
Share on other sites
On 8/18/2017 at 8:15 AM, Jaxon said:

Progress Update: 08-18-2017

Thanks to @Carsen, @buzzkillb and @KawaiiCrypto, I have been able to test transactions being performed and received for purchases. As it stands, the code can look for payments that are listed with a note as a sort of key, enabling verified but not tracked transfers. The GitHub repo posted in the second reply has gotten a new commit. Next step tomorrow is to make a demo app and add the PHP script filter between the wallet and the application. The API is making progress guys! I'm excited for what is gonna come!

Good stuff mate :) will probs use this for when DenariusOnline comes in to play ;)

Share this post


Link to post
Share on other sites

Finally, an Alpha release has been published to GitHub. Setup to use this may be a bit technical, but very low maintenance is required. Of course, I would love some feed back on how to make this better, it is in alpha after all. Link here: https://github.com/Roxas240/CryptoInApp/releases/tag/v0.0.1

How to run:
===========

1.) Edit both the run.bat (Windows) or run.sh (Linux) and the node_config.prop
    where ever you see text between < >
    
2.) Edit the setup.php file with the configuration that works with your Http
    and SQL server. Once you are done, move the setup.php and index.php to
    your web document root (htdocs for apache2).
    
3.) Open up setup.php in your web browser and fill in all the info that shows
    up. On the last step, it will tell you all the info you need to create an
    app with the CryptoPayAPI and what info to update index.php with.
    
4.) After filling out all the info in index.php, get to work! There is a sample
    application included in this library's source under the example package.
    Modify that source to your own or start from scratch. Either way, enjoy.
    
PS.) It is possible to link CryptoPayAPI with any application that supports
     POST requests. Hint: look at the source of the Client Side API, located
     in the client package.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×