GoHighLevel integration

This development preview requires a Ulasend-configured HighLevel marketplace payment app and acceptance testing with a location. It is inactive until setup is complete and is not a published or certified Marketplace app. It is separate from Ulasend's existing CRM contact synchronization.

Supported first release

One-time USD orders from $1 to $100,000 use Ulasend hosted USDC on Base checkout. Recurring payments, stored cards, off-session charges, and automatic refunds are unavailable, as is bank-transfer checkout. Payment creation reads the order and transaction from HighLevel before accepting a total; browser-provided payment details do not authorize an order.

Connect a location

1. Have Ulasend configure the payment app and test environment, including the exact funnel or store domains used for checkout.
2. Use an approved Ulasend account with USDC on Base enabled under accepted coins.
3. Sign in to Ulasend as an account owner or administrator and complete two-factor authentication.
4. Open HighLevel connection setup and authorize the intended location.
5. Confirm the connection is ready, then choose Ulasend in the location's Payments → Integrations settings. New connections allow test payments only.
6. Run a test purchase through the actual funnel or store. Hosted checkout opens in a separate tab; confirm it shows test mode before simulating payment.

Each payment is bound to its Ulasend merchant, HighLevel location, order, and mode. The connection manages separate test and live credentials on Ulasend's server. Do not paste a secret Ulasend API key into a HighLevel public-key field or page script.

Test payments move no real money. Keep test automation, emails, inventory, and fulfillment separate from real orders. Verify successful, partial, duplicate, expired, and changed-order cases in your own location.

Payment confirmation

Payment can remain pending while the buyer completes checkout. The connector reports success only after verifying the saved invoice and the full final quoted amount, including any passed processing fee and conversion rounding above the original order total. Returning to a funnel or closing the payment window does not confirm payment. An unresolved or cancelled order needs review before fulfillment. Retries reuse the saved attempt; an expired checkout is not automatically replaced. Contact Ulasend with the order and transaction reference if the result remains unresolved.

Enable or pause live payments

Once Ulasend confirms platform setup and acceptance tests are complete, return to the connection page and explicitly choose Enable live payments. This requires an owner or administrator with two-factor authentication. Authorizing a location alone does not enable real payments.

Disable live payments stops new live checkouts while preserving reconciliation of existing payments. Disconnect stops verification and notifications and clears the connection credentials. Resolve pending payments before disconnecting or reconnecting. If remote disconnection cannot be confirmed, also remove Ulasend in HighLevel. Cancelling or disconnecting does not refund a transfer.

Platform reference: HighLevel custom payments integrations.