wal said:



1) use electrum client however this isnt working on testnet so for testing builds is a problem

2) use dash-qt.exe client however need a way to get private keys from payment processor and import into dash-qt ? (if yes is there any docs on how to do this?)



With the payment processor (or dash in general) is it possible to credit someone ? e.g. programatically pay someone in the case of say a store credit that needs to be refunded.



Cheers again > Due to this fact (and due to the fact that Dash Core v0.12.1.x doesn't support BIP32 address generation) there's unfortunately not a good way to set this up to point to a Dash Core wallet address. @snogcel thanks for confirming this. What do you suggest is the best way to view (say as a business owner) the transactions credited to the payment processor? The options I see at the moment are1) use electrum client however this isnt working on testnet so for testing builds is a problem2) use dash-qt.exe client however need a way to get private keys from payment processor and import into dash-qt ? (if yes is there any docs on how to do this?)With the payment processor (or dash in general) is it possible to credit someone ? e.g. programatically pay someone in the case of say a store credit that needs to be refunded.Cheers again Click to expand...

Hey Wal,Thanks for looking at this angle of the processor. In my eyes there's a couple ways to accomplish the type of oversight you're speaking of - it's definitely an important requirement.1.. Larger clients would probably prefer this type of system as it could be set up to connect to a pre-existing platform (or maybe even just dumped into CSV?). The drawback for this is the development effort required and also that clear requirements for this type of functionality is yet to be defined. I started building this out, considered removing it, but left it commented as a development resource: https://github.com/snogcel/dash-payment-processor/blob/master/lib/index.js#L173 2.. This is the simpler way to go for sure and probably the most practical in the short-term. While developing this I was using a BIP32 public key from Copay-Dash (see https://copay.io/ ) if only to sanity-check payment receipt. Electrum-Dash is certainly an option as well however as you'd noticed right now we're not seeing the transactions go through (I think this is temporary - due to load testing the past week or so). A few minutes ago I finished up an preliminary build of Copay-Dash as a chrome app. Once testnet has settled down a little bit I plan to make this publicly accessible and I think it will solve this problem you're facing.As for your other question: in it's current incarnation, no, the Payment Processor does not have the ability to create/sign transactions on behalf of the store owner and as a result wouldn't be able to initiate a refund. These types of functions will be possible with Dash Evolution, but we're not quite there yet