How to temporarily save credit card info and shipping choice during checkout so that it doesn't have to be re-entered when a change is made?

[AlanSalamander]

Hi all,

 

I'm using the Paypal Webpayments Pro U.S. module, and everything works except...

 

It is clunky when someone has put in their credit card info, gets to the final confirmation screen, and then changes their address or shipping method. All of the sudden they then have to enter the credit card information all over again.

 

Here is how the navigation works:

 

cart->sign in->shipping/address->payment->final confirm

 

When someone gets to the "final confirm" page and wants to change shipping or address, then this is what should happen:

 

cart->sign in->shipping/address->payment->final confirm->shipping/address->final confirm (using temporarily saved information)

 

however, what actually happens instead is this:

 

cart->sign in->shipping/address->payment->final confirm->shipping/address->payment(re-entered)->final confirm

 

As you can see, it is ridiculous to have to enter the payment or shipping info twice. It should be temporarily saved either on the client side or on the paypal side so that when the customer can then be directed right back to "final confirm" without having to re-enter anything.

 

The same problem occurs if a user leaves the checkout process to add more to the cart and then returns. Everything has to be re-entered, quite annoyingly.

 

Here is my question:

 

 

Is it possible to fix this illogical and annoying behavior, and if so, how do I do that? Is there an add-on that can handle this, or some other way?

 

Best,

 

Alan

[AlanSalamander]

Hello again,

 

I have scoured the osCommerce forums and the addons, and I have still not found anything even slightly solving the problem.

 

Here is my idea for a way to solve the problem, please tell me if something like this exists:

 

cart->login->choose shipping->store shipping variable in a secure, but temporary, database->select payment info-> store payment info in the same secure/temporary database->review order/place order->all information in database is erased.

 

In the mean time, a variable is also stored each time someone moves to the next part of the checkout process. shipping would be "1" and payment "2"

If something is edited or revised such as the address, then the "next" button would lead to different pages depending upon whether 1 or 2 is stored. If 2 is stored, then it would return to the final review page instead of starting over at the beginning.

 

I am no programmer here, so I am hoping that some of you can take a look at my ideas and tell me if some addon like this currently exists, or if there is anything else that could help me.

 

Thank you in advance for any and all help,

 

Alan

[Guest]

Hello again,

 

I have scoured the osCommerce forums and the addons, and I have still not found anything even slightly solving the problem.

 

Here is my idea for a way to solve the problem, please tell me if something like this exists:

 

cart->login->choose shipping->store shipping variable in a secure, but temporary, database->select payment info-> store payment info in the same secure/temporary database->review order/place order->all information in database is erased.

 

In the mean time, a variable is also stored each time someone moves to the next part of the checkout process. shipping would be "1" and payment "2"

If something is edited or revised such as the address, then the "next" button would lead to different pages depending upon whether 1 or 2 is stored. If 2 is stored, then it would return to the final review page instead of starting over at the beginning.

 

I am no programmer here, so I am hoping that some of you can take a look at my ideas and tell me if some addon like this currently exists, or if there is anything else that could help me.

 

Thank you in advance for any and all help,

 

Alan

Perhaps it may be illegal.

[AlanSalamander]

I was under the impression that a temporary database of information could be stored server-side during the checkout process and then deleted automatically upon the order being placed? Is this not correct?

 

Also, if it isn't legal to store any of this info server-side, then is there an addon that stores all of the information user-side in the browser cache or in a cookie that will solve this problem.

 

Any information at all would be very helpful. This seems like such a huge issue to me that I am finding it hard to believe that no one else has been frustrated by it or who has tried to solve it.

 

Out of all of the issues reported during a testing of the site, this one seemed to annoy people the most, even to the point where one of them said that she often simply doesn't order from a site that makes her re-enter some of her information after altering another part of it. I can sympathize, and find it to be incredibly clunky.

 

Any help at all? I will beg if I have to. :'(

 

Alan

[Guest]

I was under the impression that a temporary database of information could be stored server-side during the checkout process and then deleted automatically upon the order being placed? Is this not correct?

 

