Availability before implementation
Partner announcement versus released connector
GoHighLevel was named in the partner integration announcement supplied to us. Public release documentation was not verified on the provider website or in its developer guides. Account availability and the actual payment features require written confirmation.
Separate payment and communication setup
An email sending domain, SMS registration, booking calendar, and payment provider connection have different functions. Working email does not establish that a payment connector is installed or approved.
Which GoHighLevel payment flow needs a connection?
Choose the workflow
Specify whether you need invoice payments, a funnel checkout, payment links, or recurring billing. Confirm which of these the Blackstone connection actually supports.
Separate payments from communications
A payment connection and your email or SMS setup are different configurations. Connecting an email sending domain does not install a Blackstone payment provider.
What should happen after payment?
Records and workflow triggers
Identify which contact, invoice, order, or subscription should change after payment. Confirm the supported success, failure, cancellation, and refund events before enabling automated actions after payment.
Existing subscriptions
Determine how current subscriptions and payment credentials will be handled through an approved provider process. Do not assume they move when a provider is connected.
How do you confirm readiness?
A complete customer path
Test the actual payment flow in an approved environment, then check the customer record, payment status, refund handling, and any triggered workflow. Get written confirmation of the released connector, supported sub account setup, costs, and support contact.