LifterLMS Checkout Errors: Causes and Fixes for Failed Payments

What each common LifterLMS checkout error message means, why the checkout sometimes just reloads, how to read gateway logs and order notes, and how to fix declined, failed and stuck payments.

  • Add as a preferred source on Google
Illustration for “LifterLMS Checkout Errors: Causes and Fixes for Failed Payments”

A LifterLMS checkout error costs you a sale and usually a support email. The student sees a red message, or worse, nothing at all: they click the purchase button, the page reloads, and they are back where they started.

This guide is for course owners and developers who need to fix that quickly. It explains the error messages LifterLMS shows at checkout and what causes each one, the silent failures that show no message, where to find the gateway's own explanation for a declined payment, and what to do with orders left as Pending or Failed.

If you are still setting up your checkout, read our LifterLMS checkout setup guide first. This article assumes a checkout that used to work, or should work, and does not.

First, work out where the checkout failed

A LifterLMS purchase passes through three stages, and the fix depends on which one failed:

  1. Validation by LifterLMS. Before any money moves, LifterLMS checks the access plan, the coupon, the selected gateway, the student's details and the terms checkbox. Failures here show a red notice on the checkout page and no order is charged.
  2. Processing by the gateway. LifterLMS creates a pending order and hands it to the payment gateway, for example the Stripe or PayPal add-on. Declines and authentication failures happen here.
  3. Confirmation and enrollment. The gateway reports success, LifterLMS records the transaction, activates the order and enrolls the student. Failures here leave money taken but no access, which is the most urgent kind.

Check the order list first. Go to LifterLMS > Orders and look for an order from the student at the time of the attempt. No order at all points to stage 1. An order with the status Pending Payment or Failed points to stage 2. An order with a successful transaction but no enrollment points to stage 3, which we cover in when a student cannot access a course.

LifterLMS checkout error messages and what they mean

These are the validation messages built into LifterLMS core, quoted as they appear.

MessageWhat it meansFix
This access plan is not available.The plan is unpublished, or set to members only and the buyer is not a memberCheck the plan's Plan Availability and the product's status
This product is not available for purchase.The course has a restriction in effect, such as a closed enrollment period or full capacityCheck Enable Enrollment Period and Enable Course Capacity on the course
Invalid Access Plan ID.The checkout link points to a plan that no longer existsRebuild the button or link from the current plan
Coupon code "…" not found.The code does not match any couponCheck spelling and that the coupon is published
This coupon has reached its usage limit… / This coupon expired on…Coupon limits or expiryEdit the coupon's limits or dates
This coupon cannot be used to purchase "…".The coupon is restricted to other products or plansAdd the product to the coupon's allowed list
No payment method selected.The plan costs money but no gateway was chosen, often because none is enabledEnable a gateway under LifterLMS > Settings > Checkout
The selected payment gateway does not support recurring payments.A subscription plan combined with a gateway, usually a third-party one, that only handles one-time paymentsUse a gateway that supports recurring billing, or change the plan's frequency
You must agree to the … to continue.A Terms and Conditions Page is set and the box was not tickedNothing to fix, unless your theme hides the checkbox
There was an error creating your order, please try again.The order post could not be createdCheck the PHP error log; usually a database or fatal error
Suspicious activity detected. Try again in a few minutes.Spam protection has blocked the visitor's IPSee the spam protection section below
CAPTCHA validation failed — please try again.reCAPTCHA or Turnstile rejected the requestCheck keys and score threshold

If a student reports a message that is not in this list, it almost certainly came from the payment gateway or from an add-on, and the gateway section below applies.

When the checkout reloads with no error at all

This is the most confusing failure, and it has a specific cause. Every LifterLMS checkout form contains a security nonce. When the form is submitted, LifterLMS verifies it before doing anything else. If the nonce is missing or invalid, LifterLMS simply ignores the submission. No error is shown and the page loads again.

A nonce becomes invalid in a few predictable ways:

  • The checkout page was cached. A page cache served a copy of the form generated for a different visitor or many hours ago. This is by far the most common cause. Exclude the checkout page and the confirmation endpoint from every caching layer: plugin, host and CDN. Our guide to LifterLMS caching conflicts lists what to exclude.
  • The tab was left open too long. WordPress nonces expire. A buyer who opens the checkout, goes away for a day and comes back may need to refresh the page.
  • The session changed during checkout. Logging in, or creating an account in another tab, changes the nonce for that user.

JavaScript errors are the other cause of a "dead" purchase button. Gateways such as Stripe collect card details through JavaScript. If an optimisation plugin delays or combines those scripts, or another plugin throws an error first, the button does nothing. Check the browser console on the checkout page. Testing with other plugins disabled on a staging copy confirms the cause.

Spam protection and captcha blocking real buyers

