Forem: Intally

WHMCS Alert Email Spam? 4 Solutions Compared for 2026

Intally — Fri, 08 May 2026 16:08:58 +0000

Originally published at intally.hkdfc.net.

WHMCS alert spam at 3 AM: 4 paths out, with the actual math (2026)

3 AM, phone buzzes 50 times. Not a traffic spike. It's WHMCS, faithfully emailing every invoice paid notification because the default alerting has no dedup, no cooldown, no quiet hours. Every invoice state change is one email. If you run WHMCS, you've been there.

Worse: built-in alerts only do email. No Slack, no Telegram, no Discord, no SMS. Maintenance window? Every customer alert still pings the on-call phone, no built-in silence. On-call rotation for a small team is basically not a thing. Either every admin gets every email, or one person eats it 24/7.

Quick disclosure: I run Intally (a small WHMCS / WordPress plugin shop) and one of the four options below is something we built. So this isn't neutral, but I tried to write it honestly, which means flagging the cases where you should not pick option 4.

The four real paths

There are basically four ways to fix this in 2026:

Patch WHMCS default emails and write your own hooks
Pipe WHMCS into an external SaaS monitoring tool (PagerDuty, Opsgenie, Datadog)
Buy a WHMCS Marketplace alert module from ModulesGarden or CodeCanyon
Install a dedicated WHMCS alert plugin (Smart Alerting Hub style)

Below is what each one actually costs in money and time, for a solo or small hosting shop.

Option 1: roll your own with WHMCS hooks

Best fit: teams with at least one backend dev who already knows WHMCS hooks.

Cost: 0 dollars, free as in beer
Effort: high. You need to know WHMCS hooks (InvoicePaid, TicketOpen, OrderAdd, dozens of them), write PHP for dedup (Redis or a custom table), Slack webhook forwarding, Telegram bot calls
Channels: as many as you write. Theoretically unlimited
Maintenance: hook names shift between WHMCS 8.x and 9.x. Every new channel is a new adapter. Realistically 1 to 2 engineer weeks per year
Catches:
- Maintenance silencing ends up as one-off hacks scattered across hooks.php
- On-call rotation, you design the schedule logic yourself
- Alert history, replay, retry on failure, all built from zero

If you have a dev who's done WHMCS hooks before and your needs are weird enough that no plugin fits, fine. Otherwise year-one math looks free and year-three math doesn't.

Option 2: external SaaS monitoring

Best fit: shops already running PagerDuty or Opsgenie for infra.

Pricing: PagerDuty starts at $19/user/month. Opsgenie $9 to $29/user/month. Datadog by event volume
Effort: medium. WHMCS side, write hooks that fire webhooks into the SaaS. SaaS side, configure routing, channels, on-call schedules
Channels: very wide. SaaS providers ship 30+ integrations out of the box. On-call, dedup, silence, all mature
Catches:
- Per-user pricing scales painfully. 10 admins on PagerDuty standard is $190/month, $2,280/year
- SaaS doesn't read WHMCS events natively. You middleware through webhooks, so "invoice paid" arrives as a generic incident, stripped of business context
- For most small shops, paging via PagerDuty for invoice notifications is like calling the SRE team because someone's coffee is cold

If you're already paying for PagerDuty for infra, adding WHMCS is cheap. If not, overkill.

Option 3: WHMCS Marketplace alert modules

ModulesGarden, CodeCanyon. Search "WHMCS notification" or "WHMCS alert."

Price: $179 to $499/year, ModulesGarden tier
Effort: medium. Install, configure, plug in Slack or Telegram credentials
Channels: depends on the plugin. Most cover email plus 2 to 3 channels
Catches:
- Most older plugins do "email plus Slack" and stop there. No dedup, no cooldown, no on-call rotation
- Maintenance is uneven. If the latest release is from 2024, skip it. WHMCS 8.6 and 9.0 already shifted hook semantics
- 5-year cost runs $900 to $2,500, and you may still end up writing hooks to cover the gaps

Two things to check before you buy: does it actually do dedup or just forwarding, and was it updated in the last 90 days.

Option 4: a dedicated WHMCS alert plugin

Smart Alerting Hub style plugins do the full loop: WHMCS events, multi-channel routing, dedup, on-call rotation, all in one module.

