|
July 12, 2013, 12:37:11 PM |
|
You are absolutely correct.
The most unpleasant thing with Bitcoins, from Store Developer's point of view, is anonimity. Currently, if customer does not pay, order expires. If he pays less, he gets an e.mail, saying "here is vendor's e.mail, insufficient funds". If he pays more, he gets an e.mail saying "here is your order, but you have paid extra, so here is vendor's e.mail..." I am going to add a more advanced logging system, so you can trace back, who (e.mail) have sent money and for what. However, to make the system bullet-proof, I need to ask your customer for a Bitcoin address for refunds, which is BAD, as he might or might not want to provide it...
My point of view is, the Engine is for tracking down payments and sending info that was ordered ONLY. As for any kind of support - this is between customer and seller. I do not control their money in any way and I am not part of their business.
Example: customer pays, e.mail with reg. code goes to junk folder and is trashed. What can I possibly do? Example: see above, plus the customer is paranoid, he uses an e.mail address he created for this sole purpose, and then he forgets the password, so he can not access it. Now there is NO WAY he can proove the money came from him.
Well, this is the back side of Bitcoin's anonimity.
What would you say, is it a good idea to ask the customer for an id, which is a Bitcoin address, that can be (if the seller agrees) used for refund purposes?
|