Qtrop

Oh its comforting to know IM not alone:) Well you are correct. I just created a $.01 invoice as a test and then I could enter/edit a credit card from the admin interface just like we use to. So I guess for now we'll do some sort of setup fee or something that will create a default invoice on a new customer and that shoudl at least corect it for now Yep we converted to CIM to make the PCI side of things easier. I had opened a support ticket and the reply was that it has always worked this way but I had disagreed and its good to hear I wasnt dreaming....

Well even more bizarre for us. We converted to using the cim module awhile back and hvae been entering CC info and getting tokens fine on new custoemrs(Im not sure evidently how it was happening) We recently jumped to ver 6 and all of sudden noticed that our new customers CC info wasnt going to CIM. So now even when a new customer signs up and goes to their details area to enter their CC it saves locally, what a mess it creates. I dont understand the logic behind this one So the general consensus from what IM reading is that we need to create aa bogus invoice for a new customer and they have to pay it first before entering their CC info in their Account detail area? thanks MIke

Hi MACscr Sounds liek what I felt like when MB was acquired. We didnt hvae much luck wiht Bluepay and switched to authorizenet but continued to use ONLIne as the processor We've had very good luck with them but then we hadnt tried to cancel our account either MIke