Scott...I guess what I am asking is in the payment page under authorize.net instead of putting my Merchant Account Username I should put in my API LOGIN number.

Scott....I went ahead and entered my API LOGIN number that I have on my Authorize.net account and entered it in the field where Merchant Account Username and uploaded it and it is working fine. I edited some pages and when I attempted checking out with Authorize.net it worked fine so would it not be better maybe in the new Pro to have the API LOGIN number also or replace the Merchant Account Username field with the API LOGIN number field.

Glad it is working. I see what you were trying to describe now. Authorize.net made that text change about a month ago. We have already made that change in the Pro version and Basic version and it will be in the next release.

Scott, I've set up a shopping cart and purchased the authorize.net module. I contacted my current merchant services to see if I could use my existing account and to inquire on authorize.net. They offered me a package and set up an ecommerce account. At the same time, I bought a SSL certificate for my domain and got that set up. I called today and checked with merchant services as I hadn't heard anything back. They need the page active so they can check the SSL certificate. I've been given a site to authorize.net test account. Is this normal? It seems that it's a question of what came first - the chicken or the egg? Can I use this authorize.net test account in the Coffee Cup authorize.net module and supply them with the certification information that they need to OK the site?

Thanks, Lynn Snell

You really do not need an SSL certificate at all for your domain to use with our software. Each purchase is handled directly by the merchant and all purchases are handled over HTTPS anyways. Unless you are trying to capture other account data on your website, I think you can live without it on your server.

Hope that is what you were asking..

Electronic Payments (EPI) is my existing merchant service provider. When I contacted them about ecommerce and using authorize.net they told me that I would have to purchase a SSL certificate from my GoDaddy (my hosting provider). Did this. Now they won't set up the authorize.net account until they can use the payment page and verify the SSL. I'm in the process of setting up their test account but was wondering if it was going to work in my shopping cart. Seems to me that they could verify the SSL by the fact that the website is now https: Maybe I'm wrong. Lynn

It sounds like they are confused on how this service will be used. You do not need an SSL certificate at all to use authorize.net and Shopping Cart Creator.

Great! Just what I need - confusion on their part!

I'm almost through the process of setting up the test account - with a few customer interruptions - so we'll see if I can get what they need. I'm not going to argue with them. I've purchased the SSL already so that's done with even if I didn't need it. I'm just hoping that the authorize.net test account works OK through your software. I guess I'll find out here shortly.

Looks like I've got the test account set up in the shopping cart but now I have an error message which they say will happen. (The following errors have occurred.
(13) The merchant login ID or password is invalid or the account is inactive.)

From the Test Account Activation Guide: NOTE: When testing AIM or SIM integrations using a test environment account, you must send your POST data to https://test.authorize.net/gateway/transact.dll. If you attempt to send transactions to our production server URL, https://secure.authorize.net/gateway/transact.dll, you should expect an error 13 to occur (The merchant Login ID is invalid or the account is inactive).

Should I go into the HTML and change the POST location during the test? Will it harm anything... as long as I "fix" it back to the original when account goes live?

This whole verification process seems totally unnecessary as it looks like the customer is directed to the authorize.net server for processing of payment. Isn't that part of what I'm purchasing from them? The CC information isn't stored on my computer.......am I correct? If I understand you correctly, that's why my site doesn't really have to have a SSL certification. Of course, now they are gone for the day. Oh well.

Lynn

Lynn AIM is used when the customer stays on your site for the entire process using SSL. CC SC does not use this method.

CC SC uses the SIM method whee the customer shops on your site and is directed to A.net for CC processing. Nothing is stored on your server. All the credit card details are transacted on the A.net servers.