Compare the Dwolla Morass (DBA, etc) To The Instant Solution!

(I win! Grin

)

I found the link to your Easy Pay Widget:

https://coin.mx/merchant/generate_url

Kudos! That can almost entirely meet my needs! That is exactly what I was asking for except one feature appears to be lacking.

Although I can sniff the receipt of the BTC at the specified address over the Bitcoin network (or even wait for 1-confirmation on the block chain), I am unable with your current API to get any feedback that a customer has initiated an yet unverified (or partially verified) transaction with you.

My understanding is that your full verification process can cause a delay ranging from minutes to days.

Some merchants offer intangible goods which have basically no cost and even some merchants are offering for example a 30 day subscription to the paid members only area of a web site. Such merchants often prefer to give immediate access to the customer who has completed the basic instant verification you do for credit cards (e.g. your AVS and geolocation checks, etc). The merchant can rescind the subscription if final payment is never received within some maximum window of time (4 days?).

This is about making the experience more pleasant for the good customers. If we make it too frustratingly slow, good customers form bad opinions and we lose good will. Customer attrition rate is very important to business models.

I understand you don't want to encourage fraud if merchants give customers immediate access after only the instant verification of credit cards, so merchants need to be careful to give only a very limited access while waiting for final payment. OTOH, you all have to do the slower, more extensive verification procedures any way for each transaction. And I am sure I understand that your profit comes from good repeat customers and from the free referrals you get from bonafide merchants who introduce new customers to this paradigm.

So on balance, I think it would be net win-win for both you and the merchants if you add the "callback on initial verification" feature I am suggesting.

I eagerly await your feedback and thoughts. We want to work with you to meet mutual synergies.

Sincerely,
iamback

P.S. If ever the card companies accuse you of reselling in violation of any merchant agreement you may have with them, please consider removing the "merchant name" and "product" fields from you API. It is impossible for you to verify if the BTC address you are loading belongs to the customer or a merchant thus it can not be proven you are "reselling". Perhaps this is not a problem for your relationship with the credit card companies; I am just thinking in advance on your behalf. I am very happy you offer this service and I want to help you succeed.

> ##- Please type your reply above this line -##
>
> [Coin.Mx] Re: Simplified proposal to add a merchant service
>
> Your request (28297) has been updated. To add additional comments, reply
> to this email.
> ----------------------------------------------
>
> Coin.MX, Feb 26, 3:44 PM
>
> Hi iamback,
>
> Have you seen our easy pay widget?
>
> Here is a quick tutorial on how it works.
>
> Is this something that would work for your purposes?
>
> Let me know if you have any questions,
> Jen
>
> ----------------------------------------------
>
> iamback, Feb 25, 1:55 PM
>
> I would like to have the customer pay me in BTC using their credit card. I
> can use the following capability to generate unique BTC addresses for each
> customer:
>
> https://blockchain.info/api/api_receive
>
> But I would prefer to have more seamless integration into your website,
> where I can direct the customer to a page on your website where the BTC
> address is automatically entered, and also supply a return URL that you
> send the customer to after receiving all the information you need from the
> customer.
>
> --------------------------------
> This email is a service from Coin.Mx.
>
>
>
>
>
>
>
>
>
> [F0B2-0JRR]