Just an FYI ...
We've had a couple of transactions now where the customer has received the error message 'Technical problem contacting the Protx gateway' and no order has appeared in the shop, but Protx has actually authorised the transaction and taken the funds from the customer's card.
On one of these occasions the customer tried (and 'failed') twice with Protx before emailing us. We checked in the Protx admin and no transactions were being shown as received/authorised for the customer, so we suggested he used Paypal instead - and the transaction went through fine.
(We also checked the Protx admin the next day - no transactions for the customer were showing then either).
The customer has just emailed us on getting his card statement and it seems his card was debited twice by Protx. We've just checked the Protx admin again today (3 weeks since the transaction) and it now shows the two authorisations.
Obviously, the transactions apparently not showing in the Protx admin is a Protx problem, and nothing to do with the mod - but it's something to be aware of if anyone has any customers who get the 'Technical error contacting payment gateway' error.
With respect to the 'Technical problem contacting the payment gateway' error, there's a post on the (new) Protx forum here:
https://support.protx.com/forum/Topic277-22-1.aspx
that suggests that the default cURL timeout might be set too low for times when Protx and/or the banks are busy - the default in the Protx integration kit is 30 seconds, same as in the Protx module.
We've upped the timeout to 120 seconds to see if that helps to avoid the problem, although, obviously, customers are likely to give up anyway if they have to wait that long ... 
includes/modules/payment/protx_direct.php, line 950:
PHP Code:
curl_setopt($ch, CURLOPT_TIMEOUT, 120);
Bookmarks