Floob Posted August 1, 2007 Share Posted August 1, 2007 Ok - so its 1st August and my Protx form has problems. I go through the payment process and it just hangs on this page (after I press submit): https://ukvps.protx.com/vspgateway/service/authorisation I think at this point it is supposed to return me to my website. Is the fault with Protx or with us? Anyone else having problems? Also, according to Protx, this problem lies with osCommerce. This cannot be the case. 1. The problem shows with or without changes to the Protx payment module. 2. This problem did not show on the old payment pages This is going to lose me, and others significant business until this issues is fixed. KB https://support.protx.com/forum/Topic1606-23-1.aspx Quote Link to comment Share on other sites More sharing options...
Guest Posted August 1, 2007 Share Posted August 1, 2007 Protx are having systemwide problems following the 1st August upgrade. http://www.protx.com/monitorvsp.asp Quote Link to comment Share on other sites More sharing options...
muhsinb Posted August 1, 2007 Share Posted August 1, 2007 Protx are having systemwide problems following the 1st August upgrade. http://www.protx.com/monitorvsp.asp Looking at VSP Monitor Protx have screwed up an UPGRADE...AGAIN: http://www.protx.co.uk/monitorvsp.asp There getting a slating here: https://support.protx.com/forum/Topic1598-22-1.aspx They've essentially shut over 1000 internet store the muppets! Quote Link to comment Share on other sites More sharing options...
ronb Posted August 1, 2007 Share Posted August 1, 2007 These URLs all begin with https://ukvps.protx.com Submission URLs Old URL New URL /vps200/dotransaction.dll?service=VendorRegisterTx /vspgateway/service/vspserver-register.vsp /vpsDirectAuth/PaymentGateway.asp or /vpsDirectAuth/PaymentGateway3D.asp /vspgateway/service/vspdirect-register.vsp /vpsDirectAuth/CallBack3D.asp /vspgateway/service/direct3dcallback.vsp /vps2Form/submit.asp or /VSPAdmin/submit.asp /vspgateway/service/vspform-register.vsp Sever and Direct Additional Transaction Type URLs Old URL New URL /vps200/dotransaction.dll?service=VendorReleaseTx /vspgateway/service/release.vsp /vps200/dotransaction.dll?service=VendorAbortTx /vspgateway/service/abort.vsp /vps200/dotransaction.dll?service=VendorRefundTx /vspgateway/service/refund.vsp /vps200/dotransaction.dll?service=VendorRepeatTx /vspgateway/service/repeat.vsp /vps200/dotransaction.dll?service=VendorVoidTx /vspgateway/service/void.vsp /vps200/dotransaction.dll?service=VendorManualTx /vspgateway/service/manualpayment.vsp /vps200/dotransaction.dll?service=VendorDirectRefundTx /vspgateway/service/directrefund.vsp New Authorise URL, not in old system /vspgateway/service/authorise.vsp New Cancel URL, not in old system /vspgateway/service/cancel.vsp this is the 1st time ive seen this was it emailed ?? so the form at the moment shows $this->form_action_url = 'https://ukvps.protx.com/vps2form/submit.asp'; what should it be ?? thanks ron Quote Link to comment Share on other sites More sharing options...
nafri Posted August 1, 2007 Share Posted August 1, 2007 this is the 1st time ive seen thiswas it emailed ?? so the form at the moment shows $this->form_action_url = 'https://ukvps.protx.com/vps2form/submit.asp'; what should it be ?? thanks ron if you are using the form change the above to https://ukvps.protx.com/vspgateway/service/...rm-register.vsp nafri Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 1, 2007 Share Posted August 1, 2007 (edited) Latest Contribution http://www.oscommerce.com/community/contributions,441 takes care of these URL changes including 2 extra things added with the VendorTxCode. 1. 24 Hr time reference 2. Store Name added to the VendorTxCode incase unique identifiers are doubled. Does not however change the PREAUTH section of the code as of yet....I'll leave that update for the people that use it and can test it. Cheers, Michael. Edited August 1, 2007 by sofaking Quote Link to comment Share on other sites More sharing options...
ronb Posted August 2, 2007 Share Posted August 2, 2007 Latest Contribution http://www.oscommerce.com/community/contributions,441 takes care of these URL changes including 2 extra things added with the VendorTxCode. 1. 24 Hr time reference 2. Store Name added to the VendorTxCode incase unique identifiers are doubled. Does not however change the PREAUTH section of the code as of yet....I'll leave that update for the people that use it and can test it. Cheers, Michael. thanks mike - knew you'd come up with the update :) Quote Link to comment Share on other sites More sharing options...
FOD Posted August 2, 2007 Share Posted August 2, 2007 Hi All I am having problems with the Success/failure URLS. I changed PREAUTH to AUTHENTICATE in the code as shown below: if (MODULE_PAYMENT_PROTX_FORM_PREAUTH == 'true') { $transaction_type = 'AUTHENTICATE'; } else { $transaction_type = 'PAYMENT'; } I also tried changing the Success URL to CHECKOUT_SUCCESS and at first I thought it had worked - then I realised that the item I had just paid for was still in my shopping cart but no record of the order was made in the database (or on the order page in admin). The 'Authenticated' payments seem to be showing up in Protx admin but not in osCommerce admin orders.php page or database. Anyone who can come up with a solution (hopefully Protx themselves) will help all us traders a great deal. By the way I installed the latest version of Protx form from by Sofaking (01/08/2007) before trying this change. Any help trully appreciated... Quote You can kill the King, but you can't kill the King Riddim... Link to comment Share on other sites More sharing options...
FOD Posted August 2, 2007 Share Posted August 2, 2007 I changed PREAUTH to DEFERRED this time in the code as shown below: if (MODULE_PAYMENT_PROTX_FORM_PREAUTH == 'true') { $transaction_type = 'DEFERRED'; } else { $transaction_type = 'PAYMENT'; } I left the Success/failure URL's at the default setting: $plain .= "SuccessURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&"; $plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&"; and everything worked; page redirected to checkout_sucess.php, order logged at Protx and in Oscommerce admin. Can't for the life of me figure out why changing PREAUTH to AUTHENTICATE won't work still... Quote You can kill the King, but you can't kill the King Riddim... Link to comment Share on other sites More sharing options...
sofaking Posted August 3, 2007 Share Posted August 3, 2007 Latest Contribution http://www.oscommerce.com/community/contributions,441 Changes made to the VendorTxCode - issues brought up by theINtoy. Adds Store Name from Protx form (as these have to be unique) Adds Customers ID to the end of the reference as there is a very slim chance the SAME customer is ordering from 2 windows/carts at EXACTLY the same second. Cheers, Michael. FOB - I don't use AUTHETICATE and I know others are having problems with it. Protx is giving users till 1st Sept to fix this one so until then you can still use PREAUTH. I'll have a wee look about and see what I can find for you, but I am low in confidence that I'll have the soloution for you. Does it return you to the payment page with "3Dsecure=1&CAVV=blahblahblah" or something like that? fernyburn - Cheers :thumbsup: Quote Link to comment Share on other sites More sharing options...
FOD Posted August 3, 2007 Share Posted August 3, 2007 Latest Contribution http://www.oscommerce.com/community/contributions,441 Changes made to the VendorTxCode - issues brought up by theINtoy. Adds Store Name from Protx form (as these have to be unique) Adds Customers ID to the end of the reference as there is a very slim chance the SAME customer is ordering from 2 windows/carts at EXACTLY the same second. Cheers, Michael. FOB - I don't use AUTHETICATE and I know others are having problems with it. Protx is giving users till 1st Sept to fix this one so until then you can still use PREAUTH. I'll have a wee look about and see what I can find for you, but I am low in confidence that I'll have the soloution for you. Does it return you to the payment page with "3Dsecure=1&CAVV=blahblahblah" or something like that? fernyburn - Cheers :thumbsup: Hey Sofaking Good work The meassage I was getting is this (on checkout_payment after paying for goods at Protx): 2011 : The transaction has been Registered.&GiftAid=0&3DSecureStatus=NOTCHECKED This appeared at top of page (but under header) in a red band.??? Quote You can kill the King, but you can't kill the King Riddim... Link to comment Share on other sites More sharing options...
sofaking Posted August 3, 2007 Share Posted August 3, 2007 Hey Sofaking Good work The meassage I was getting is this (on checkout_payment after paying for goods at Protx): 2011 : The transaction has been Registered.&GiftAid=0&3DSecureStatus=NOTCHECKED This appeared at top of page (but under header) in a red band.??? It nomally produces this when there is an error..... I am wondering if because there is extra info included letting you know the status that it thinks this is an error too....hhmm It might be worth a try removing the StatusDetail part from the php file. Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 3, 2007 Share Posted August 3, 2007 I think I have found the problem......but I could be wrong. near the end of the file there is this section $Status = $values['Status']; $StatusDetail = $values['StatusDetail']; [/b]if ($Status != 'OK')[/b] { $sessionName = tep_session_name(); $sessionId = $HTTP_GET_VARS[$sessionName]; $hrefLink = tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $sessionId . '&error_message=' . urlencode($StatusDetail), 'SSL', false, false); tep_redirect( $hrefLink ); Now......I haven't fixed or worked on this but...... I think if you are using Payment and Defered then the Status that is returned is OK IF you are using Authorise and Authenticate the Status is returned as Authenticated, Registered or Rejected. I think that some more if and else statments will be needed like if (if ($Status != 'OK')...... else if if ($Status != 'AUTHENTICATED') ....... else if if ($Status != 'REGISTERED') ...... else if if ($Status != 'REJECTED') As said before I dont know if this is right, but I think it might me.....but I stand to be corrected. Cheers, Michael. Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 3, 2007 Share Posted August 3, 2007 (edited) the status bit shouldn't have [ b ] and [ /b ] around it...ooppss I definatly think this is what needs added not just a case of changing a couple of lines......but I could be wrong again Edited August 3, 2007 by sofaking Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 3, 2007 Share Posted August 3, 2007 I was thinking something like this (around Line 150) if ($Status != 'OK'); if ($Status != 'AUTHENTICATED'); if ($Status != 'REGISTERED'); { $sessionName = tep_session_name(); $sessionId = $HTTP_GET_VARS[$sessionName]; $hrefLink = tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $sessionId . '&error_message=' . urlencode($StatusDetail), 'SSL', false, false); tep_redirect( $hrefLink ); } } or if ($Status != 'OK') { $sessionName = tep_session_name(); $sessionId = $HTTP_GET_VARS[$sessionName]; $hrefLink = tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $sessionId . '&error_message=' . urlencode($StatusDetail), 'SSL', false, false); tep_redirect( $hrefLink ); } } else { if ($Status != 'AUTHENTICATED') { $sessionName = tep_session_name(); $sessionId = $HTTP_GET_VARS[$sessionName]; $hrefLink = tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $sessionId . '&error_message=' . urlencode($StatusDetail), 'SSL', false, false); tep_redirect( $hrefLink ); } else { if ($Status != 'REGISTERED') { $sessionName = tep_session_name(); $sessionId = $HTTP_GET_VARS[$sessionName]; $hrefLink = tep_href_link(FILENAME_CHECKOUT_PAYMENT, tep_session_name() . '=' . $sessionId . '&error_message=' . urlencode($StatusDetail), 'SSL', false, false); tep_redirect( $hrefLink ); } } maybe a right php programmer - or someone with a bit more knowledge about it that me caould have a bash at it. Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 4, 2007 Share Posted August 4, 2007 I have asked protx to setup the authorise stuff on my account so that I can see if any of this code works.... I wouldn't hold my breathe on it being done very soon though. Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 5, 2007 Share Posted August 5, 2007 (edited) Can someone who uses PREAUTH just now try the file from my site? It is an attempt at adding the AUTHENTICATE and AUTHORISE bit of code to get it to process properly for VSP FORM I didn't want to add it as a contribution unless I know it works. The file to be downloaded is in a new thread I have started for the AUTHENTICATE and AUTHORISE problem people are having. The thread is HERE Cheers, Michael. Edited August 5, 2007 by sofaking Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 6, 2007 Share Posted August 6, 2007 added new version to contributions http://www.oscommerce.com/community/contributions,441 Quote Link to comment Share on other sites More sharing options...
nafri Posted August 15, 2007 Share Posted August 15, 2007 Hi all i am using the latest version of protx form.protx recenlty enabed the pre auth feature for me.when i select pre authorisation to true i get this error message. 4006 : The TxType requested is not supported on this account. The value was AUTHENTICATE. In order to check if protx did enabled it, i logged in to my admin account on protx and this feature is enabled. when i installed the new version of protx form i did remove the old old one by uninstalling it.. Dont know what i am doing wrong or is this a protc issue or mine. Any suggestions.. many thanks nafri Quote Link to comment Share on other sites More sharing options...
sofaking Posted August 15, 2007 Share Posted August 15, 2007 Hi Nafri, Email protx support as they have had a few problems when the system got updated......in the mean time install the previous version....V1.16 - 2nd Aug. This still uses the PREAUTH codes that protx are allowing vendors to use until 1st Sept. At least this way you will still be able to take payments without any issues. With V1.12-V1.17 there is no need to uninstall the previous version. (I know the instuctions said so, but this code was a small update and not a mojor one) Just replace the protx_form.php file that is in catalog\includes\modules\payments with the one from the zip file. This will save you a bit of time at least. If you find that is was indeed protx that had not setup AUTHENTICATE AND AUTHORISE on your account properly, you can just copy over the same file from V1.17 again to update it. If that doen't work, post a message backup again, Cheers, Michael. Quote Link to comment Share on other sites More sharing options...
Thieving_Gypsy Posted October 9, 2007 Share Posted October 9, 2007 Hello All... My client has recently had a nightmare running Protx Direct - causing over £2500 worth of failed transactions. We've now switched back to Protx form and the problem has eased but still happens. Is anybody else experiencing problems with transations timing out? Is this really down to users not understanding the 3d Secure process or is there a problem with the whole osCommerce/Protx Form integration? Anybody got any ideas at all? THanks Andy Quote Link to comment Share on other sites More sharing options...
vmaster Posted April 9, 2008 Share Posted April 9, 2008 Would it be possible present the Protx Form payment in an IFRAME to maintain the feel of integration with the site. Any ideas ... ? Quote Link to comment Share on other sites More sharing options...
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.