Powerful Product for Simple Problem

Hello:

SETUP
I have eCart 4, a form, and database set up to take the following user inputs:
1. Name (first and last)
2. Address fields
3. Credit Card field
4. Amount of Donation field
5. Donate button
No DB connection or any PHP has been applied (although I have all of the pertinent information).

GOAL:
To use eCart as the shopping cart that connects to Authorize.net

QUESTION/DESIRED OUTCOME
Am I using the right tool (eCart)? Or is there an easier way to connect? This is my first time connecting to a Merchant Account. I would like to have eCart connect my form fields to the Authorize.net account.

Thank you,
Jon

Yes, create a shopping cart. Add an add to cart button with the amount set to "updatable" from a text field. Set the ID to 1 and select the Replace option if item is already in cart.

Apply the local checkout server behavior in eCart for Authorize.net.

That should do it.

I know I need to put in a lot more time studying the eCart to fully maximize its functionality. So I thank you for providing a solution that will address my specific need.

I will post a follow up by tomorrow with the successful results.

Ray,

Unfortunately the solution did not work for me. I believe that to accomplish my task with any level of success I am going to have to work completely through the dynamic and static tutorials.

I would like to suggest to the WebAssist team a solution receipt for simple tasks like mine. The documentation is fantastic for a fully operational store, but to use eCart for a two field donation is very overwhelming.

Thank you for your solution . . . it didn't work only because I don't have a firm grasp on e-commerce and how to use eCart (yet).

Jon

Hopefully you see this Ray:

I have gone through the two tutorials and feel a little bit better about using eCart. I know I need another month or so using it to get good, but . . .

STATUS:
1. I followed your previous directions, but made a few modifications. Instead of the local checkout behavior, I used the checkout wizard.
2. Everything works great until I get the credit card submit. I get the error page saying my transaction could not be processed at this time.

QUESTIONS:
1. My Authorize.net account is still in TEST MODE. Would this affect the transaction causing the "Could not process at this time" error?
2. Am I missing an Authorize.net requirement by using the checkout wizard?

Link to the donation and subsequent checkout form:
donation.php

Thank you,
Jon

No, test mode should always be successful, so that is not the problem.

On your failure page, go to the Bindings tab and click the plus button.

Go to Webassist->eCart->local checkout response and choose Authorize.net.

This will allow you to drag and drop things like Error Messages from authorize.net to give you more information on why the transaction was rejected. It could be any number of things.

Good afternoon Ray:

I would like to share the steps I have taken with the hope that maybe you see something I missed.

1. I have two pages: donation.php and donation-details.php

2. On donation.php:
a. ID set to 1 and Replace Cart option enabled.
b. Quantity is hidden with default value of 1.
c. Price is visible and updatable via List (not text box).
d. Add to Cart button with GO TO PAGE set to donation-details.php

3. Donation-details.php:
a. Summary of charges with a SUBMIT DONATION button
b. DONATION button set up with Checkout Wizard to generate all pages. When clicked you are taken to Checkout.php (generated by the wizard).

4. On the Checkout.php: all of the credit card fields. The user fills those out and hits the Checkout Button which takes them to Confirm.php (generated by the wizard)

5. Here the summary is redisplayed and users can choose to modify the order or submit (SUBMIT ORDER button).
Here is where the problem occurs: When the SUBMIT ORDER button on Confirm.php is clicked by the user they are automatically taken to checkout_failure.php

I added the behavior to the failure page, but have been unable to generate any error codes. I am not sure how to drag and drop the error codes.

UPDATE (MARCH 18, 2009):
After adding the binding behavior, create a table (2 columns by 6 rows) in checkout_failure.php. Click on the twirly (triangle) to expand the Local Checkout Response (in the Bindings panel). I dragged out the following six responses: Response Code, Subcode, Reason Code, Reason Text, AVS Response Code, and way down at the bottom, Full Response.

Run your cart and the errors will appear.



Not sure if it makes a difference, but I am using static pages (no DB of any kind)

I contacted authorize.net and the support said that none of my attempts have 'reached' their server.

I do have PASSWORD REQUIRED MODE set to ON.
The following statement is from Authorize.net:
To use Password-Required Mode with a shopping cart, please contact your shopping cart provider and ask them to enable their cart to pass your password or transaction key with every transaction.

QUESTIONS
How do I start generating error codes, as I do not receive a 'string' of text on failure.php? Did I miss something in the above steps?

Thank you!
Jon

Your steps seem correct. Are you using local checkout or remote checkout in the checkout wizard?

I felt like I was doing everything right . . . after doing the WA tutorials and re-doing this cart a million times I felt good about the WebAssist steps.

I am using local checkout. I talked with another authorize.net support tech and he said that I should try generating a new transaction ID.

I'm going to give it a go tonight after work and I'll post the results.

Thank you for looking at my steps!

UPDATE:
I figured out how to put in the drag and drop error codes you referred to! Here is what I got:
1. Response Code: 3
2. Response Subcode: 1
3. Reason Code: 270
4. Reason Text: (TESTMODE) Line item 1 is invalid

If there are other codes I should apply to further clarify the problem, let me know. I am off to look up the code meanings . . .

Thanks again Ray!
Jon

Well this tells me exactly what the problem is... line item 1 is invalid means that you are probably setting the name or description to a field that is too long.... Drag and drop the "Full Request" and "Full Response" onto your page and send those (remove your username, password, and security key where present). Looking at that will tell me the exact problem.

My guess is that either it has an invalid amount or the name and/or description are too long. I can't believe Authorize.net support couldn't tell you that, but make sure to give them the reason code and reason text and they should be able to be more accurate with you.

Or send them the full request that is literally everything you send to them at checkout, and somebody familiar with their api would be able to spot the exact problem.