How it works:
1. The credit card number is collected from the customer (via SSL-protected page)
2. The number is submitted via CURL (over SSL) to the Linkpoint server ... on port 1129 (meaning 1129 needs to be open on the firewall)
3. The gateway sends a response back, and the cart stores the order.

mod_security should only be able to affect it at step #1 ... but if that's the case, it's being too restrictive.

If it's never getting to the linkpoint server, then step 2 is failing ... meaning either CURL isn't configured to run over SSL, or port 1129 isn't open on the firewall/router.



Semi-related FAQ article: https://www.zen-cart.com/tutorials/i...hp?article=298


One way to test the CURL/SSL setup is to look in your /extras file for curltest.php, and run it from your browser, using an extra parameter, like this:

www.my_site.com/extras/curltest.php?linkpoint=1

If you get SSL or CURL errors, something's broken in those.
If you get a timeout error then the firewall is blocked.
If you get a message from Linkpoint about invalid account number, then it means you talked to the linkpoint server successfully (ie: the error is from *their* server, meaning your communications is open)

What happens when you do that test?

What happens if you turn on the "Debug Log To File" option in your admin area inside the linkpoint module settings? The logs will be stored in the /cache folder, as long as it's writable.


Ask them to tell you "which" rules are being triggered ... and the log details that indicate such.