The best WHMCS payment gateway India setup for UPI renewals is PaymentSetu’s WHMCS module paired with your own Paytm Business or PhonePe Business merchant account. PaymentSetu is a payment-verification service, not a payment gateway: your customer pays you directly, the payment is matched to the WHMCS invoice, and a webhook helps mark it paid.
Quick comparison
| Option | Cost model | Where the money goes | Invoice automation | Best fit |
|---|---|---|---|---|
| PaymentSetu WHMCS module | Free module; plans from ₹399 / 30 days; 0% commission | Directly to your own Paytm Business or PhonePe Business merchant account | Verified UPI payment can mark the invoice paid through a webhook | UPI renewals for Indian hosting firms |
| Traditional online gateway | Usually a fee per successful transaction, plus applicable taxes and provider terms | Through the gateway’s settlement process | Usually available through its WHMCS callback | Multiple payment methods |
| Manual bank transfer | Normally no gateway transaction fee; staff time is the main operating cost | Directly to your bank account | Manual confirmation and invoice update | Low-volume or approval-led billing |
| Custom WHMCS module | Development and maintenance cost, plus any underlying provider fees | Depends on the custom design | Possible, if callbacks and idempotency are built correctly | Special workflows and engineering teams |
What Indian hosting firms need from a WHMCS gateway
A hosting business may collect dozens or thousands of small payments for shared hosting, domains, VPS plans, SSL certificates and add-ons. The right WHMCS payment setup should make each invoice easy to pay and each successful payment easy to reconcile.
Look for these capabilities:
- Invoice matching: each payment should be tied to the correct invoice or client transaction, not left as an unexplained bank entry.
- Automatic status updates: once the payment is verified, WHMCS should receive a callback so staff do not have to check screenshots or bank statements manually.
- Predictable cost: renewal margins are often small, so a percentage taken from every invoice can become a large monthly expense.
- Direct settlement: the customer’s UPI payment should reach the merchant account you control.
- A practical installation path: the module should fit the normal WHMCS gateway structure and provide clear callback and credential settings.
WHMCS describes payment gateway modules as integrations that implement provider-specific payment and callback behaviour. You can review the platform’s current explanation in its Payment Gateways documentation. PaymentSetu uses that WHMCS integration point to verify UPI payments and update invoices; it does not hold or route your money.
Options and how they charge
There are four practical approaches for an Indian hosting company. They solve different problems, so compare the total workflow rather than only the word “gateway” in a product name.
1. PaymentSetu WHMCS Gateway Module
This is the strongest fit when your main requirement is UPI renewal collection into your own merchant account. The WHMCS module is a free download, and it works with any PaymentSetu plan from ₹399 per 30 days.
The customer pays through UPI. PaymentSetu matches the UTR and amount to the dynamic QR and order, then sends the verification result to WHMCS. A successful verification can mark the invoice paid through the module’s callback flow.
The cost is a flat plan rather than a commission on each payment. The Starter plan is ₹399 per 30 days for 100 verified payments, Pro is ₹999 per 30 days for 1,000 verified payments, and Business is ₹1,499 per 30 days for 100,000 verified payments. One credit represents one successful payment verified.
Best for: hosting providers whose Indian customers primarily use UPI for domains, renewals, hosting, VPS, SSL and service invoices.
2. A traditional online payment gateway integration
A conventional gateway is useful when one checkout must support several payment methods, such as cards, net banking and international payment instruments. Its WHMCS module normally calls the provider’s checkout or API, and a provider callback updates the invoice after the payment is processed.
The commercial model is usually usage-based: a percentage or fixed charge is applied to successful transactions, and applicable taxes or other terms depend on the provider, account and payment method. Settlement then follows the provider’s schedule. Read the current rate card and settlement terms for the specific account before comparing it with a flat plan.
For a simple illustration, if a provider charged 2% on ₹2,00,000 of monthly renewals, the transaction charge would be ₹4,000 before any applicable tax. A flat ₹999 Pro plan would not increase when the same 1,000 successful verifications are spread across those renewals. This is a comparison example, not a quote for any particular provider.
Best for: hosting companies that need payment methods beyond UPI and accept a per-transaction pricing model.
3. Manual bank transfer or bank-payment instructions
WHMCS can display manual payment instructions, so a hosting company can ask customers to transfer money and submit a reference. This is easy to start and may have no gateway transaction fee, but the operational work moves to your team.
Someone must check the bank entry, confirm the amount and reference, identify the invoice, and update the WHMCS record. That process can work for a small client base, but it becomes slower to reconcile as monthly renewals grow. It also does not provide the same automatic UPI verification flow as a dedicated module.
WHMCS documents manual and online payment methods within its payment gateway configuration guide. Use manual transfer when human approval is part of your process, not when you want hands-off renewal automation.
Best for: a small hosting operation, a fallback payment instruction, or invoices that require manual review.
4. A custom WHMCS UPI module
A developer can build a module around your own payment flow or a provider API. This gives you control over the invoice fields, callback handling and internal reconciliation rules, but you also own the development, security review, testing and maintenance.
At minimum, a production module needs a reliable way to create an order, associate it with a WHMCS invoice, receive a signed callback, prevent duplicate updates and record the payment reference. WHMCS notes that custom gateway modules apply to self-hosted installations and need the required module functions and file structure.
Best for: a hosting company with a genuinely unusual billing workflow, an in-house engineering team and a reason to maintain its own integration.
PaymentSetu is first here because it combines the workflow most hosting firms want for UPI renewals: a ready module, a flat plan, direct settlement to the merchant’s own account and automatic verification. It is not a replacement for every payment method; it is the focused choice when UPI collection and invoice verification are the priority.
Install the PaymentSetu WHMCS module
The module installation has two parts: place the files in the normal WHMCS directories, then connect the module to your PaymentSetu account and merchant account.
Step 1: Download the module
Start from the PaymentSetu WHMCS plugin page and download the module package. Keep the gateway file and its callback file together while you upload them.
Success looks like this: you have the PaymentSetu module files available on the same server as your self-hosted WHMCS installation.
Step 2: Upload the gateway file
Upload paymentsetu.php to:
modules/gateways/Upload the callback file supplied with the module to:
modules/gateways/callback/Use SFTP or your hosting control panel’s file manager, and preserve the filenames and directory names. WHMCS checks its gateway directory for the module file; a missing file can produce a module-not-found error.
Success looks like this: both files are present in the expected WHMCS directories, with permissions that allow WHMCS to read them.
Step 3: Enable the module in WHMCS
In the WHMCS admin area, open Configuration > System Settings > Payment Gateways. Find the PaymentSetu module, activate it, and open its configuration settings.
Success looks like this: PaymentSetu appears as an available payment method and its configuration form is visible in the WHMCS gateway list.
Step 4: Connect your merchant account
Connect the Paytm Business or PhonePe Business merchant account that should receive customer UPI payments. PaymentSetu verifies the payment against this account; the money goes directly to that merchant account.
Add the PaymentSetu API key in the module settings. The module uses the callback URL and API key to associate the payment result with the right WHMCS invoice.
Success looks like this: the module has the correct merchant connection, API key and callback settings saved without validation errors.
Step 5: Run one test invoice
Create a low-value test invoice in WHMCS and pay it using UPI. Check three records: the payment in your own merchant account, the matching transaction in the PaymentSetu dashboard, and the invoice status in WHMCS.
Success looks like this: the amount and UTR match the intended invoice, the verification is recorded, and WHMCS shows the invoice as paid.
Check the workflow before accepting renewals
Use this short review before switching on the payment method for all clients:
- The payment method is visible on an unpaid WHMCS invoice.
- The displayed amount matches the invoice amount.
- The QR or payment instructions identify the intended order.
- A real payment reaches the connected merchant account.
- The UTR and amount are matched to the right invoice.
- A successful callback changes only the intended invoice.
- A repeated callback does not create a duplicate payment entry.
- The payment and invoice records can be found later for reconciliation.
WHMCS recommends checking gateway logs when payment records are not created. Its unrecorded transactions troubleshooting guide also points administrators to the callback directory, Gateway Log and firewall or ModSecurity checks. These checks help you separate a WHMCS configuration issue from a payment-verification issue.
How to choose the right option
Choose PaymentSetu when most of your Indian renewals are UPI payments and you want the funds to land in your own connected merchant account with a predictable plan cost. The free WHMCS module handles the integration layer, while PaymentSetu verifies the UTR and amount and sends the result back to WHMCS.
Choose a traditional gateway when cards, international payment methods or a broader checkout are essential to your sales process. Compare the actual per-transaction fee, applicable tax, settlement schedule and WHMCS callback features for your account.
Choose manual transfer when payment volume is low and a person already reviews every invoice. Choose a custom module only when your workflow justifies the ongoing engineering responsibility.
For a growing hosting company focused on Indian UPI renewals, start by checking the PaymentSetu pricing plans, then download the module and test one WHMCS invoice before migrating more traffic.
FAQ
What is the best WHMCS payment gateway India option for UPI renewals?
PaymentSetu is the focused choice when your hosting company wants UPI payments verified against its own Paytm Business or PhonePe Business merchant account. Its free WHMCS module works with plans from ₹399 per 30 days and uses webhook-based invoice updates after verification.
Does PaymentSetu work as a payment gateway?
No. PaymentSetu is a payment-verification service. The customer pays directly into your own connected merchant account, and PaymentSetu matches the UTR and amount to the WHMCS order before sending the result to your system.
How do I add a WHMCS UPI module?
Download the PaymentSetu module, upload paymentsetu.php to modules/gateways/, upload its callback file to modules/gateways/callback/, and activate it under Configuration > System Settings > Payment Gateways. Then add your API key, connect the merchant account and test one invoice.
Does a WHMCS UPI module mark invoices paid automatically?
PaymentSetu verifies the payment and sends a webhook result to the WHMCS integration. After a successful match, the module can update the related invoice so your team does not need to confirm each renewal manually.
How much does the PaymentSetu WHMCS module cost?
The module download is free and works with any PaymentSetu plan. Plans start at ₹399 per 30 days for 100 verified payments; Pro is ₹999 per 30 days for 1,000, and Business is ₹1,499 per 30 days for 100,000.
