stopping refresh from running php scripts

cranfss

I have a website using php to accept a credit card, then if authorized, queries an external database and delivers a report to the customer. If the customer hits refresh while viewing the report, the customer will be charged for another report and the same report will be generated again(charging me). I wasn't able to figure out how to stop from executing the php all the way back to the credit card order form. I know I could check the db but the report is large and I would prefer not to dump the data into a db just so I could redisplay it if the user hits refresh.

Is there a way just to reprint what is on the screen or simply not do anything?

Can I instruct the browser to just redisplay what is already there without running php scripts again?

DigitalExpl0it

Originally posted by cranfss
I have a website using php to accept a credit card, then if authorized, queries an external database and delivers a report to the customer. If the customer hits refresh while viewing the report, the customer will be charged for another report and the same report will be generated again(charging me). I wasn't able to figure out how to stop from executing the php all the way back to the credit card order form. I know I could check the db but the report is large and I would prefer not to dump the data into a db just so I could redisplay it if the user hits refresh.

Is there a way just to reprint what is on the screen or simply not do anything?

Can I instruct the browser to just redisplay what is already there without running php scripts again?

might beable to set a cookie or session and after its doen processing just remove the cookie or session then if they hit refresh have it redirect to another page casue the value is now gone

bike5

Another way would be to save the transaction number into a database and also have a field in the database that tells if the transaction is complete or not. Then when the page loads, check the database against the transaction number and if flags that it has been competed, display the info and skip the process. Sort of what DigitalExpl0it said only saving the info in the database would be sure to last longer then a cookie or session and solve the problem if a user can't accept a cookie.