Price: free tier works, Pro is $69/year or $249 lifetime
Effort: low. Install, configure channels (paste a Slack webhook, a Telegram bot token), pick which events to subscribe
Channels: 8 standard (Email, Slack, Telegram, Discord, WhatsApp, SMS, PagerDuty, custom Webhook), no adapter writing
WHMCS events: 26 (invoice, ticket, order, service, client, network, admin)
Pro features:
- Alert dedup with cooldown windows (same event N minutes, only one push)
- Maintenance silence windows (toggle on, alerts paused, no losses)
- Custom message templates ({{variable}} placeholders, override per channel or per event)
- On-call rotation (weekly cycles plus event filtering)
- Alert digest (hourly or daily batched summary)
- Unlimited alerts plus configurable history retention
Catches:
- Free tier caps at 100 alerts/day, which a mid-size shop blows through in one busy day. Free also limits you to email plus one extra channel
- No cross-platform incident escalation in the PagerDuty sense (Slack to phone call to manager-on-call)
- Less customizable than raw hooks, though templates cover ~90% of real cases

Best fit: small to mid WHMCS hosting shops (under 50 admins) needing multi-channel alerts plus on-call plus dedup, without the per-seat SaaS bill.

Side by side

Option	Effort	Monthly / yearly cost	Channels	Dedup / on-call / silence	5-year cost
Roll your own hooks	High	0	As many as you write	Build it yourself	1-2 engineer weeks/yr
External SaaS	Medium	$19+/user/month	30+	Full	10 users ~ $11k
Marketplace module	Medium	$179-499/yr	2-3	Usually missing	$900-2,500
Dedicated plugin (Smart Alerting Hub style)	Low	Free or $69-249 once	8	Full (Pro)	$69-249

Pick by team size

1 to 3 people, under $5k/month: option 4 free tier. 100 alerts/day plus email plus one Slack channel covers it
3 to 15 people, $5k to $30k/month: option 4 Pro. $69/year unlocks dedup, on-call, silence
10 to 50 people already on PagerDuty or Opsgenie for infra: option 2. Unify incident management, eat the per-seat cost
50+ people with dedicated backend: option 1 plus option 4 or 2 mixed. Big shops have enough custom logic that off-the-shelf doesn't quite fit

A shortcut if you go with option 4

The Smart Alerting Hub plugin is the one we built, free tier installs in a few minutes. Out of the box:

Dashboard for channel health and alert stats
Configure Slack, Telegram, Discord webhooks from the WHMCS admin UI, no code
Alert history, replayable, retryable, filterable

Pro ($69/year or $249 lifetime) unlocks the things you only need once the team grows: cooldown windows, on-call rotation, maintenance silence, custom templates. If you're under 3 people and under 100 alerts/day, free is enough.

If you end up picking option 1, 2, or 3, that's fine. The reason I wrote this is so you don't pick the cheapest-looking thing and six months later realize you needed dedup and on-call all along, stacking three tools to do what one would've done. The most common WHMCS alert budget overrun I see is "just add Slack" turning into "actually we need dedup, on-call, silence" later. The rebuild costs 5 to 10x the up-front difference.

WHMCS alerting in 2026 is still underrated. Most shops treat "alert equals email" as a law of physics. Written against actual May 2026 data.

If your setup or pricing differs, I'd like to know. Drop a note at @intally_channel and I'll update the article.

Accepting Alipay in WHMCS: 4 Options for 2026, with the Actual Math

Intally — Fri, 08 May 2026 14:12:33 +0000

Originally published at intally.hkdfc.net.

Accepting Alipay in WHMCS: 4 options for 2026, with the actual math

WHMCS ships with PayPal, Stripe, and credit card gateways out of the box. If you want to take Alipay (mainland China), or HKD/USD paid via an Alipay+ wallet from a customer in HK / Taiwan / Singapore / Malaysia, WHMCS gives you nothing.

If you sell hosting and any meaningful slice of your buyers is Chinese-speaking, missing this rail probably costs you 30 to 50 percent of would-be conversions. tbh I underestimated this for years.

Quick disclosure before the math: I run Intally (a small WHMCS / WordPress plugin shop) and one of our plugins is in option 4 below. So this isn't neutral. I tried to write it the way I'd want someone else to write it for me when I was comparing, which means showing the cases where you should not pick option 4.

The four real paths

There are basically four ways to do this in 2026:

