 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / General / March 2008Ajax for Credit Card Processing
Hello. I have a web app that accepts credit card payments. I want to use AJAX to do an asynchronous post to the server and process the payment. I am using the UpdateProgress control to show a progress indicator. Two questions: 1) If the user clicks the button more twice will the payment be processed twice? I performed a test where I just added text to a lable in the same UpdatePanel as the button and the text did not "double up" when I clicked the Submit button twice. So it "seems" as though the payment wouldn't be process twice. And, 2) Is there a way to "Lock" the screen so that the user can't click the Submit button more than once (in the event that my assumption in #1 is wrong)? Thanks in advance, Mike > 2) Is there a way to "Lock" the screen so that the user can't click the > Submit button more than once (in the event that my assumption in #1 is > wrong)? Why not just disable the button as soon as it has been clicked once...?  SignatureMark Rae ASP.NET MVP http://www.markrae.net I could do that but I'm curious about AJAX's behavior. >> 2) Is there a way to "Lock" the screen so that the user can't click the >> Submit button more than once (in the event that my assumption in #1 is >> wrong)? > > Why not just disable the button as soon as it has been clicked once...? > Hello. > [quoted text clipped - 10 lines] > the Submit button twice. So it "seems" as though the payment wouldn't be > process twice. And, What processing service do you use? I think upon clicking the button you will get redirected to the payment page to make the payment (entering data). In this case it wouldn't be process twice in any case. > Hello. > [quoted text clipped - 11 lines] > the Submit button twice. So it "seems" as though the payment wouldn't be > process twice. And, There are a couple of ways to avoid this. One is to set up, as part of your asynch request, a "code" (GUID is fine) that is sent with the request. You can avoid double bumps by storing the "code" when the user clicks the button the first time. You then check for status of that code prior to running the payment. I would use the disable as well as this, just in case. > 2) Is there a way to "Lock" the screen so that the user can't click the > Submit button more than once (in the event that my assumption in #1 is > wrong)? AJAX allows you to use a modal dialog. You can bring it down when the asynch return is complete. You can also disable the button on click, which is a bit easier. It depends on whether you want the user to be able to do nothing or not. SignatureGregory A. Beamer MVP, MCP: +I, SE, SD, DBA Subscribe to my blog http://gregorybeamer.spaces.live.com/lists/feed.rss or just read it: http://gregorybeamer.spaces.live.com/ ************************************************* | Think outside the box! ************************************************* Hi Greg. Thanks for the response. Yes, I want the user to do nothing. Is there a modal dialog "object" as part of AJAX? >> Hello. >> [quoted text clipped - 31 lines] > | Think outside the box! | > ************************************************* Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.