paymentsUrl integration), post { type: "custom_element_ready_for_payment" } to window.parent on DOMContentLoaded before loading heavy UI scripts, and render the card input fields the moment setup_initiate_props arrives.
Text2Pay) link where your Custom Payment Provider iframe mounts directly on the checkout page instead of routing new clients through Billing Dashboard > Payments.
Payment Failed) that texts or emails the client a direct card-update checkout link so they can replace an expired card on one screen.
Configure a one-screen card-on-file onboarding and recovery flow for a Custom Payment Provider in sub-account <YOUR_LOCATION_ID>: 1. In Settings > Private Integrations and your paymentsUrl iframe handler, emit custom_element_ready_for_payment on DOMContentLoaded and mount card inputs immediately upon receiving setup_initiate_props. 2. In Sites > Funnels, route SaaS card-on-file onboarding through a hosted order form where the payment iframe loads directly on the page. 3. In Automation > Workflow Builder, send a direct card-update checkout link whenever an invoice or subscription payment fails.
# Audit funnel order forms and payment failure workflows in the sub-account ghl-crm workflows list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID> ghl-crm custom-fields list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID>
Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.
custom_element_ready_for_payment on DOMContentLoaded in your Settings > Private Integrations custom payment iframe so setup_initiate_props arrives immediately when the frame mounts, collect initial SaaS cards on a Sites > Funnels order form where the iframe mounts on page load| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Settings > Private Integrations | In Settings > Private Integrations (and your Marketplace Custom Payment Provider paymentsUrl integration), post { type: "custom_element_ready_for_payment" } to window.parent on DOMContentLoaded before loading heavy UI scripts, and render the card input fields the moment setup_initiate_props arrives. |
| Step 2 | Sites > Funnels | Collect the client's SaaS card on file during onboarding using a 1-step order form or Payments > Invoices (Text2Pay) link where your Custom Payment Provider iframe mounts directly on the checkout page instead of routing new clients through Billing Dashboard > Payments. |
| Step 3 | Automation > Workflow Builder | Trigger a workflow on Subscription or Invoice (Payment Failed) that texts or emails the client a direct card-update checkout link so they can replace an expired card on one screen. |
Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GHL Custom Payment Provider & SaaS Billing Kit) and weekly live clinics.