Also, if it isn't legal to store any of this info server-side, then is there an addon that stores all of the information user-side in the browser cache or in a cookie that will solve this problem.

 

Any information at all would be very helpful. This seems like such a huge issue to me that I am finding it hard to believe that no one else has been frustrated by it or who has tried to solve it.

 

Out of all of the issues reported during a testing of the site, this one seemed to annoy people the most, even to the point where one of them said that she often simply doesn't order from a site that makes her re-enter some of her information after altering another part of it. I can sympathize, and find it to be incredibly clunky.

 

Any help at all? I will beg if I have to. :'(

 

Alan

I don't know about wpp, I just have the normal paypal ipn. It does not require that the customer enter their data twice. There are issues if the paypal end is not wet up correctly.

 

There is a support thread for wpp, and you should ask there.

[AlanSalamander]

I don't know about wpp, I just have the normal paypal ipn. It does not require that the customer enter their data twice. There are issues if the paypal end is not wet up correctly.

 

There is a support thread for wpp, and you should ask there.

 

There seem to be many WPP support threads. Is there one in particular that you are referring to?

 

Thanks for the link if possible.

[AlanSalamander]

Hello again,

 

If there is indeed a thread devoted to Paypal WPP that fixes this problem, then I am not able to find it. I have been searching every thread that I can find, and I can't find a single mention of this problem.

 

Can someone please point out the thread that discusses this issue? Any further feedback would also be appreciated.

 

Thank you.

[Guest]

Hello again,

 

If there is indeed a thread devoted to Paypal WPP that fixes this problem, then I am not able to find it. I have been searching every thread that I can find, and I can't find a single mention of this problem.

 

Can someone please point out the thread that discusses this issue? Any further feedback would also be appreciated.

 

Thank you.

Contribution

http://www.oscommerce.com/community/contributions,3647

Support thread

http://www.oscommerce.com/forums/index.php?showtopic=174981

 

I said to post there, I did not say the solution was there.

[AlanSalamander]

Contribution

http://www.oscommerce.com/community/contributions,3647

Support thread

http://www.oscommerce.com/forums/index.php?showtopic=174981

 

I said to post there, I did not say the solution was there.

 

Thank you. I'll see what I can find out over there.

 

Alan

[dynamoeffects]

You'll need to modify the PayPal Pro module to store the credit card info in a session variable and modify the fields to display that info if found. There are no PCI issues with this method.

[♥toyicebear]

You'll need to modify the PayPal Pro module to store the credit card info in a session variable and modify the fields to display that info if found. There are no PCI issues with this method.

 

 

 

Actually there is.....If you are not PCI compliant yourself and rely on using a 3 party payment gateway which is to keep you compliant...you are not alowed to store the cc info at all..even for a short time during checkout.....

 

Actually all osCommerce MS2.2 versions prior to RC1 , are NOT compliant as such...

[AlanSalamander]

Hmm, could it be possible to temporarily store the info user-side in a cookie, and then to delete it upon completion of the sale?

 

This way my server would never have the information.

 

Would this be possible Dynamoeffects? and would this be legal Toyciebear?

 

Also, Toyciebear, I do not completely follow your last sentence. i.e., "Actually all osCommerce MS2.2 versions prior to RC1 , are NOT compliant as such..."

Could you elaborate please?

 

Thank you to you both.

 

Alan

[♥toyicebear]

Hmm, could it be possible to temporarily store the info user-side in a cookie, and then to delete it upon completion of the sale?

 

This way my server would never have the information.

 

Would this be possible Dynamoeffects? and would this be legal Toyciebear?

 

Also, Toyciebear, I do not completely follow your last sentence. i.e., "Actually all osCommerce MS2.2 versions prior to RC1 , are NOT compliant as such..."

Could you elaborate please?

 

Thank you to you both.

 

Alan

 

 

No you can not bypass the PCI regulations by setting it in a cookie , you can not store it periode.

 

RC1 did introduce a small but important change in regards to taking payment by credit cards and complying to the new PCI Regulations , instead of showing the credit card form fields on the checkout_payment page it has them on the checkout_confirmation.php page.