Australian Payment Gateways for WHMCS
This reference summarises how common Australian payment options map to WHMCS—official integrations, third-party modules, custom development, or manual reconciliation. Use it to plan checkout and renewals; implementation details vary by processor and WHMCS version.
How to use this page
- Compare integration types before you commit checkout changes
- Pair with gateway development for implementation scope
- FAQ explains official vs third-party vs custom
Integration types
Labels in the table below match these categories—plan renewals and admin capture separately from signup checkout.
Official
Integration provided or documented by WHMCS for that processor.
Third-party
Vendor or marketplace modules outside WHMCS core—verify update cadence.
Custom
Bespoke gateway development when no supported module exists (e.g. BNPL).
Manual / custom
Bank-channel payments often need reconciliation automation into WHMCS.
| Gateway | Integration type | Notes | Berisco |
|---|---|---|---|
| eWAY | Official | Ships as an official WHMCS payment gateway integration. Configure with credentials from your eWAY account. | Custom configuration and automation available; TODO(owner): confirm delivered eWAY projects. |
| Pin Payments | Third-party | Requires a third-party WHMCS module—not part of WHMCS core. Verify vendor updates and support terms. | TODO(owner): confirm Berisco-built Pin Payments modules. |
| Stripe | Official | Official WHMCS integration; supports Australian methods including BECS direct debit when enabled in Stripe. | Custom checkout flows and automation available on request. |
| Afterpay | Custom | No official WHMCS module from WHMCS Ltd—custom gateway development only. | Custom development available. |
| Zip | Custom | No official WHMCS module from WHMCS Ltd—custom gateway development only. | Custom development available. |
| PayID | Manual / custom | Often settled outside card gateways; WHMCS updates typically rely on reconciliation automation. | Reconciliation automation available. |
| BPAY | Manual / custom | Bill payments via bank channels; match CRN or reference data to WHMCS invoices programmatically where possible. | Reconciliation automation available. |
| Cash App | Custom | Third-party/custom module documented on Berisco blog. | See Cash App WHMCS gateway write-up. |
| Square | Custom | Third-party/custom module documented on Berisco blog. | See Square WHMCS gateway write-up. |
| GoDaddy Payments | Custom | Third-party/custom module documented on Berisco blog. | See GoDaddy Payments WHMCS write-up. |
For delivery scope, see WHMCS payment gateway development.
From reference to implementation
A practical sequence once you know which gateways appear in the table.
Shortlist gateways
Mark which options you need at signup vs renewals vs admin capture.
Check integration type
Use this table to see official, third-party, custom, or manual paths.
Plan testing
Card, direct debit, callbacks, and refund flows in staging before go-live.
Implement
Engage gateway development or configure supported modules with documented settings.
Australian hosting providers often start from WHMCS for Australian hosting providers and WHMCS development services.
Australian WHMCS gateways FAQ
What does “official” mean in this table?
Official indicates a payment gateway integration provided or documented by WHMCS for that processor. Third-party modules are built by external vendors; custom means bespoke development.
Can Berisco implement any gateway in the table?
We implement supported official and third-party modules and build custom gateways where no supported module exists. Availability depends on processor APIs and your compliance requirements.
Where do Afterpay and Zip fit?
Both require custom WHMCS gateway work—there is no official WHMCS module listed by WHMCS Ltd for these buy-now-pay-later providers.
Need implementation help?
See our WHMCS payment gateway development service for scope, testing, and reconciliation—or request a quote with your target gateways.