I work so much using AJAX I may not be able to see the forest for the trees.
Without using AJAX and using its success callback function, how else will I "send (my) thank you email after they are redirected back to (my) site" ? My first thought is to use the AJAX success callback as the means by which I'll call another method to send a thank-you email, store info in the database (not cc info), etc. Is there a simpler way? Besides an AJAX submission and callback, how else will I continue processing info? Call another CFC method to further process form data from the re-direct page? And if the page that Authorize.net redirects to is a "Thank-You" page, then the form variables will have to be saved as session variables to further process the original form variables for emailing, database storage of info, etc.... correct? Rick -----Original Message----- From: Russ Michaels [mailto:[email protected]] Sent: Tuesday, September 18, 2012 1:48 PM To: cf-talk Subject: Re: Question about using AJAX with Authorize.net well it depends how you process. if you redirect to authorize.net and then come back to your site, then why not simply send your thank you email after they are redirected back to your site, this is how most folks do it. The ajax stuff seems a bit overkill. If your processing serverside, then you simply need to wait till you get the response back from your CFHTTP call. On Tue, Sep 18, 2012 at 6:40 PM, Rick Faircloth <[email protected]>wrote: > > I'm implementing my first donation form using Authorize.net. > > I've found in their fine-print that I cannot submit any personally > identifiable information to their servers. > > We have a form which includes personally identifiable information > for emailing thank-you's, etc. > > Therefore, I'm planning to implement an AJAX solution to > intercept the formfield data that is applicable to the transaction > and is required by Authorize.net and submit that via AJAX to a method > in a cfc, which will send the pertinent data to Authorize.net. > > In the success section of the AJAX solution to Authorize.net, I'll > implement a further submission of the rest of the form data (the > personally identifiable information) to another method in a cfc, > which will process that data for in-house (non-Authorize.net) use. > (Or something similar to this process...) > > Any warnings, cautions, or gotcha's in this approach? > > Thanks for any feedback! > > Rick > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352659 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
