Tiger LMS

Payments (LMS)

Sell courses with Stripe/PayPal/Square/Razorpay/Manual — per-gateway test/live modes with separate key pairs, Test connection, plus coupons and an orders ledger.

2 min read Updated July 14, 2026

Tiger LMS sells courses directly with built-in payment gateways. Each gateway runs in its own Test/Sandbox or Live/Production environment with a separate set of keys, so you can rehearse checkout before taking real money.

Where: WP Admin → Tiger LMSSettingsPayments.

Gateways

Gateway Credentials
Stripe Publishable key + Secret key (per environment)
PayPal Client ID + Client secret (per environment)
Square Access token + Location ID (per environment)
Razorpay Key ID + Key secret (per environment)
Manual Offline / bank-transfer instructions shown to the buyer

Each gateway is its own card. Per card you set an Environment toggle (Sandbox or Production), enter that environment’s credentials, and press the card’s own Save. A read-only Webhook endpoint is shown to copy into the provider’s dashboard, and a Test connection button pings the provider using the stored keys for the selected environment and reports back honestly.

Free vs. Pro

The Manual gateway (offline / bank transfer) works on every plan, so you can accept payments and grant access by hand. The automated card gateways — Stripe, PayPal, Square and Razorpay — are unlocked by the Pro license; on the free plan checkout through them is blocked server-side.

Currency

Where: SettingsGeneral.

New orders are created and charged in the site’s Currency, set once on the General tab. All gateways use it.

Coupons

Where: Tiger LMSCoupons.

Coupons (a Pro feature) apply a percentage or fixed-amount discount at checkout. Create a code, choose the discount, and buyers enter it during purchase.

Orders

Where: Tiger LMSOrders.

Every purchase is recorded as an Order with its buyer, course, amount and payment status. A completed order is what triggers enrollment and the purchase-receipt email; a pending order means the gateway hasn’t confirmed the payment yet.

Troubleshooting

Test connection fails.

Re-check the keys for the selected environment — sandbox keys tested against production (or vice-versa) will fail. Save the card after editing keys, then test again.

Payments succeed but students aren’t enrolled.

Enrollment is driven by the gateway’s webhook confirming the charge. Copy the shown Webhook endpoint into the provider dashboard and make sure the events reach your site; until the webhook lands, the order stays pending.

A card gateway isn’t available.

Stripe, PayPal, Square and Razorpay checkout require a Pro license. On the free plan use the Manual gateway.

Frequently asked questions

Confirm the card is in the right mode — test mode pings the sandbox, live pings production.

No — they’re write-only and never returned to the browser.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.