Msg#: 3952107 posted 9:21 am on Jul 14, 2009 (gmt 0)
In order to reduce support costs and also increase customer retention what are the acceptable ways of validating cards online when integrated with a payment processor. Some of them could be like;
1. to do a “$0” transaction, which is interpreted as an authorization request and won’t appear on the customer’s bill, or need to be reverted 2. another is to use a specific API to validate the credit card 3. the last one is to revert/cancel the $1 authorization after it has been done. This may not be the best solution because it might end up showing on buyer monthly statement which merchant has no control over.
What are the other possible ways? What if the integrated payment processor does not offer better ways of validating? Is there anything a merchant can do?
Thanks much for sharing your thoughts and any experiences.
Msg#: 3952107 posted 11:02 am on Jul 14, 2009 (gmt 0)
Another way is to validate where the customer comes from. For instance his IP could be used to verify certain things, say if you see someone behind a proxy placing an order it may imply foul play. Or if the IP belongs to country A but he ships to country B could be a red flag in which case you don't even need to worry about the payment processor.
Msg#: 3952107 posted 5:56 am on Jul 15, 2009 (gmt 0)
enigma1 - thanks. Your suggestion is more of doing some validation by the merchant without having to do any handshake with the payment processor. But I was looking for ways to do validation with an handshake to payment processor.