Page 1 of 1

Add a New Payment function

Posted: Mon Jan 19, 2009 1:36 pm
by WylieE
We must be missing something simple here. (But it escapes us!)

We're ready to go live with our site and have plans to switch over tomorrow. Warmoth is using USAePay as our payment company and have been processing test orders through their test sandbox. We thought everything was going smoothly so we're proceeding to the rollout. (It looks like the test sandbox was not validating CVV2 numbers.)

We switched over to the live USAePay processing site and ran a few test orders and the initial payment and adjustments to that payment work fine. However, when we try to add a payment, it fails because we have not passed the CVV2 code. Of course, we cannot store this. (We regularly add payments for international shipping and need to do this.)

So... we're scratching our heads here. How can we add a payment if we cannot store and send the CVV2 code? I'm presuming there are more than a few AC'ers out here that can add additional payments. What are you doing??

Thanks,

Re: Add a New Payment function

Posted: Mon Jan 19, 2009 1:46 pm
by jmestep
We had the SecurityCode set as required in Authnet, then if we ran a payment manually, we just put in a fake one. Unless you want to call the customer and get the code.

Re: Add a New Payment function

Posted: Mon Jan 19, 2009 4:31 pm
by WylieE
jmestep wrote:We had the SecurityCode set as required in Authnet, then if we ran a payment manually, we just put in a fake one. Unless you want to call the customer and get the code.
Given the number of international orders we receive, calling each one would not be feasible or efficient.

Since we're not using Authnet for processing, I'm not familiar with their setup. Can you elaborate a bit on how you handle the CVV2 number during initial order processing and additional (manual) payments?

Thanks,

Re: Add a New Payment function

Posted: Mon Jan 19, 2009 4:39 pm
by jmestep
We had the autorizenet gateway set up to require the security code, and decline the charge if it was wrong. Then if we wanted to add a payment for an existing order, we used 999 for the security code, then went back and OK'd the charge. I definitely would not recommend this with international orders or any questionable orders because you have no chargeback protection when the code is wrong. It depends on what kind of risk you want to take.