Billing Information Overwrites Shipping in Step 3. Using C# and CIM ... I think.

[myprimewine]

We recently converted to asp.net and from AIM to CIM.

Our programmer posted a couple of test transactions and said all was working as it should.

But clearly this is not the case. Because we have only received 2 small orders in the time we typically would have received 100 or more

Our programmer has been paid is gone. We need to find and fix these bugs immediately. So today I'm getting  crash course in this subject

From everything I've read here and all the testing  I was able to do with the tools here,  the problem seems to be on the Step3  Review Screen

Step1:  Enter Billing info

Step2: Enter Shipping info

Step3: Review>>>> Screen Shows  

Bill To: Billing  

Ship To: Billing

As far as I can tell everything else works smoothly and we are live. 

Please let reply with suggestions or let me know if you require any additional info.

Thank you much... We are standing by.

Our Cart starts here: http://www.myprimewine.com/checkout/process.aspx?step=1

[RaynorC1emen7]

I think the problem is that it is not running under HTTPS.

Look like it will run under HTTPS if I change the URL https://www.myprimewine.com/checkout/process.aspx?step=1

So it might just be a fix on the http://www.myprimewine.com/basket.aspx checkout button to call the checkout page with HTTPS instead of HTTP

[myprimewine]

Thanks for the prompt reply. We had SSL before the conversion. 

This programmer wanted to use  solution without SSL - so we have not installed it. Hence the current CIM setup

SSL is the only way I know to set up https for the basket.aspx . Is there any reason I shouldn't apply it here?

[RaynorC1emen7 · Accepted solution]

Most web user will not put in their CC# on a non-HTTPS site. And the SSL is good until April 17th, 2012. Not sure why the programmer don't want to use it.

CIM still need SSL unless you use the new "hosted option" for CIM.

You can set it up from any page as long as "step 3" show it is using it.

[myprimewine]

The problem was resolved by correctly configuringthe SSL.

Thanks for assistance!

J