Short answer: WHMCS supports several Australian payment options. eWAY is built in. Stripe's Dynamic Payments module supports Australian BECS Direct Debit from WHMCS v9.0.3. Pin Payments and Square work through third-party modules. Afterpay and Zip need a custom module, and PayID and BPAY are bank transfers, so the job there is automating reconciliation rather than installing a gateway.
If you run a hosting company or subscription service on WHMCS with mostly Australian customers, your gateway mix affects how fast you get paid, how many renewals fail, and how much time goes on matching payments by hand. Here's each option and where custom work is worth it.
Why gateway choice matters for Australian WHMCS businesses
WHMCS automates invoices, reminders and renewal charges. That only works if your gateway supports tokenised recurring payments: the payment details stay with the provider, and WHMCS keeps a token it can charge later.
For Australian businesses, also think about:
- AUD billing, so local sales aren't converted.
- Local habits. Many customers prefer direct debit, PayID, BPAY or buy now, pay later over cards.
- Recurring vs one-off. Some methods can't be stored for automatic renewals.
- Reconciliation. Every payment WHMCS can't match itself becomes manual work.
Gateways WHMCS supports natively
eWAY
eWAY is an Australian gateway with a native WHMCS module. According to the WHMCS documentation, the current eWAY module uses token payments, so card details are stored in eWAY's PCI DSS environment and WHMCS charges the token for future invoices. The module supports one-time payments, recurring payments, refunds and remote card updates.
You set it up under Configuration > Apps & Integrations with your eWAY API key, password and public API key. If you used the older eWAY Rapid 3.1 module, WHMCS has a migration option that moves existing tokens across to the current module.
Good fit for: businesses wanting a local gateway with a built-in integration.
Stripe, including BECS Direct Debit
WHMCS recommends its Stripe Dynamic Payments module for Stripe. WHMCS has confirmed that Australian BECS Direct Debit through Stripe is available in this module from v9.0.3. That lets customers pay straight from an Australian bank account using their BSB and account number.
A few things to know before you switch it on:
- Mandates. Stripe's documentation says BECS payments need a Direct Debit Request (DDR) mandate from the customer, and Stripe can generate it for you.
- Delayed confirmation. BECS is a "delayed notification" method. Stripe says it can take up to three business days to find out whether a debit succeeded or failed. Factor this into your suspension and late-fee rules so you don't suspend a service while a payment is still pending.
- AUD only. BECS Direct Debit only works in Australian dollars.
- Extra verification. Stripe may ask for more identity checks before enabling BECS.
- Restricted API keys. WHMCS recommends restricted keys for its Stripe modules, and generates webhook secrets automatically when you save them.
Good fit for: recurring hosting or SaaS billing where you want a direct debit option next to cards.
Gateways that need a third-party module
Pin Payments
Pin Payments is an Australian payment provider. Its WHMCS integration is a third-party module developed by Snapfrozen and listed on the WHMCS Marketplace. The listing describes tokenised payments, support for WHMCS recurring billing, and refunds.
Check its listed WHMCS version compatibility against your version, and if you run a newer release, test it in staging first.
Square
Square isn't one of WHMCS's built-in gateways, but several Square modules are available on the WHMCS Marketplace. Desmarter, which develops WHMCS modules under Berisco, has also built a Square payment gateway for WHMCS. When comparing Square modules, check tokenised card storage, refunds, webhooks and WHMCS/PHP compatibility.
Options that need custom development
Afterpay and Zip (buy now, pay later)
We couldn't find an official WHMCS module for Afterpay or Zip at the time of writing. Both providers publish merchant APIs, so a custom WHMCS gateway module is possible. There are some important limits, though:
- Stripe's documentation lists Afterpay as single-use with no recurring payments, and lists Zip as not supporting recurring payments either. Neither can be stored and charged automatically on renewal.
- Through Stripe, Afterpay is listed for B2C sales only, which rules out many business-to-business hosting customers.
- Both have transaction limits, so the option should only appear when an invoice falls within them.
That makes BNPL best suited to one-off or upfront invoices, such as annual plans, setup fees or project work, rather than monthly renewals. We cover this in detail in Afterpay and Zip in WHMCS: what's possible and what needs a custom module.
PayID and BPAY bank transfers
PayID and BPAY are bank payments, not card gateways. Customers pay from their banking app, so WHMCS never sees the payment. The usual approach:
- Show clear payment instructions on the invoice. For PayID, that's your registered PayID plus the invoice number as the reference. For BPAY, it's your biller code and a customer reference number (CRN) from your bank.
- Pull transactions from your bank, via a bank feed, export or bank API where your bank offers one.
- Match each payment to an open WHMCS invoice by reference and amount.
- Mark matched invoices as paid using the WHMCS API, and send anything unclear to a review queue.
How you build this depends on what data your bank makes available.
Quick comparison
| Payment method | WHMCS support | Automatic renewals | Notes |
|---|---|---|---|
| eWAY | Built-in module | Yes (token) | Australian gateway; migration path from eWAY Rapid 3.1 |
| Stripe cards | Built-in (Stripe Dynamic Payments) | Yes (token) | Uses restricted API keys; webhooks set up automatically |
| Stripe BECS Direct Debit | Built-in from v9.0.3 | Yes | AUD only; mandate required; results can take up to three business days |
| Pin Payments | Third-party module (Snapfrozen) | Yes (token) | Check version compatibility |
| Square | Third-party modules | Depends on module | Check tokenisation and refund support |
| Afterpay / Zip | Custom module needed | No | One-off invoices only; eligibility and transaction limits apply |
| PayID / BPAY | Manual by default | Not applicable | Automate with bank-data reconciliation |
How to choose the right mix
A sensible setup for most Australian WHMCS businesses is one tokenised card gateway (eWAY, Stripe or Pin Payments) for renewals, Stripe BECS for customers who'd rather not use a card, PayID or BPAY with automated matching, and BNPL only on one-off invoices where it fits.
Test in a staging copy of WHMCS first. Run an order, a renewal, a failed payment and a refund before going live.
How Berisco can help
Berisco builds and customises WHMCS for hosting providers and service businesses, including payment gateway modules, webhooks and billing automation. If you need a gateway WHMCS doesn't support, or want bank transfers matched automatically, see our WHMCS development services or request a quote.
Frequently asked questions
Does WHMCS support eWAY?
Yes. WHMCS includes a native eWAY module that uses token payments, so cards are stored with eWAY and renewals can be charged automatically. It supports one-time payments, recurring payments and refunds.
Can WHMCS take BECS Direct Debit payments in Australia?
Yes, through the Stripe Dynamic Payments module from WHMCS v9.0.3. You'll need BECS enabled on your Stripe account. Payments are in AUD and can take up to three business days to confirm.
Is there an official Pin Payments module for WHMCS?
Pin Payments points to a third-party module developed by Snapfrozen, which is listed on the WHMCS Marketplace. Check its version compatibility before installing it on a current WHMCS release.
Can customers pay WHMCS invoices with Afterpay or Zip?
Not out of the box. A custom module can connect to the Afterpay or Zip APIs, but neither supports automatic recurring charges. They suit one-off invoices better than monthly renewals.
How do I automate PayID and BPAY payments in WHMCS?
Get transaction data from your bank, match each payment to an open invoice by reference and amount, then mark it paid through the WHMCS API. Anything that doesn't match cleanly should go to manual review.
Which gateway is best for recurring hosting billing in Australia?
Any tokenised gateway with recurring support works well. eWAY and Stripe are both built into WHMCS, and Stripe BECS adds a bank-account option.
