Skip to main content
GHL MCP Guide
CPR

Custom Providers

Payments & Billing · Advanced · Updated March 2026

Create and delete custom payment provider integrations to extend GHL payment processing with third-party or custom payment gateways.

Custom Providers lets you extend GHL’s payment processing beyond the default Stripe integration. If a client uses a different payment gateway, needs specific regional processors, or requires custom payment flows, this is where you connect them.

What This MCP Tool Does

This tool handles creation and deletion of custom payment provider integrations. Once a custom provider is registered, it can be configured through Custom Provider Config and used for transactions within the sub-account.

Endpoint Reference

Create a custom provider: POST /payments/custom-provider Register a new custom payment provider integration.

Delete a custom provider: DELETE /payments/custom-provider/{providerId} Remove a custom payment provider and disconnect its integration.

Authentication

Requires a Private Integration Token (PIT) with the payments scope enabled.

Key Parameters

When creating a custom provider:

  • Provider identification and type
  • Integration metadata
  • Supported payment methods and capabilities

Important Notes

Custom payment providers are an advanced feature. Most agency use cases are fully served by the default Stripe integration through Payment Integrations. Only pursue custom providers when a client has a specific requirement that Stripe cannot meet.

After creating a custom provider, you must configure it through Custom Provider Config before it can process transactions. The creation step registers the provider; the configuration step activates it.

Deleting a custom provider that has processed transactions will not reverse those transactions, but it will prevent future transactions through that provider. Verify no active subscriptions or recurring invoices depend on the provider before deletion.

Common Questions

When would I need a custom payment provider? Common scenarios include clients in regions where Stripe is not available, businesses requiring specific payment methods (ACH, specific banks), or integrations with industry-specific payment systems.

Can I have both Stripe and a custom provider active? Check the platform documentation for multi-provider support. The payment routing between providers depends on GHL’s current implementation.

How do I test a custom provider integration? Use test mode credentials from your payment provider and process small test transactions. Verify the transaction flow end-to-end before going live.

Back to GHL MCP Guide