Simple Machines Forum does not ship with a shopping cart, but it does include a genuine payment workflow through the Paid Subscriptions feature found under Admin → Features and Options → Paid Subscriptions. This module lets forum owners charge members for access tiers, usergroup promotions, or timed memberships, and it integrates directly with PayPal, 2CheckOut, and Authorize.Net. Because SMF relies on asynchronous server-to-server notifications rather than only the buyer's browser redirect, most payment problems on shared hosting trace back to one of three places: the gateway cannot reach your callback URL, PHP cannot open an outbound TLS socket to verify the transaction, or the subscription row never gets written because of a silent cURL error. The sections below work through each failure path using only the tools an unprivileged hosting account exposes.
How SMF processes gateway callbacks
When a member purchases a subscription, SMF generates an order and hands the buyer off to the chosen gateway. The gateway processes the card or PayPal balance, then sends an out-of-band notification back to a fixed SMF endpoint: https://yourforum.com/subscriptions.php. For PayPal this is the Instant Payment Notification (IPN); for other providers it is an equivalent server callback. SMF receives the POST, then opens a second outbound connection back to the gateway to confirm the message is authentic before it activates the subscription and promotes the member. This handshake is what trips up shared hosting most often, because two independent network paths both have to work: inbound POST delivery to subscriptions.php, and outbound TLS from your account to the gateway's verification host.
Start by confirming the callback URL the gateway actually holds. In your PayPal business account the IPN notification URL under Account Settings → Notifications → Instant Payment Notifications must point at the exact subscriptions.php path with HTTPS, no trailing query string, and the same canonical hostname your forum uses. A mismatch between www and non-www, or an http-to-https redirect sitting in front of the endpoint, causes PayPal to receive a 301 and stop retrying. If you force HTTPS or canonical host in .htaccess, exempt the callback so the POST body survives the redirect instead of being dropped:
RewriteEngine On
# Do not rewrite or redirect the payment callback endpoint
RewriteCond %{REQUEST_URI} ^/subscriptions\.php [NC]
RewriteRule ^ - [L]
# Canonical host enforcement for everything else
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [R=301,L]
A redirect that rewrites a POST into a GET silently discards the transaction data, so the exemption above matters even when the endpoint is otherwise reachable. You can confirm the raw endpoint answers by requesting it in a browser; a blank page or a short SMF notice (rather than a 403 or 500) means LiteSpeed is routing the request to PHP correctly.
Fixing outbound cURL and TLS verification failures
The most common silent failure is the verification callback. SMF receives the IPN, posts back to the gateway, and the TLS negotiation fails, so the subscription is never marked paid even though money changed hands. Gateways retired TLS 1.0 and 1.1 years ago and now require TLS 1.2 or 1.3, which in turn depends on the OpenSSL library and CA bundle available to your selected PHP version. On CloudLinux this is controlled entirely by the PHP Selector, not by any root-level file.
Open cPanel → Select PHP Version (or PHP Selector in DirectAdmin) and choose PHP 8.1 or newer. In the Extensions tab, confirm that curl, openssl, and fileinfo are enabled. An SMF installation that works for logins but fails every payment almost always has curl disabled or is pinned to an EOL PHP build with a stale CA bundle. SMF uses its own fetch helpers, but when those fall back to cURL the SSL settings still apply. If verification posts fail with certificate errors, raise the default TLS level and point cURL at a current CA bundle in .user.ini placed in your document root (/home/USER/public_html/.user.ini):
; Allow outbound HTTPS to payment gateways
allow_url_fopen = On
default_socket_timeout = 30
; Use the system CA bundle shipped with CloudLinux PHP
curl.cainfo = /etc/ssl/certs/ca-bundle.crt
openssl.cafile = /etc/ssl/certs/ca-bundle.crt
Note that .user.ini changes apply on the next PHP worker recycle, which can take a few minutes. After saving, trigger a fresh test payment and watch the forum's own error_log (visible in File Manager inside public_html). A line referencing SSL certificate problem or Could not resolve host tells you the problem is outbound network or certificate trust, while Connection timed out usually means the gateway's verification host is being blocked or the request is exceeding default_socket_timeout. If you only ever see the inbound hit with no outbound attempt logged, the IPN body itself is malformed or the endpoint is returning early, which points back to the redirect issue in the previous section rather than TLS.
PayPal sandbox versus live is a frequent credential trap. SMF has a separate Sandbox checkbox in the PayPal gateway settings. If that box is ticked, SMF posts verification to the sandbox host while real buyers pay through the live host, so verification can never match. Confirm the toggle matches the environment your email address and API credentials belong to.
Transaction logging and verifying activation
SMF records every gateway notification in the database, which is where you confirm whether a payment actually completed the loop. Open phpMyAdmin from cPanel, select your forum database, and inspect smf_log_subscribed (your table prefix may differ). A row with status = 1 and a populated payments_pending or vendor_ref value confirms SMF accepted and verified the callback. Rows stuck at status = 0 with no vendor reference indicate the IPN arrived but verification failed, the exact symptom of the TLS problems above. You can also review Admin → Members → Paid Subscriptions → View Subscribers to see which members were promoted and when.
To capture the raw gateway conversation for debugging, temporarily enable PHP error logging through .user.ini rather than editing any server config:
log_errors = On
error_log = /home/USER/public_html/smf_payment_errors.log
display_errors = Off
Keep display_errors off so payment pages never leak warnings to buyers, then review the log file after a test purchase and delete it once resolved. If you administer other carts alongside SMF, the same outbound-TLS and callback-exemption patterns apply, and our walkthrough of CS-Cart payments and webhooks on shared hosting covers the gateway-side verification checks in more depth. Once a live test payment produces a status = 1 row and the member is promoted to the paid usergroup, the full loop is confirmed working, and you can remove any temporary logging and redirect exemptions that were only needed for diagnosis.