WooTz wrote
I don't think you can do another transaction based on an earlier transaction number.
The user would however have to enter his CC / Expiry date again. To me this is a perfect method as his info does not get stored in your portal. For the transaction though, the gateway provider will store the needed information.
In my suggestion I would never store that information in the store, the customer can easely enter just 16 digits without too much hassle, and I'm sure he would feel more comfortable.
I have to completly agree with WootZ here, I've done a good amount of research on this and the Payment Card Industry is pretty strict on how data is stored in order to reduce liability. It's best to just store the transaction number.
And most eComm managers like myself aren't necessarily worried about being hacked from the outside and those getting CC Num's.. It's the people on the inside you've gotta be more concerned about. As bad as that sounds, it's true.
Also, another consideration is how often are people actually ordering from your store that the speed of the order is that important? I don't think you're planning on putting up another Amazon, or Ebay, or WooT ;) where your getting the same customers every day and sometimes multiple times a day. And if you are, well, no offense against the Store Module, but I don't think thats really the direction it's ready to go at this point.