LifterLMS has built-in protection against card-testing attacks, where bots hammer a checkout with stolen card numbers. It lives under LifterLMS > Settings > Security:

  • Spam Protection is on by default. Its description reads: "Block IPs from checkout if there are more than 10 failures within 15 minutes." Blocked visitors see "Suspicious activity detected. Try again in a few minutes."
  • Captcha lets you require reCAPTCHA v3 or Cloudflare Turnstile at checkout. For reCAPTCHA you also set a reCAPTCHA Minimum Score, which defaults to 5 on a 1 to 10 scale.
  • Akismet Spam Protection is off by default.

Leave spam protection on. Card-testing attacks can cost you gateway fees and get your merchant account reviewed. Do watch for false positives, though:

  • Shared IP addresses. A class booking from one office or campus network can count as one IP. If ten colleagues each mistype a card in the same quarter of an hour, the eleventh is blocked. The block clears after the time window.
  • Proxy and CDN setups. If your server sees the CDN's address instead of the visitor's, all buyers can look like a single IP. Make sure your host passes the real client IP to WordPress.
  • Captcha scores. Privacy-focused browsers and VPN users sometimes score low on reCAPTCHA. If genuine buyers fail, lower the minimum score a step or try Turnstile. Wrong or swapped site and secret keys fail every request, so check those first.

Reading gateway errors, logs and order notes

When validation passes and the payment still fails, the explanation lives with the gateway. Three places tell you what happened.

Order notes

Open the order in LifterLMS > Orders. The notes panel records status changes, transactions and, for many gateways, the reason a charge failed.

The gateway's debug log

Each payment gateway's settings include a Debug Log option ("Enable debug logging"). Turn it on, reproduce the problem with a test purchase, then read the log under LifterLMS > Status > Logs. The LifterLMS Stripe documentation describes the same process for Stripe, where the log file name begins with "stripe-". Turn logging off again when you are done.

The gateway's own dashboard

Stripe and PayPal record every attempt, including ones that never reached your site. A decline code such as insufficient funds or a failed authentication is a matter between the buyer and their bank. Your job is to make sure the message reaches the buyer clearly and that they can try again.

Gateway-specific causes worth checking

  • Stripe: the webhook must be installed and receiving events. The LifterLMS Stripe documentation shows a Webhook Status field and explains how to recreate the webhook if it shows "Not installed". Payment methods must also be enabled in your Stripe dashboard, and a one-time-only payment method used on a recurring plan will fail. See our Stripe setup guide.
  • PayPal: recurring plans depend on account permissions that PayPal must enable. Check this before offering PayPal on subscription plans.
  • Test mode left on, or off: live cards fail in test mode and test cards fail in live mode. Check the gateway's test mode setting before anything else.
  • Currency: the Currency in LifterLMS checkout settings must be one your gateway account accepts.

Handling Pending and Failed orders

LifterLMS uses these order statuses: Pending Payment, Active, Completed, On Hold, Pending Cancellation, Cancelled, Expired, Refunded and Failed.

  • Pending Payment orders are created as soon as validation passes. Many of them are abandoned checkouts, not errors. If the student retries in the same session, LifterLMS can reuse the pending order.
  • Failed means the gateway reported a failed payment. For a first payment, the student has no access, and a new checkout attempt is the fix.
  • On Hold usually follows a failed recurring payment on an existing subscription. With Retry Failed Payments enabled in checkout settings, LifterLMS retries automatically. Persistent recurring failures are covered in recurring payments not processing.

If money was taken but the order still shows Pending Payment, do not simply enroll the student and move on. Find out why the confirmation did not arrive, which is usually a webhook problem, because it will keep happening to other buyers.

Checking PHP errors safely

"There was an error creating your order" and blank checkout pages usually mean PHP is failing. On a staging copy, or briefly on production during a quiet period, enable logging in wp-config.php without displaying errors to buyers:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reproduce the checkout, then read wp-content/debug.log. The file and line number in the error tell you which plugin is responsible.

Frequently asked questions

Why does my LifterLMS checkout page just refresh?

Almost always because the form's security nonce failed, usually due to page caching of the checkout. Exclude the checkout page from all caches and test in a private window.

How do I see why a payment was declined?

Check the order notes, then the gateway's dashboard. For more detail, enable the gateway's Debug Log setting and read the log under LifterLMS > Status > Logs.

A buyer says they were blocked for suspicious activity. What do I do?

The block is temporary and clears after the failure window. Ask them to wait and try again with one card. If it happens regularly to genuine buyers, check that your server sees real visitor IP addresses.

Can I test checkout without real money?

Yes. Use your gateway's test mode on a staging site, or a 100% coupon for a quick enrollment test, and place a full purchase as a logged-out visitor in a private window.

Next steps

Work through the stages in order: check whether an order exists, read the exact message, rule out caching, then read the gateway log. Most checkout problems are solved by a cache exclusion, a gateway setting or a webhook fix.

If you are losing sales and cannot find the cause, or the fix involves custom gateway code, our LifterLMS support team can investigate on a staging copy of your site. Contact us with the error message and an order number.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day