
*Last updated: 13 November 2026*

**Short answer:** PayID and BPAY are bank transfers, not card gateways, so WHMCS never sees the payment land. Automation means pulling transactions from your bank (CSV, feed or API), matching each one to an open invoice by reference and amount, then marking it paid with [AddInvoicePayment](https://developers.whmcs.com/api-reference/addinvoicepayment). Anything that does not match cleanly goes to a review queue, not straight onto the invoice.

It's Tuesday morning. Three "when will my service be unsuspended?" tickets sit in your hosting inbox.

You check the bank. The money is there — three PayID transfers, invoice numbers in the descriptions, amounts that match.

You open WHMCS. All three invoices still say **Unpaid**.

That gap — money in the bank, status still Unpaid — is the problem this guide solves. Not "how do I accept PayID?" You already can. The question is how you stop matching bank lines by hand every morning while services hang and cash sits unused.

## Why PayID and BPAY aren't gateways in WHMCS

Card gateways sit inside WHMCS: the customer pays on the invoice page, the provider returns a result, and WHMCS records it. PayID and BPAY work outside that loop. The customer pays in their banking app. Your bank credits your account. WHMCS knows nothing until someone (or something) tells it.

That is why the useful work is **reconciliation**, not installing another gateway module. For the broader Australian gateway picture, see our [Australian payment gateways for WHMCS](/whmcs/australian-payment-gateways) guide. This post stays on the matching pipeline only. If you also offer buy now, pay later on one-off invoices, see [Afterpay and Zip in WHMCS](/blog/whmcs-afterpay-zip).

## What PayID and BPAY are (briefly)

**PayID** is an easy-to-remember identifier — such as an email, mobile number or organisation identifier — linked to a bank account. [Australian Payments Plus PayID FAQs](https://www.auspayplus.com.au/solutions/payid-faqs) note that payments typically move fast through Osko, often in under a minute, and the payer sees the registered name before they send. Unique email-style PayIDs per payment can make matching easier where your bank offers them — [check with your bank](https://www.nab.com.au/business/online-banking/payid).

**BPAY** is Australia's bill-payment rail. You register as a biller, then show a Biller Code and Customer Reference Number (CRN) on each invoice. Funds and digital payment information typically arrive on the next banking business day, which makes CRN-based reconciliation practical. CRNs can identify an account or a single bill, and check digits reduce mistypes — see the [BPAY support pages](https://www.auspayplus.com.au/solutions/bpay-support) and [check with your bank](https://www.nab.com.au/business/payments-and-merchants/merchant-support-centre/bpay-how-it-works).

Some banks sell branded PayID biller products. Treat those as bank-specific offerings, not universal features.

## The reconciliation pipeline

### 1. Put a matchable reference on every invoice

- **PayID:** ask customers to put the WHMCS invoice number in the payment description. Keep the wording identical on every notice.
- **BPAY:** print your Biller Code and a CRN that maps to the invoice. Agree the CRN scheme with your bank so check digits and length are valid.

Without a clear reference, automation fails.

### 2. Pull bank data

You need credits with date, amount, reference or description, and a bank transaction identifier. Common sources are a daily CSV export, a bank feed via accounting software, or a bank API where one exists. What you can pull and how often is **bank-dependent** — confirm formats and cut-offs with your bank before you design the matcher.

### 3. Match by reference and amount

For each credit: normalise the reference; find open invoices whose invoice number or CRN matches; confirm the amount equals the balance (or a defined partial rule); skip Cancelled invoices; and if anything is ambiguous, queue it. Matching on amount alone is dangerous. Matching on reference alone invites wrong allocations.

### 4. Mark paid with AddInvoicePayment

Call [AddInvoicePayment](https://developers.whmcs.com/api-reference/addinvoicepayment). Required fields: `invoiceid`, `transid` (unique), `gateway`, and `date` as `YYYY-MM-DD HH:mm:ss`. `amount` is optional. Authenticate per the [WHMCS API authentication docs](https://developers.whmcs.com/api/authentication) with identifier/secret credentials on an admin that has API Access.

**Unique `transid` matters.** Use the bank's transaction ID (or a stable hash of date + amount + reference + bank id) so a re-imported file cannot double-apply the same payment.

```text
AddInvoicePayment(
  invoiceid = matched WHMCS invoice,
  transid   = bank transaction id (unique),
  gateway   = your bank-transfer gateway name,
  date      = payment datetime from the bank,
  amount    = matched amount (optional)
)
```

### 5. Review queue for exceptions

Send unclear rows to a human: no matching invoice, amount mismatch, already Paid or Cancelled, duplicate bank id, or partials without a rule. A short daily exceptions list beats chasing every transfer.

## Reference design

**PayID:** one house rule — bare invoice number as the description. If your bank offers unique email-style PayIDs per receivable, that can encode the invoice in the PayID itself; availability is a bank question.

**BPAY:** Biller Code identifies you; CRN identifies the bill. A **variable CRN per invoice** (plus a bank-approved check digit) usually reconciles cleanest. Confirm the algorithm with your bank before generating CRNs in WHMCS. Do not invent bank product claims — each institution packages tools differently.

## Quick-win checklist

- [ ] Fix PayID description wording on every unpaid-invoice notice
- [ ] Confirm BPAY Biller Code and CRN scheme with your bank
- [ ] Pick a bank data source and daily pull schedule
- [ ] Create a dedicated WHMCS gateway name for bank transfers
- [ ] Generate API credentials with minimum needed permissions
- [ ] Define match rules: exact amount, open status, unique `transid`
- [ ] Build an exceptions queue
- [ ] Test in staging: clean match, wrong amount, missing reference, duplicate import
- [ ] Document who reviews the queue each morning

> **Still matching bank transfers by hand?** Berisco builds WHMCS automation for Australian hosting providers — invoice instructions, bank-feed matching and API payment posting with a review queue. [Book a free consultation](/get-a-quote) and we'll map what your bank can export to a safe reconciliation flow.

## What this looks like in practice

**For example, imagine a small Australian hosting provider** with a few hundred monthly WHMCS invoices. Many customers prefer PayID or BPAY. Every weekday someone opens the bank CSV, searches WHMCS, and clicks Add Payment. Renewals slip when that person is away. Suspensions fire on accounts that already paid.

They fix invoice instructions, schedule a job that matches yesterday's credits on reference + amount, and call AddInvoicePayment with the bank transaction id as `transid`. Odd rows land in a review queue. Within a week the morning chase is a short exceptions list. (This is a labelled illustration, not a real client result.)

## Common mistakes

- Expecting WHMCS to detect bank transfers like a card module
- Vague instructions so customers invent their own references
- Matching on amount only when two invoices share a price
- Reusing transaction IDs so a re-import double-pays
- Auto-applying partials without rules
- Skipping the review queue
- Hard-coding one bank's export format as if all banks match

## How Berisco can help

Berisco customises WHMCS for Australian hosting and subscription businesses: PayID and BPAY instructions, bank-feed matching, AddInvoicePayment automation, and exception queues your team can trust.

Want bank transfers to update WHMCS the same day the money lands? See [WHMCS for Australian hosting providers](/services/whmcs-for-australian-hosting-providers), [WHMCS development](/services/whmcs-development), or [request a quote](/get-a-quote).

## Frequently asked questions

### Can WHMCS take PayID or BPAY automatically out of the box?
No. They are bank transfers outside the WHMCS checkout loop. WHMCS learns about the payment when you (or automation) record it, usually via AddInvoicePayment after matching bank data.

### What is the safest way to match bank transfers to WHMCS invoices?
Match on a clear reference (invoice number for PayID, CRN for BPAY) **and** the expected amount, then post with a unique bank transaction id. Send unclear rows to manual review.

### Which AddInvoicePayment fields are required?
`invoiceid`, `transid`, `gateway` and `date` (`YYYY-MM-DD HH:mm:ss`) are required. `amount` is optional. Use a unique `transid` so the same credit cannot be applied twice.

### Does every Australian bank offer the same PayID or BPAY tools?
No. Products, file formats and APIs vary. Check with your bank for PayID options, BPAY biller setup, CRN rules and how you can export or pull transactions.

### Should PayID and BPAY replace card gateways for hosting renewals?
Usually not. Cards and direct debit still suit automatic renewals. Automate PayID/BPAY reconciliation so preferred bank payments do not create unpaid backlog. Keep a tokenised gateway for recurring charges — see the [Australian payment gateways for WHMCS](/whmcs/australian-payment-gateways) guide.

### How do Afterpay or Zip fit next to PayID and BPAY?
Different products. BNPL needs a custom module and does not support automatic recurring charges. PayID/BPAY need bank reconciliation. See [Afterpay and Zip in WHMCS](/blog/whmcs-afterpay-zip).
    

Automate PayID and BPAY in WHMCS: pull bank data, match invoice references by amount, and mark invoices paid with AddInvoicePayment.

WHMCS PayID BPAY Bank Transfer Automation

Automating PayID and BPAY Payments in WHMCS: A Reconciliation Guide


*Last updated: 13 November 2026*

**Short answer:** A WHMCS IPTV module is a provisioning module that turns billing events into panel actions. After payment, WHMCS calls [CreateAccount](https://developers.whmcs.com/provisioning-modules/supported-functions/) on your panel (for example XUI One or Xtream UI), then your welcome email can send credentials. Overdue invoices drive [SuspendAccount](https://developers.whmcs.com/provisioning-modules/supported-functions/); payment restores the line; renewals extend expiry. Berisco only builds this for operators who hold rights to the content they distribute.

It's Friday afternoon. Three new paid orders sit in WHMCS as Active — or worse, as Pending.

Nobody has created the lines on the panel yet.

Support tickets start: "I paid. Where are my login details?" Someone opens the panel admin, copies a username, pastes it into an email, and hopes the package and bouquet match what the customer bought.

That gap — money received, service not live — is what order-to-activation automation closes. Not "how do I accept card payments?" You already can. The question is how a paid order becomes a working line, a welcome email, and a renewals path that does not depend on who is in the office.

**Important:** this guide is for **licensed** IPTV and OTT operators only — hospitality TV integrators, community and multicultural broadcasters, and authorised resellers of licensed services. Berisco does not work with unlicensed IPTV sellers. Australia's copyright framework includes civil remedies and a Federal Court [site-blocking scheme under section 115A of the Copyright Act](https://www.copyright.org.au/browse/book/ACC-Site-Blocking-&-Copyright-Infringement-INFO129); [IP Australia](https://www.ipaustralia.gov.au/tools-and-research/professional-resources/data-research-and-reports/australian-ip-report-2026/copyright/use-of-copyright-content) summarises how owners enforce rights. We ask for evidence of licence or authorised-reseller status before any project starts.

## What "WHMCS IPTV module" actually means

WHMCS does not ship an IPTV product. It bills and provisions "just about any service" through a **server/provisioning module** under `modules/servers/`. The module maps WHMCS product events to your panel's API (or equivalent access method).

On a clean install you still need:

1. A panel your customers actually use (package, bouquets, connection limits, expiry).
2. A WHMCS module built for **that** panel — a module for XUI One does not drive Xtream UI.
3. Products in WHMCS whose Module Settings point at the right panel package.
4. Automation Settings so overdue and paid events fire without a human click.
5. Email templates that send credentials after provisioning succeeds.

Miss one and you are back to copying lines by hand.

## The order-to-activation flow

### 1. Order and payment

The customer picks a plan on your order form (or client area upgrade). WHMCS creates the order and invoice. Payment lands through your gateway — card, tokenised renewals, or another method you already support. Until the invoice is Paid (or the order is accepted under your free-trial rules), provisioning should not run.

### 2. Provisioning via the panel API

When WHMCS is ready to provision, it calls the module's **CreateAccount** function. Per the [supported functions docs](https://developers.whmcs.com/provisioning-modules/supported-functions/), that runs on checkout/payment for a new order, or when an admin triggers Module Commands.

A solid CreateAccount path should authenticate with credentials scoped to WHMCS (not a shared personal admin login), create the line with the package, bouquets and connection limit from Module Settings, store username/password or device identifiers on the service, and fail into the Module Log if the panel rejects the request. Run Test Connection on the server entry before you sell anything live.

### 3. Welcome email with credentials

Once CreateAccount succeeds, WHMCS can send your product welcome email with credentials and setup steps — server URL, username, password, M3U link if you offer one, and a short sign-in block. Customers should not wait for a human to paste anything. If CreateAccount fails, do **not** pretend the service is live: fix the Module Log error, then retry Module Commands.

### 4. Renewals, suspension and termination

Paid renewal invoices should call **Renew** so panel expiry stays aligned with the WHMCS Next Due Date. Overdue invoices should call **SuspendAccount**; payment should call **UnsuspendAccount**. Long-overdue services can call **TerminateAccount** when enabled.

Those behaviours only run on schedule if [Automation Settings](https://docs.whmcs.com/8-13/system/automation/automation-settings/) are correct: Enable Suspension with Suspend Days, Enable Unsuspension, and optionally Enable Termination with Termination Days. The system cron must run reliably (self-hosted installs need it at least every five minutes). Services you suspend by hand with a custom reason are **not** auto-unsuspended on payment. Paid upgrades should hit **ChangePackage** so the panel matches what the customer now pays for.

## Quick-win checklist

- [ ] Confirm you hold rights (or authorised-reseller status) for every package you sell
- [ ] Pick one panel and one WHMCS module built for that panel — do not mix
- [ ] Add the panel under System Settings → Servers; run Test Connection
- [ ] Map each WHMCS product to the correct panel package, bouquets and connection limit
- [ ] Turn on Module Logging and run Create / Suspend / Unsuspend / Renew / Terminate once in staging
- [ ] Enable Automation Settings for suspension and unsuspension; set Suspend Days deliberately
- [ ] Rewrite the welcome email so credentials and setup steps go out automatically
- [ ] Restrict panel API credentials to the WHMCS server (IP allow-list where the panel supports it)
- [ ] Document who watches failed Module Log rows each morning

> **Still creating IPTV lines by hand after every paid order?** Berisco builds WHMCS IPTV billing automation for **licensed** Australian operators — panel provisioning, welcome emails, renewals and suspension sync. [Book a free consultation](/get-a-quote) and we'll map your panel to a safe order-to-activation flow.

## What this looks like in practice

**For example, imagine a licensed hospitality IPTV integrator** selling room and venue packages through WHMCS. Sales close in the evening; someone used to open the panel, create each line, and email logins the next morning while paid invoices sat idle.

They install a panel-specific module, map each product to a package, enable CreateAccount on payment, and put credentials in the welcome template. Overdue venue accounts suspend on the cron; payment restores them. The morning job shrinks to a Module Log exceptions list. (This is a labelled illustration, not a real client result.)

## Common mistakes

- Buying a module for the wrong panel and expecting it to "just work"
- Leaving products on Manual provisioning so paid orders never call CreateAccount
- Sending the welcome email before provisioning succeeds
- Skipping Automation Settings, then wondering why overdue lines stay active
- Sharing one panel admin login across staff and the WHMCS server
- Auto-terminating too early without a clear commercial policy
- Writing marketing copy that hints at unlicensed content or "avoiding blocks" — that puts payment accounts and the business at risk
- Ignoring Module Log failures until customers complain

## How Berisco can help

Berisco customises WHMCS for licensed IPTV and OTT operators: panel provisioning, product mapping, welcome emails, and renewals/suspension automation. We only take on operators who can show rights to the content they distribute.

Want paid orders to activate the same day the money lands? See [WHMCS IPTV billing automation](/services/whmcs-iptv-billing-automation), [WHMCS development](/services/whmcs-development), or [request a quote](/get-a-quote).

## Frequently asked questions

### Does WHMCS include a built-in IPTV module?
No. WHMCS provisions IPTV through a third-party or custom server module that talks to your panel. You still use WHMCS for orders, invoices, the client area and automation.

### Which panels can connect to WHMCS?
Common licensed-operator setups use panels such as XUI One or Xtream UI, each with its own module and connection method (API key, admin API, or another panel-specific path). Match the module to the panel you actually run — do not assume one module covers every fork.

### What happens after a customer pays?
On a correctly configured product, WHMCS calls CreateAccount, the panel creates the line, credentials are stored on the service, and your welcome email can send. If CreateAccount fails, fix the error from the Module Log and retry — do not email fake credentials.

### How do renewals and overdue invoices affect the panel?
Paid renewals should call Renew so expiry extends. Overdue services can SuspendAccount after Suspend Days; payment can UnsuspendAccount. Termination is optional and controlled in Automation Settings. Confirm your cron is healthy via [Automation Status](https://docs.whmcs.com/8-13/system/automation/automation-status/).

### Will Berisco work with any IPTV reseller?
No. We only work with operators who hold rights or authorised-reseller status for the content they distribute. We do not build or support unlicensed IPTV services.

### Is this the same as recurring subscription dunning?
Related, but different. This post covers order → provision → renew/suspend. Failed-card retries, trial conversion and dunning copy belong in a separate billing-ops conversation once activation is solid.
    

Connect WHMCS to your IPTV panel so paid orders create lines, welcome emails send, and renewals or suspensions stay in sync — for licensed operators only.

WHMCS

Automating PayID and BPAY Payments in WHMCS: A Reconciliation Guide

WHMCS for Licensed IPTV and OTT Providers: Automating Order to Activation

Australia

United Kingdom

Pakistan