Porkbun for WHMCS

Porkbun domains, sold and managed from WHMCS

Porkbun publishes an API but no WHMCS module. This one connects the two, so a
customer orders a domain on your site and it is registered on your Porkbun
account, without you opening the Porkbun dashboard for every order.

It covers what the Porkbun API covers: registration, availability, expiry
sync, nameservers, DNS records, glue records and TLD pricing. Five operations
have no endpoint at Porkbun at all. The module names them in plain words instead
of failing quietly, and they are listed on this page, before you buy.

The only thing that leaves your server is a licence check, which carries your
licence key, your WHMCS address and the module version. Nothing about your
customers or their domains.

What you get

Domains registered without leaving WHMCS

An order is placed, the module calls Porkbun, the domain lands on your
Porkbun account and WHMCS records it. Registration is charged against your
Porkbun account balance: Porkbun bills the account and not the API call, so that
balance needs to hold.

Availability checks run inside the Porkbun limit of one lookup every ten
seconds. Past that budget the module reports the answer as unknown, never as
“not offered”. A rate limit is not a verdict on a domain, and a customer should
not be told a name is taken because a counter was full.

DNS edited from the client area, without losing the rest

WHMCS edits A, AAAA, CNAME, MX and TXT records. Everything else already in
the zone, CAA, ALIAS, SRV, TLSA and subdomain NS records, is read, kept and
written back with its TTL untouched.

This matters because WHMCS sends the whole record set on every save. A module
that only understood the five types WHMCS knows would drop a CAA record the
first time a customer edited an A record, and nobody would notice until a
certificate authority refused to issue.

Expiry dates that stay true

The sync reads the real expiry date from Porkbun, so WHMCS stops inferring it
from its own renewal maths. It needs API access enabled per domain in the
Porkbun dashboard. A domain without it is reported as exactly that, rather than
being marked expired on a failed read.

Nameservers and glue records

Nameservers are read and written, up to the five Porkbun accepts. Glue
records can be created, modified and deleted, with one IP address per
nameserver, which is what the Porkbun endpoint takes.

TLD pricing imported with your margin

Pull the Porkbun price list into WHMCS and apply the margin you set. Porkbun
publishes a one-year price per TLD, so that is the figure the import carries.
Multi-year rows are not invented from it.

How it works

1. Upload the module to modules/registrars/porkbun and activate
   the registrar in WHMCS.
2. Paste your Porkbun API key and secret key, and your licence key, in the
   module settings.
3. Assign the TLDs you sell to the Porkbun registrar, then run the pricing
   import if you want it.

Compatibility

• WHMCS 8.x and 9.x
• PHP 7.4 and above
• Porkbun API v3, with the API key and secret key from your Porkbun
  account
• API access enabled per domain at Porkbun, which is what expiry sync
  reads
• Module interface in English

Your licence

The licence is verified with a public-key signature. The module carries the
public key only, which can check a reply but cannot produce one: the key that
signs never leaves our server. If our server is unreachable, the module opens a
grace window and keeps working. Only a reply that is present and wrong is
refused.

Questions asked before installing