Build it yourself against the Alipay Open Platform SDK
Use a third-party payment aggregator (LianLian, cross-border acquirers, Stripe-Alipay, etc.)
Buy a ready-made WHMCS module from ModulesGarden or CodeCanyon
Integrate Antom directly (Ant International's official API, the thing Alipay+ runs on)

Below is what each one actually costs in money and time, if you're a solo or small hosting shop.

Option 1: roll your own against Alipay Open Platform

Best fit: teams with a dedicated backend dev and high volume.

Fee rate: 0 percent platform cut. Bank settlement charges 0.1 to 0.2 percent on top
Monthly fee: free
Integration effort: high. RSA2 signing, callback verification, WHMCS gateway hooks (gatewayCallback, refundCallback), plus a reconciliation script
Settlement: T+1 to your merchant bank
Maintenance: Alipay's API changes every 1 to 2 years. Signing, async callbacks, refund reconciliation, each has sharp edges. Realistically 2 to 3 weeks of engineer time per year, ongoing
Docs: all in Chinese, and not great. Noticeably rougher than what you'd expect from a Stripe-tier SaaS

If you're under $20k/month in volume and don't already have a backend dev who reads Chinese docs comfortably, this is not where I'd start.

Option 2: third-party aggregators

Best fit: low volume, no dev appetite.

Fee rate: 2 to 4 percent. LianLian around 2.5 percent, Stripe-Alipay around 3.5 percent, others vary
Monthly fee: usually free, some charge $30 to $50/mo
Integration effort: low. There are existing WHMCS modules, you fill in 3 to 5 fields
Settlement: T+1 to T+3
Catches:
- Stripe-Alipay is restricted in mainland China. Some IP ranges get blocked outright
- Many aggregators don't actually support ALIPAY_CN. They support the Alipay+ wallets used in HK / TW / SEA, which is a different rail
- KYC requirements are not lighter than going direct. You still need the same paperwork

Quick math. If you do $5,000/mo and pay 2.5 percent, that's $125/mo, $1,500/yr, $7,500 over 5 years. For a lot of shops that's more than the one-time KYC pain of going direct.

Option 3: WHMCS Marketplace modules

ModulesGarden, CodeCanyon, etc. Search "WHMCS Alipay" and you'll find them.

Fee rate: the plugin itself is 0 percent. The underlying rail might not be
Price: $179 to $499/yr typical, ModulesGarden pricing
Integration effort: medium. Install, configure, test against your merchant account
Catches:
- A lot of these plugins are wrappers around an aggregator. So you're paying both the aggregator's 2 to 4 percent cut and the plugin's annual license fee. Double dipping yourself
- Maintenance varies wildly. If the latest release is from 2024, skip it. Alipay's API has shifted at least once since then
- Most of them ship encrypted source. When something breaks you're filing a vendor ticket and waiting

Two things to check before you buy: does it call the official API directly, and has it been updated in the last 90 days.

Option 4: integrate Antom directly

Antom is Ant International's unified payment API for overseas merchants. The consumer-facing brand is Alipay+. It covers ALIPAY_CN (mainland) plus the HK / TW / Japan / Korea / SEA wallets in one integration.

Fee rate: 0 percent platform cut. Your real rate lives in the Antom merchant contract, typically 1.5 to 3 percent. Lower than the aggregators
Monthly fee: free
Integration effort: medium. RSA256 signing, callback handling, plus KYC (about 1 week)
Settlement: T+1 to your merchant bank
Catches:
- KYC needs a HK / Singapore / Malaysia (or similar) entity. A pure mainland entity goes through domestic Alipay, which is a different rulebook
- Docs are in English and genuinely good. Better than the Open Platform docs imo
- Get the timestamp or signature wrong by one byte and the whole flow fails. Sandbox debugging usually takes 2 to 5 days the first time

Side by side

Option	Cut	Fixed cost	Effort	Settlement	Long-term cost
Build your own	0%	0	High	T+1	2 to 3 weeks/yr maintenance
Aggregator	2-4%	0 to $50/mo	Low	T+1 to T+3	Compounding cut forever
Marketplace plugin	0-2% (depends on rail)	$179-499/yr	Medium	T+1	Annual license + possible double cut
Antom direct	1.5-3%	0	Medium	T+1	One-time KYC

Pick by monthly volume

Under $500/mo: aggregator. The total cut is small in absolute dollars and you save the engineering hours
$500 to $5,000/mo: Antom direct. 1.5 to 3 percent beats aggregator 2.5 to 4 percent over time, and your rate gets negotiable as volume grows
$5,000 to $30,000/mo: Antom direct. The savings here pay for half an engineer
$30,000+/mo: build it yourself or stay on Antom direct. Depends on team bandwidth

A shortcut if you go with option 4

The bottleneck for option 4 is the integration. If you don't want to write the RSA256 signing, the callback dispatcher, and the WHMCS gateway glue from scratch, there are pre-built plugins that do it for you.

Mine is one of them. antom-gateway, free tier:

ALIPAY_CN QR code in the invoice page, no off-site redirect
RSA256 signing plus platform public key verification
Multi-region API (Asia / North America / Europe) switchable via dropdown
11 currencies with correct decimal handling
One-click refunds
Sandbox / production toggle

Once you have your Antom credentials, integration goes from "3 weeks of dev time" to "fill 7 fields and save."

If you end up picking option 1, 2, or 3 instead, that's fine. The reason I wrote this is so you don't pick X and six months later realize Y was the better fit.

WHMCS-plus-Alipay is still a niche topic. Most English teutorials are 2020-era. This is written with May 2026 data.

If your setup differs, ping @intally_channel.