Skip to Content
How it works

Payments & subscriptions

How customers pay in Rands on HighLevel — one-time checkouts and recurring products.

Overview

Your buyer pays on PayFast or Paystack with the local methods on your merchant account. Money settles to you. HighLevel keeps the order, transaction, and subscription record.

letsgetpaid is the bridge in the middle: it opens checkout, listens for gateway notifications, and marks HighLevel paid so your automations and reporting keep working.

Recurring billing is run by the gateway (PayFast subscription / Paystack plan). We do not invent a second billing engine.

One-time payments

  1. Customer checks out on a HighLevel order form, funnel, invoice, or store with letsgetpaid as the provider.
  2. They pay on PayFast or Paystack — card, Instant EFT, or whatever your gateway account enables.
  3. On success, the order and transaction mark paid in HighLevel (after verification).
  4. Failed or abandoned checkouts leave the HighLevel transaction pending or failed, depending on what the gateway reports.

Support tip: If an order stays pending, confirm the gateway webhook / ITN URL is correct and that test vs live credentials match the HighLevel mode. For Paystack, confirm the contact has an email.

Subscriptions (recurring products)

Use HighLevel subscription / recurring products and prices. At checkout:

  1. HighLevel opens the letsgetpaid checkout with subscription mode.
  2. PayFast or Paystack creates a gateway-managed subscription when the first payment succeeds.
  3. HighLevel activates the subscription when verification returns an active subscription state.
  4. Later renewals are charged by the gateway. letsgetpaid forwards each successful renewal into HighLevel so subscription history stays current.
  5. Failed renewals update the subscription toward an unpaid / attention state in HighLevel when the gateway reports failure.
  6. Cancelling from HighLevel cancels at the gateway (when the subscription was linked successfully after the first payment).

What you should expect

SituationWhat happens
First subscription payment succeedsOrder paid; subscription Active in HighLevel
Customer abandons gateway checkoutNo charge; HighLevel stays incomplete / pending
Renewal succeedsHighLevel shows the new charge on the subscription
Renewal fails (card declined, etc.)Gateway retries per its rules; HighLevel is updated when failure is reported
Cancel in HighLevelGateway subscription is cancelled; HighLevel shows canceled
Cancel only in the gateway dashboardSync may lag until the next gateway event; prefer cancel from HighLevel

Intervals and cycles

Billing interval and cycle count come from the HighLevel product/price (e.g. monthly, yearly, fixed number of cycles). PayFast and Paystack each map those to their own frequency settings. If a price has no interval, monthly is used.

Not supported yet

  • Creating subscriptions only via HighLevel’s manual create_subscription path without a checkout (card-on-file scheduler). Use a recurring product checkout instead.
  • Saving cards for off-session charges as a primary Off Session product feature (Paystack may retain authorizations for some flows; do not rely on this for go-live demos unless confirmed).

Refunds

  • Paystack: refunds can be initiated through HighLevel when the provider supports the refund action.
  • PayFast: process refunds in the PayFast merchant dashboard for now, then reconcile in HighLevel as needed.

Platform fee

Successful charges (including renewals) incur the disclosed 1% platform fee, billed through HighLevel marketplace wallet charges (USD meter with min/max bounds). If fees cannot be collected or the wallet has no funds, new checkouts pause until you fund the wallet and retry from settings. Gateway fees are separate and billed by PayFast / Paystack.

See Pricing.

Troubleshooting

SymptomCheck
Order never marks paidWebhook/ITN URL, signature passphrase / secret key, test vs live mismatch
Subscription stuck IncompleteFirst payment must succeed; verify path must complete; wait for gateway notify
Cancel fails in HighLevelFirst payment and subscription link must have completed; retry after a successful first charge
Renewals missing in HighLevelConfirm gateway webhooks still point at production; subscription was created on that same connected location
Checkout blockedOutstanding platform fees or empty HighLevel wallet — fund wallet and retry from settings

On this page