Hello Merlin,
For US consumers anyway, the merchant's bank has no control over it.
The "chargeback" policies are set by the consumer's bank who issued
the card, and your merchant bank has no influence or effect on that.
Thursday, December 07, 2000, 4:47:59 PM, you wrote:
>> You left out the fourth step!
>>
>> 4. The client receives their credit card statement, claims not to have
>> authorized the charge, and the credit card company charges it back to you.
>> You provide documentation to the credit card company, but the credit card
>> company doesn't know what a domain name is, and since you have so signature
>> they rule against you.
> not a problem here, because I'm using an eCommerce interface specifically set up by
>the Bank+eSecure (the security company), that
> doesn't require a signature because it is specifically designed for online commerce,
>so in the rare event that a charge is
> contested, they actually sort it out, and not me.
> The mechanics of the online transaction generates a really solid paper trail with
>the bank and the eCommerce company, so it's nearly
> impossible for the customer to "forget" they made the purchase. The excuse doesn't
>wash in other words.
> If the 'forgetful' customer is actually insisting that they didn't buy the domain -
>then it's just too bad. They now own it and can
> just let it expire or sell it or do what ever they like with it.
> Either way, I'm not out of pocket because the eCommerce company guarentees the
>transaction. (their fees are enough to cover it
> anyway :-) )
> ---
> Robert Chalmers
> http://www.quantum-radio.net.au Quantum Radio
>[EMAIL PROTECTED]
> http://www.inexpensivewebsites.com Domain Name Registrations
>[EMAIL PROTECTED]
--
Best regards,
William mailto:[EMAIL PROTECTED]
