Critical Limitation in Multi-Gateway Support — Request for Gateway Selection at Order Form Level
M
Mahmoud Ismail
We were initially very excited when we saw that GHL allows us to install multiple payment gateways inside Payments → Integrations. This gave us the impression that we would be able to assign different gateways to different checkout pages or funnels based on our business needs.
However, this excitement quickly faded once we realized the current limitation:
there is no option anywhere inside the Order Form element, page, or funnel to select which gateway to use. Instead, all Order Forms are forced to use only the default payment gateway, regardless of how many gateways we have integrated.
This limitation significantly impacts our business model. We operate in a market (Egypt) where:
- Paymob is the payment provider that fully supports local EGP payments,
- While Stripe is essential for international customers.
Our ideal setup was:
- Detect customer location based on IP
- Automatically show the appropriate checkout form:
* Paymob Order Form for Egypt
* Stripe Order Form for other countries
This would allow us to offer EGP local payments for Egyptians (debit cards, Meeza, etc.) and USD Stripe payments for global customers — all within the same GHL sub-account.
However, due to the limitation where the Order Form always uses the default gateway, this entire flow becomes impossible.
Although GHL allows multiple gateways to be connected, we unfortunately cannot utilize them because there is no ability to select a gateway on order form element and as a result, only one gateway (the default) is ever used, and all others become unusable.
This limitation defeats the purpose of allowing multiple gateways to be installed in the first place.
For GHL to truly support multiple gateways and real global businesses, we kindly request the following features:
- Ability to choose a payment gateway at the Order Form level
This can simply be a dropdown inside the Order Form settings (like Stripe, Paymob, NMI, etc.).
- Or at minimum, the ability to assign a gateway per Page or per Funnel
Allowing us to bind a specific funnel to a specific gateway.
- Or allow the “Default Gateway” setting to be overridden for specific Order Form modules
Any of these options would immediately solve the problem.
Why This Is Critical for Us (and many others)
Markets like Egypt, India, Pakistan, KSA, UAE, South Africa, and emerging regions require local payment gateways because:
- Most customers do not have international credit cards
- USD-based Stripe payments are rejected
- Local currency pricing dramatically improves conversions
- At the same time, Stripe remains essential for global traffic.
Without the ability to assign gateways per Order Form/page/funnel:
- Multi-country businesses cannot operate properly
- Local-currency conversions drop significantly
- The multi-gateway integration feature becomes unusable
We kindly ask you to consider adding this feature, as it is essential for businesses that need to support multiple regions with different payment infrastructures.
We truly believe that enabling gateway selection at the Order Form (or page/funnel) level would make GHL dramatically more flexible, powerful, and suitable for international businesses like ours.
Thank you very much for your time and support.
We look forward to your feedback and hope this becomes part of GHL’s roadmap.
Warm regards,
Mahmoud Ismail
Mental Health Hub UAE
Log In