Home → Problems →

Unable to bill through the site.

• Edit

marcus

20 Jan, 2010 04:31 AM

When I turned the gateway out of test mode I'm not able to create a customer/subscription through cheddar getter's web interface. I can create a customer/subscription through the API however.

Please advise
Marcus

1. Support Staff 1 Posted by Marc Guyer on 20 Jan, 2010 03:22 PM

   

   Marcus -- We're looking into this. Did you receive an error message?

   • Edit

2. Support Staff 2 Posted by Marc Guyer on 20 Jan, 2010 03:24 PM

   

   what is your product code?

   • Edit

3. 3 Posted by marcus on 20 Jan, 2010 04:10 PM

   

   COMMUNITY_OFFERS_TEST

   This is what I see when I try to create a customer:
   http://skitch.com/mirven/ntjxq/cheddargetter-new-customer

   • Edit

4. Support Staff 4 Posted by Marc Guyer on 20 Jan, 2010 04:49 PM

   

   Ah, I see. That's somewhat normal. AuxCode=6000 is a basic declined payment. You can see the documentation on that here. You can also see the declined payment in the authorize.net merchant interface. Since your merchant account is probably new, there might be something wrong with the configuration there or at Authorize.Net.

   What's happening in this case is the setup fee transaction is being declined. Authorize.Net doesn't provide any more information than that. It might be worth a call over there assuming that you've verified that the card you're using is valid and has enough available balance.

   • Edit

5. 5 Posted by marcus on 20 Jan, 2010 05:11 PM

   

   Hi Marc,

   When I try creating a customer/subscription via the api it works but when I
   create via cheddar it does not. This can be seen by using the page
   https://www.communityoffers.com/test_payment/new.

   This will create a TEST subscription on the COMMUNITY_OFFERS_TEST product. I
   cannot create a TEST subscription directly from within cheddar.

   Thanks,
   Marcus

   • Edit

6. 6 Posted by David Carolan on 20 Jan, 2010 05:55 PM

   

   I checked with AN. No issues at all on their end. We are live and active.
   They show no configuration issues, but we cannot accept AMEX or Discover
   yet.

   Not sure if you would need to try a different card. Would like me to try?

   Keep pressing Mark to assist with any config issues.

   • Edit

7. Support Staff 7 Posted by Marc Guyer on 20 Jan, 2010 06:44 PM

   

   There is very little difference between the GUI and the API logic. Are you also seeing a declined payment in the authnet merchant interface?

   • Edit

8. Support Staff 8 Posted by Marc Guyer on 20 Jan, 2010 06:46 PM

   

   Oh, and btw, I get the attached when going to https://www.communityoffers.com/test_payment/new

   • Picture_1.png 11.4 KB
   • Edit

9. 9 Posted by David Carolan on 20 Jan, 2010 06:50 PM

   

   No

   • Edit

10. Support Staff 10 Posted by Marc Guyer on 20 Jan, 2010 07:00 PM

    

    Hmm... It's actually the verification transaction that is failing. CG communicates with the authnet CIM. When CG tells AN that there is a new customer and subscription, AN automatically executes a verification transaction for 0.01 to ensure that the credit card is valid and at least has a positive balance. I'm seeing in our logs that this communication is happening as expected and the response from AN is:

    2,1,2,This transaction has been declined.,,Z,2806704438,none,Test transaction for ValidateCustomerPaymentProfile.,0.01,CC,auth_only,none,marcus,irven,irven,,,,78704,,,,[email blocked],none,none,none,none,none,none,none,none,0.0000,0.0000,0.0000,FALSE,none,F0AE01F7DFB8B91F494B9E68037893CE,N,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,3626796
    

    This is the response that indicates a standard declined transaction. You should see a declined transaction in the AN interface.

    • Edit

11. 11 Posted by David Carolan on 20 Jan, 2010 07:10 PM

    

    I am forwarding this to Marcus for verification. Marcus?

    • Edit

12. Marc Guyer closed this discussion on 18 May, 2010 01:29 PM.