Prevent credit card number from clearing when selecting different shipper

[corrado444]

When a customer lands on the check out page and they enter their credit card number BUT then they change their shipping method, the page refreshes and the credit card number field is cleared (not the name and the exp date though).

We used to have this problem a lot because our version of Zen cart did not pre-select a shipping method and a lot of customers filled out the CC fields only to get an error when continuing and they had to enter their CC# again. A bit annoying.

I have made a small change to the php code and now the Payment method is pre-selected and I think it will curtail future errors like this, but I noticed that any error on the checkout page and some operations such as choosing a different shipping method refresh the page and delete the CC# and the CSV number.

I think this is actually by design, but I was wondering if there was a way to have the CC# and CSV to remain persistent even if the checkout page was reloaded or if that is a built in behavior that can't be changed.

I hope I explained my problem properly.

Edit: I have actually found anotehr post where the poster is actually looking for the opposite behavior. His problem was that the CC field "remembered" the CC# even after the page was refreshed. We would like it to "remember" the CC number after a page refresh but it "forgets" it.

here is the link to that post: http://www.zen-cart.com/forum/showthread.php?t=65568

Thank you

[Kim]

What version of Zen Cart are you using? What payment module are you using?

[corrado444]

Hi, I wish I knew. This shop was built by someone else a few years ago. I tried looking in the files if there was a version number, but so far I haven't found it. Is there a place where that info may be?

As far as the payment module, it's the regular built in credit card module ad s far as I can tell, linked to authorized.net

[Kim]

... if it was a "few years ago" you need to upgrade ASAP

[DrByte]

Your version number is displayed in the footer of your admin home page, as well as by clicking the "Version" link in the upper right corner of your admin menu.
If it doesn't say v1.3.9h, you need to do some upgrading for security reasons.

And, you can determine which payment modules are enabled by going to Admin->Modules->Payment menu and seeing which ones have green dots next to them. Same with shipping, etc.

[DrByte]

I think this is actually by design

Yes, it is.

but I was wondering if there was a way to have the CC# and CSV to remain persistent even if the checkout page was reloaded or if that is a built in behavior that can't be changed.

Not intended to be changed, for PCI Compliance reasons.

[corrado444]

Quote:
Originally Posted by corrado444
I think this is actually by design

Yes, it is. Quote:
Originally Posted by corrado444
but I was wondering if there was a way to have the CC# and CSV to remain persistent even if the checkout page was reloaded or if that is a built in behavior that can't be changed.

Not intended to be changed, for PCI Compliance reasons.
##############################___

Thank you, that's exactly what I told them most likely was the case. I needed some confirmation from someone a bit more familiar with Zen Cart than I am.

Incidentally, this shop used to belong to a friend, but he has since sold it. The new owner contacted me yesterday, after probably a couple of years, because he was having a problem with customers leaving without purchasing because the CC payment was not pre-selected.

I fixed that so now the CC is pre-selected but I certainly have not had time to check on the general health and status of the store.

Naturally, the version number is in the footer of the stock template, but this store uses a custom template sans Zen Cart footer. I can probably get it from the administration footer, now that I think of it, but I haven't had reason to gothere yet (but I know where the payment modules are).

Thank you very much. I really appreciate the help.

[DrByte]

I fixed that so now the CC is pre-selected

That is a built-in feature of v1.3.9. Upgrading will take care of that for you.