murasaki Posted February 6, 2004 Posted February 6, 2004 Does anyone hosting with TCH have success with using osCommerce, shared SSL and Payflow Link? After installing and setting the payflow link module, I am having problem processing test transaction with shared SSL. Because VeriSign Manager do not allowed accepted URL to have HTTPS, I have set the URL to: http://www.mysite.com/ http://www.mysite.com/checkout_confirmation.php http://server#.totalchoicehosting.com/~username http://server#.totalchoicehosting.com/~use...onfirmation.php http://ipaddress http://ipaddress/~username/checkout_confirmation.php And all gave the same error message when attempting to confirm order with osCommerce: Referring URL Error Referring URL does not match accepted URLs. I have seached the osCommerce community forum, but other than problems and solutions to the verisign module, I have not found solution resolving this. By typing http://server#.totalchoicehosting.com/~username, or using the ipaddress, I can get to my site no problem. So even if I purchase my own SSL certificate throuch TCH, wouldn't that also give me error? Any fellow merchants hosting with TCH have success with these packages? murasaki Quote
TCH-Rob Posted February 8, 2004 Posted February 8, 2004 murasaki, Sorry brother, I use osc and SSL but not payflow. I will see if I can find anything out for you. Give me a little time. Quote
TCH-Rob Posted February 9, 2004 Posted February 9, 2004 (edited) I have found this, Long URL to Verisigns support for Payflow Link Not sure if it will help much though, I am betting you read that aready. Help me understand, as I see it you shouldnt need shared SSL for this to work. Doesnt PayFlow Link take you to the PayFlow site and process the transaction there and once done send the customer back to your site? I saw this in the instructions Payflow Manager Setup Make sure to set your return url as "POST" and set it to verisignreturn.php I set the Return URL to verisignreturn.php, it will automatically redirect the customer to checkout_success.php. One of the testers let me know that you can set the Return Url to checkout_success.php with a silent post to verisign_return.php. They seem to both work, but I recommend the first. Have you tried it? Edited February 9, 2004 by TCH-Rob Quote
murasaki Posted February 9, 2004 Author Posted February 9, 2004 Thank you for your efforts. I read the manual and track down numerous posts on the osCommerce forums. I even emailed those who seem to have success. VeriSign Payflow Link has one feature that allow merchant to specify the Accepted URL which either id your site or a particular page on your site where the payment information is sent from. This provides an extra security. VeriSign also provide a simple integration method that puts the responsibility of collecting and protecting the customer's payment information on VeriSign. This allow you to safe a few bucks as SSL is not required if you do not require customer to log in. After switching to TCH and decided to migrate to osCommerce, a secured environment is now necessary. That's when SSL and more complicated integration comes in. After numerouse tests and researching the osCommerce forum, I found that now it is not possible to specify the Accepted URL anymore in Payflow Link, as HTTPS://.... will not match with any possible HTTP link I specify. So for those who use VeriSign's Payflow Link or considering it, the Accepted URL fields need to be left empty using the currently available contributions. And if one doesn't want to be held responsible for keeping the customer's payment information, new codes needs to be written to accomplish such task. The 2 currently available contributions do not offer this. For those who is on the same boat here, I found only the Payflow Link contribution by Joe Olson will work correctly with osCommerce 2.2 MS2. It does require extra work on your part to resolve the following issues: 1. Force the customer to click the return to your site button or silent post back successful transactions. Else, osCommerce never register the completed order. 2. Handle failed transcations so that osCommerce doesn't record the order as completed and log out the customer. The solution available on osCommerce forum can fail in certain conditions. Mine solutions are not perfect yet. The other contribution for Payflow Link requires more work than what its instruction specified. No adequate solution is availabe from the osCommerce forum. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.