CS-Cart processes payments through two distinct communication paths, and understanding the difference is what makes most checkout problems solvable from a hosting account. The first path is an outbound connection: your store contacts the payment gateway using server-side cURL to tokenize a card, create a charge, or request a redirect URL. The second path is an inbound callback (often called a notification, IPN, or webhook) where the gateway contacts your store back at a fixed URL to confirm that money actually moved. When either path breaks, the symptoms look identical to a shopper, an order that hangs on the payment step, lands in an unexpected status, or never appears at all, but the fix lives in completely different parts of your account.
On Hostiso's LiteSpeed and CloudLinux stack you work entirely as an unprivileged user, so every adjustment here happens through cPanel Jupiter, DirectAdmin Evolution, the CS-Cart admin panel, .htaccess, or .user.ini. You never touch system services or server-wide PHP settings. That constraint is actually helpful: it narrows the troubleshooting surface to a handful of predictable places.
Diagnosing outbound cURL and TLS failures to the gateway
Most CS-Cart gateways, Stripe, PayPal Commerce, Authorize.Net, 2Checkout, rely on PHP's cURL extension negotiating a modern TLS handshake with the processor's API endpoint. When a charge silently fails and the storefront shows a generic "payment could not be processed" message, the real error is almost always recorded locally. CS-Cart writes payment debug data to var/logs/ inside your document root, and you can read these files directly in cPanel File Manager or DirectAdmin's File Manager without any shell access. Look for files beginning with cscart_ containing the current date, and open the most recent one after reproducing a failed test order.
Two error strings dominate these logs. The first is SSL certificate problem: unable to get local issuer certificate, which means PHP has no valid CA bundle to verify the gateway's certificate. The second is OpenSSL/TLS: error:... or Unknown SSL protocol error, which usually means the installed PHP version is negotiating an outdated protocol that the gateway has deprecated. Stripe, PayPal, and most major processors now reject anything below TLS 1.2, and several require 1.3.
The fix starts in the PHP layer. In cPanel open MultiPHP Manager and confirm the domain runs PHP 8.1 or 8.2, which ships with current OpenSSL support. On DirectAdmin use Select PHP Version under the CloudLinux PHP Selector. While you are there, click the Extensions tab and verify that curl, openssl, and json are enabled, these are toggled per user on CloudLinux and a disabled cURL extension produces exactly the hanging checkout you are chasing. After enabling anything, confirm it loaded by creating a temporary file in your document root:
<?php phpinfo();Open it once in the browser, confirm cURL shows a TLS 1.2/1.3 capable version, then delete the file immediately so it is never exposed publicly.
If the log still shows the CA bundle error after moving to a modern PHP version, point cURL at a fresh certificate bundle from your own account space. Download the current cacert.pem from the curl project, upload it into a private folder such as /home/USER/ssl/cacert.pem using File Manager, then add a .user.ini file in your CS-Cart document root:
curl.cainfo="/home/USER/ssl/cacert.pem"
openssl.cafile="/home/USER/ssl/cacert.pem"Replace USER with your actual cPanel or DirectAdmin username. LiteSpeed reads .user.ini roughly every 300 seconds by default, so wait a few minutes or recycle through MultiPHP before retesting a transaction.
Fixing blocked payment callbacks and webhook delivery
The inbound path fails differently. Here the gateway reaches your store at a callback URL CS-Cart generated, for example https://yourstore.com/index.php?dispatch=payment_notification.processor&payment=stripe or a PayPal IPN handler. If that request is blocked, the customer's card is charged but CS-Cart never flips the order from Incomplete to Paid, leaving a frustrating mismatch between your gateway dashboard and your admin orders list.
Three account-level culprits block legitimate callbacks. The first is an aggressive .htaccess rule. If you previously added hotlink protection, a bad-bot blocker, or a referrer filter, a gateway's server-to-server POST (which arrives with no browser referer and an unusual user agent) can be rejected with a 403. Open the .htaccess in your CS-Cart root and whitelist the notification dispatch before any deny rules run:
RewriteCond %{QUERY_STRING} dispatch=payment_notification [NC]
RewriteRule .* - [L]The second culprit is ModSecurity, which Hostiso exposes per domain in cPanel under Security → ModSecurity. A gateway POST carrying a raw JSON payload sometimes trips a generic rule. You cannot edit server rules, but you can disable ModSecurity for the single domain while you confirm the callback is otherwise working, then re-enable it. If disabling it resolves delivery, open a support ticket referencing the blocked rule ID shown in your domain's ModSecurity Tools hit log so the specific rule can be whitelisted for your callback path only.
The third is a protective redirect or forced-login rule. If you password-protected a directory through cPanel's Directory Privacy and CS-Cart's callback happens to resolve under it, the gateway receives an HTTP 401 and treats the webhook as failed. Confirm the exact callback URL in your gateway dashboard's delivery log, paste it into a browser, and verify it returns a clean response rather than an auth prompt or 403.
Verifying API credentials, endpoint URLs and transaction logs
Once the plumbing is clean, credential drift is the remaining suspect. In the CS-Cart admin panel go to Administration → Payment methods, open the gateway, and switch to the Configure tab. Confirm you are not mixing live and test keys, a common failure after a store goes live is a leftover test secret key paired with a live publishable key, which makes the gateway reject every charge with an authentication error that surfaces in var/logs/ as a 401 from the processor.
For each gateway, re-paste the API keys directly from the processor dashboard rather than editing them inline, trailing whitespace copied from a PDF invoice is a surprisingly frequent cause of invalid-signature errors. Where the gateway requires you to register a webhook endpoint on their side (Stripe and PayPal both do), copy the exact URL CS-Cart displays and register it in the processor dashboard, then send a test event and watch it appear in var/logs/. Stripe signs each webhook, so confirm the signing secret in CS-Cart matches the one tied to that specific endpoint, a secret from a deleted or duplicated endpoint produces constant signature verification failures.
If logs are empty even on failed orders, raise visibility temporarily. In CS-Cart's admin under Administration → Logs enable logging for payments and general errors, then reproduce the failure and review entries without needing shell access. Keep an eye on PHP's own error_log file that LiteSpeed drops into the CS-Cart directory; a Maximum execution time exceeded there during checkout points to a slow gateway handshake rather than a credential problem, in which case raising max_execution_time modestly in .user.ini buys enough headroom for the API round trip.
If your symptom is less about payments and more about the store buckling under traffic during a sale, the capacity-side thinking in our guide to resource limits and scaling on shared hosting maps cleanly onto CS-Cart's PHP and database usage patterns. Work through outbound TLS, inbound callbacks, and credentials in that order, and nearly every CS-Cart payment fault resolves without ever leaving your hosting account.