Why are payments failing at checkout in HighLevel?
By Ben McGary
Drafted with AI, then reviewed and approved by Ben McGary
Verified against HighLevel as of November 20, 2026
- Area
- Payments
- Time
- 14 min
- Difficulty
- Working
- Outcome
- more collected revenue
- Updated
- November 20, 2026
Don't have a HighLevel account yet? Set one up and follow this guide in your own account.
Paid link
Before you start
- Admin access to the sub-account's Payments and Sites
- Access to your Stripe Dashboard
- The checkout page where payments fail
- In the new navigation from Labs, Payments shows as Commerce
Steps
PaymentsTransactionsFilters
Find the failed payments
Open Payments, then Transactions, and click Filters. Set Status to Failed, and use Payment Mode to separate live payments from test payments. Note the source on each failed payment so you know which page to fix.
Setting What to enter Status FailedOther options: Succeeded, Processing, Refunded, Pending Payment Mode Live payments firstTest payments never touch a real card You should now see: A list of failed transactions with the source of each
Why this matters: Failures from 1 source point to a setting on that page. Failures spread across sources point to the cards or the banks.
SitesFunnelsYour funnelSettings
Turn on the funnel's Payment mode
Open the funnel and its Settings tab. Under Payments & checkout, turn on Payment mode to accept live payments through your connected providers. While it's off, the Products tab on each step shows a notice that funnel products are set to Test mode, and real cards fail.
Setting What to enter Payment mode OnOff means Test mode Require credit card On for free trials that convert to paidAsks for a card even on a $0 checkout You should now see: Payment mode on and no Test mode notice on the step's Products tab
Why this matters: Test mode is right while you build and wrong the day you launch. A funnel left in Test turns every real buyer away with a decline.
PaymentsIntegrationsConfigure providers
Check which provider handles the channel
Configure providers sets a payment provider for each channel, such as funnels, forms, stores, and invoices. A channel-level provider overrides the default, and a channel without one uses the default. Switch between Live and Test in the same screen and confirm the failing channel points to the provider you expect.
Setting What to enter Failing channel The connected provider you sell throughOverrides the default provider Default provider Your main processorCovers every channel without its own provider Provider limit PayPal plus 1 other providerMultiple non-PayPal providers can't run together You should now see: The failing channel mapped to the right provider in Live mode
Why this matters: Each channel can run through a different processor. Checking the mapping rules out a page charging through an account you didn't expect.
PaymentsIntegrationsStripeManage Payment Methods
Turn on the payment methods buyers expect
Click Manage next to Stripe, then Manage Payment Methods. Methods are switched on per area, so a method can work on invoices and still be missing from funnels. Live and Test settings are separate, so change the mode you sell in. Apple Pay also needs your domain registered under Register domains for Apple Pay and Link.
Setting What to enter Funnels Card plus any wallets you acceptToggled separately from invoices and forms Apple Pay On, with your domain registeredHidden until domain verification is complete Mode LiveTest and Live settings don't share changes You should now see: Every method you turned on showing at checkout in Live mode
Why this matters: Each missing method forces a buyer to switch to a card mid-checkout. Some close the tab instead.
Stripe DashboardPaymentsFailed payment
Read the decline reason in Stripe
Open the failed payment in your Stripe Dashboard and read its outcome. An issuer decline means the buyer's bank refused the charge, and the decline code gives the reason, such as insufficient funds or an expired card. A blocked payment means Stripe Radar stopped it as high risk before it reached the bank. For a legitimate buyer blocked by 1 of your rules, Add to allow list stops those rules from blocking matching payments again. It doesn't retry the payment.
You should now see: A decline code or Radar reason on each failed payment
Why this matters: The reason decides the next step. A bank decline needs the buyer to act, and a Radar block needs you to review it.
AutomationWorkflowsCreate workflow
Follow up on every failed payment
Create a workflow with the Payment received trigger. Add filters for Payment status set to Failed and Source set to Funnel, or whichever source is failing. Add Send internal notification for the owner, then Send SMS or Send email asking the buyer to try again with a link back to the checkout. Publish it.
Setting What to enter Trigger Payment received Payment status FailedSuccess is the other option Source FunnelAlso: Calendar, Form, Invoice, Website, and more You should now see: A published workflow that alerts you and messages the buyer after a failed payment
Why this matters: A buyer whose card failed wanted to buy a minute ago. A plain message with a link back gives them an easy second try.
SitesFunnelsYour funnelPreview
Test the checkout, then go live
Turn Payment mode off while you test, open the order page, and pay with Stripe's test card 4242 4242 4242 4242, any future date, and any 3-digit CVC. Confirm the payment shows in Transactions as a test payment, then turn Payment mode back on before you send traffic. Stripe's terms prohibit testing in live mode with real card details.
Setting What to enter Test card 4242 4242 4242 4242Any future date and any 3-digit CVC Payment mode On before launch You should now see: A successful test payment in Transactions and Payment mode back on
Why this matters: Testing happens in 1 mode and selling in the other. The switch back to live decides whether launch-day buyers can pay.
What changes once this is set up
- Failed payments show up in Transactions with a source you can act on
- The funnel takes real cards in live mode
- Buyers see every payment method you accept
- Your team hears about a failed payment while the buyer is still deciding
Common mistakes
Testing with your own card in live mode
Fix: Stripe's terms prohibit testing in live mode with real card details. Test in Test mode with Stripe's test cards.
Changing payment methods in Test and expecting Live to follow
Fix: Test and Live settings are configured separately. Make the change in the mode you sell in.
Selling several subscriptions through PayPal in 1 funnel
Fix: Multiple recurring products and bump products with subscriptions aren't supported with PayPal. Use Stripe for those checkouts.
If it is not working
Every card fails on 1 funnel
Likely cause: Payment mode is off, so the funnel runs in Test
What to check: Open the funnel's Settings tab and check Payment mode
Apple Pay doesn't appear
Likely cause: Your domain isn't registered for Apple Pay
What to check: Click Manage on Stripe and check Register domains for Apple Pay and Link
A subscription product is missing from the funnel
Likely cause: The price is a Test-mode price or wasn't imported into this sub-account
What to check: Check Payments, then Products, and import the Live-mode price
Stripe shows the payment as blocked
Likely cause: A Radar rule or a high risk score stopped it
What to check: Review the Radar reason on the payment in Stripe
FAQs
What happens when a subscription renewal fails?
With Stripe, HighLevel retries failed subscription payments automatically after a set period. With NMI, Authorize.net, or Square, set up to 3 retries, 1, 3, 5, or 7 days apart, under Payments, then Settings, then Subscription.
Can I retry a failed subscription payment myself?
On NMI, Authorize.Net, Square, or Mercado Pago, open Payments, then Subscriptions, and choose Retry Payment from the Actions menu. A card locks for 24 hours after 3 failed retries.
Do I need a separate workflow for each funnel?
No. 1 Payment received workflow with Payment status set to Failed covers every source. Add a Source filter when you want different messages for different pages.
Why does Apple Pay show for some buyers and not others?
Wallets depend on the buyer's country, device, browser, and wallet setup. Turning a wallet on doesn't guarantee every buyer sees it.
Do this next
How do I collect payments and donations in HighLevel forms
HighLevel allows you to collect online payments, custom donation amounts, and recurring subscriptions directly inside forms. You add the Payment element under the Integrations section in the Form Builder and configure suggested amounts or user-defined custom entries. Submissions and manual payment updates automatically sync with the Payments dashboard and form submission records.
Why don't my HighLevel reports match my real numbers?
HighLevel reports drift from your own count when widgets count by different dates, mix pipelines, count opportunities where you count people, use a different attribution model, or lose the source on incoming leads. On the default dashboard, every opportunity widget counts by Status change, so a deal created in March and lost in November lands in November. Work through the checks below in order and note the number after each one. Once every widget shares 1 pipeline, 1 date property, and 1 attribution model, any gap left points to specific records you can fix.
How do I see which lead sources turn into booked calls in HighLevel?
HighLevel's Appointment report groups bookings by how they were made, with values such as Funnel and User, so it can't show which lead source produced a call. Tag every contact who books a sales call with a workflow, then compare 2 Lead source report widgets on your dashboard: 1 for all leads and 1 filtered to the booked tag. Divide the second count by the first for each source and you have a booking rate. Budget moves to the sources that fill the calendar, and leads that never book stop looking like wins.
People usually get here from
How do I use payments and invoices in HighLevel for phone charges manual entries and ad-hoc items
HighLevel allows you to collect payments over the phone, record manual payments without Stripe Connect, add ad-hoc items, and pass card processing fees to clients. You can charge saved or new credit cards directly inside the invoice builder by selecting the record payment option. Manual payment entries support offline methods such as cash, check, card, bank transfer, and other payment types for one-time invoices. Added ad-hoc items can also be saved directly to your products area for future billing.
How do I set up calendar payments in GoHighLevel
HighLevel allows you to collect payments directly when clients book appointment slots on your calendars. You must first connect a supported payment gateway under your sub-account integrations and set it as your default gateway. Once connected, enable the Accept Payments toggle inside your calendar settings under Forms & Payments. Specify your booking amount, description, and live payment mode to capture revenue at the moment of booking.
How do I chase unpaid invoices automatically in HighLevel?
HighLevel chases unpaid invoices with the reminders in Invoices, Settings, Reminder Settings. Each reminder sends an email and a text on a schedule tied to when the invoice was sent or when it turns overdue, inside business hours you set. Reminders cover one-time and recurring invoices where Automatic Payment is disabled and no payment schedule exists. Set the due date, a reminder before and after it, and an optional late fee, and clients get chased without anyone writing a follow-up.
Was this guide helpful?
Ready to build this in HighLevel?
Every step in this guide runs inside HighLevel
Paid link
We may earn a commission when you sign up through this link, at no cost to you. Full disclosure.
Try this and Sell More
Sources
- Configure Payment Providers by Channel : HighLevel Support Portal
- How to Manage Stripe Payment Methods inside HighLevel : HighLevel Support Portal
- Using Apple Pay and Google Pay in order forms : HighLevel Support Portal
- Workflow Trigger - Payment Received : HighLevel Support Portal
- Subscription Settings: Failed Payment Retries : HighLevel Support Portal
- How to Manually Retry Failed Subscription Payments : HighLevel Support Portal
- Recover Failed Payments Automatically in HighLevel : HighLevel Blog
- Declines : Stripe Documentation
- Testing : Stripe Documentation
