ultra-simple-dash-merchant (PHP)

[jimbursch]

I will port this project that was listed here: https://www.dash.org/forum/threads/call-for-devs-software-adoption.2195/

ultra-simple-bitcoin-merchant (PHP) - to be ported
https://github.com/zooitje/ultra-simple-bitcoin-merchant

The bitcoin version called for a Mt. Gox account to use for sending bitcoin. Obviously that won't work for Dash, and because there isn't a web wallet API available for dash, I think this will just be able to receive dash, and not send.

 

[jimbursch]

Here's the github repository:
https://github.com/jimbursch/ultra-simple-Dash-merchant

 

[jimbursch]

Because I hate javascript I will be stripping out all the javascript, and because I don't think anyone else will be using this (this is really just an exercise for me) I will be taking out the language localization.

I will replace the Mt. Gox API with a combination of the official Dash Explorer API (https://explorer.dash.org) and the CoinMarketCap API for price ticker (https://coinmarketcap.com/api/).

 

[jimbursch]

Well, upon review, I think I will be using the cryptoID API (https://chainz.cryptoid.info/api.dws) instead of the "official" dash explorer API, which is limited in its capability.

BTW, of the other explorers listed here, https://www.dash.org/blockchain-explorers/, only cryptoID appears to be working correctly.

 

[jimbursch]

Now I've decided to shitcan ultra-simple-bitcoin-merchant altogether and do a very-simple-dash-invoicing system instead. Should take me about a week to have a working prototype.

 

[jimbursch]

Here's a description of how it will work:

To create a very simple Dash invoice:

- mannually enter a Dash address that has never received funds
- optionally enter:
-- issuer(merchant) name
-- customer name/id
-- invoice id (from issuer's accounting system)
-- product name/id
-- amount

When submitted, a url is generated that passes all variables to invoice page (get), including a hash of the invoice to check authenticity.

When a customer views the invoice, the invoice hash is checked for authenticity and the Dash address is queried for received funds. The Dash address is displayed with a QR code and instructions for payment, along with the optional invoice data.

If the Dash address has received funds equal to or greater than the amount of the invoice, the invoice is marked paid.

To check the status of payment, simply reload the invoice page.

 

[jimbursch]

OK - this project is now underway:

live prototype:
http://jimbursch.com/simple-dash-invoice/

on GitHub:
https://github.com/jimbursch/simple-dash-invoice

Keep in mind, this is a work-in-progress.

 

[GrandMasterDash]

"Amount" should probably say ""Amount (DASH)".

Also, if it were me, I would also prefix the QR string with "dash:" because, in theory, that should trigger a wallet action, in the same way "bitcoin:1xxxxx" triggers a bitcoin wallet.

 

[jimbursch]

"Amount" should probably say ""Amount (DASH)".

Also, if it were me, I would also prefix the QR string with "dash:" because, in theory, that should trigger a wallet action, in the same way "bitcoin:1xxxxx" triggers a bitcoin wallet.

Done!

Would love to get more feedback -- feel free to take a whack at it and get back to me:

Simple Dash Invoice
http://jimbursch.com/simple-dash-invoice/index.php

 

[kodaxx]

Does this support InstantSend?

 

[jimbursch]

No -- this is a simple invoicing app. There is no interaction with a wallet. It enables you to create an invoice tied to a Dash address and monitors that address for payment received.

 

[GrandMasterDash]

If someone used Instant Send, your app would still have to wait for a confirmation, right?

 

[jimbursch]

If someone used Instant Send, your app would still have to wait for a confirmation, right?

That's a good question and I'm not sure about the answer. The app queries 'getreceivedbyaddress', which I would assume requires at least 1 confirmation, but I could be wrong.

 

[GrandMasterDash]

That's a good question and I'm not sure about the answer. The app queries 'getreceivedbyaddress', which I would assume requires at least 1 confirmation, but I could be wrong.

Yeah, I suspect you have to wait for a confirmation. I just took a quick glance at the code and can see you're using CryptoID.info. Might of been different if it was talking directly to a node.

 

[joemoraca]

good learning project - it worked fine for me.