WHMCS Applications

Payment Gateway Solutions

PayWay payment gateway modules developed for supported WHMCS billing environments.

KernWi-Fi supplies supported integration software and technical services for Bank of Melbourne, St.George and Westpac PayWay merchant facilities.

Merchant approval, payment processing, settlement and banking services remain subject to the applicable financial institution and PayWay arrangements.

WHMCS integration

Payment applications for supported billing environments

The KernWi-Fi PayWay modules are designed to connect supported WHMCS billing environments with an applicable PayWay merchant facility. The modules support payment workflows inside WHMCS while the financial institution and PayWay platform provide the underlying merchant and payment-processing services.

Real-time payments

Card payments through PayWay

Accept supported credit and debit card payments through the configured WHMCS gateway workflow.

Recurring billing

Subscription payment workflows

Support automated recurring billing for suitable services and authorised payment methods.

Tokenised methods

Reduce direct handling of card details

Use supported PayWay tokenisation features for payment-method references within the integration.

Administration

Configuration and transaction records

Configure supported settings and review available module transaction information through WHMCS.

Available integrations

PayWay modules for three merchant brands

Each module is intended for customers with an applicable PayWay merchant facility and the credentials required for that merchant environment. Final compatibility and configuration are confirmed before installation.

PayWay Module Bank of Melbourne PayWay module for WHMCS

Bank of Melbourne

WHMCS PayWay integration for customers with an applicable Bank of Melbourne merchant facility.

  • Real-time card payment workflow
  • Recurring billing support
  • Supported tokenised payment methods
  • Test and production configuration
  • Administrative settings and transaction records
PayWay Module St.George PayWay module for WHMCS

St.George

WHMCS PayWay integration for customers with an applicable St.George merchant facility.

  • Real-time card payment workflow
  • Recurring billing support
  • Supported tokenised payment methods
  • Test and production configuration
  • Administrative settings and transaction records
PayWay Module Westpac PayWay module for WHMCS

Westpac

WHMCS PayWay integration for customers with an applicable Westpac merchant facility.

  • Real-time card payment workflow
  • Recurring billing support
  • Supported tokenised payment methods
  • Test and production configuration
  • Administrative settings and transaction records

Pricing, licence duration, included updates, installation and support entitlements are confirmed for the selected module and current WHMCS environment.

Discuss a PayWay Module
Module capabilities

Functions supporting WHMCS payment workflows

Payment capture

Submit supported real-time card payment requests through the configured PayWay integration.

Recurring transactions

Support suitable recurring-payment workflows for subscription and service billing.

Payment-method tokens

Use supported references supplied through the PayWay environment rather than storing raw card details in the module.

Test mode

Configure and test the module using the applicable test environment before production activation.

Transaction records

Review module and WHMCS transaction information available for payment investigation and administration.

Multi-currency settings

Configure supported currency options where the merchant facility and WHMCS environment permit.

Implementation requirements

Prepare the WHMCS and merchant environments

The integration requires a supported WHMCS installation, an appropriate PayWay merchant facility and authorised technical access. Compatibility should be confirmed before a module is installed or an existing payment workflow is changed.

Supported WHMCS environment

Confirm the installed WHMCS version, PHP environment, theme and relevant customisations.

Merchant facility

Maintain an approved PayWay merchant facility for the selected financial-institution brand.

Merchant credentials

Obtain the applicable merchant identifier, API credentials and other required settings from the provider.

Test and production access

Confirm the available test credentials and production activation requirements.

Existing gateways

Review current payment gateways, recurring services, stored methods and customer billing dependencies.

Backup and rollback

Prepare suitable WHMCS and database backups before installation or configuration changes.

Implementation process

From environment review to production activation

  1. Environment reviewConfirm WHMCS, PHP, merchant facility, existing gateways and project requirements.
  2. Module licensing and supplyConfirm the selected PayWay module, licence and applicable service scope.
  3. InstallationInstall the module in the approved WHMCS environment where installation is included.
  4. Test configurationApply authorised test credentials and configure the supported module settings.
  5. Payment testingTest agreed payment, recurring-billing and administrative workflows.
  6. Production activationApply production credentials and complete the agreed handover and support process.
Responsibility boundaries

Clear roles across software, merchant services and billing

KernWi-Fi

Module and integration services

  • Module licensing and supply
  • Installation where purchased
  • Supported module configuration
  • Module-related technical support
  • Updates according to the purchased licence
Customer

WHMCS and merchant administration

  • Valid merchant facility and credentials
  • Authorised WHMCS and server access
  • Transactions, refunds and customer billing
  • Administrative-account security
  • Applicable PCI DSS assessment and obligations
Bank and PayWay provider

Merchant and processing services

  • Merchant acceptance and facility terms
  • Payment processing and approval
  • Settlement and banking services
  • Chargebacks and merchant fees
  • Gateway platform availability
Security and PCI DSS

Tokenisation supports security but does not replace merchant obligations

The modules use supported PayWay tokenisation features to reduce the handling of payment-card details within WHMCS. Payment processing, tokenisation and merchant services are provided through the applicable PayWay and financial-institution arrangements.

Merchants remain responsible for assessing and meeting their applicable PCI DSS obligations, securing WHMCS and administrator accounts, maintaining supported software, and following the requirements of the merchant facility and payment provider.

Existing installations

Review an existing WHMCS payment environment

An existing installation may require review before WHMCS, PHP, hosting or payment settings are changed. The assessment can identify current module files, licence status, customisations, credentials, recurring-payment dependencies and upgrade considerations.

Version compatibility

Review WHMCS, PHP and module versions before upgrades or platform changes.

Gateway configuration

Review authorised credentials, test mode, card settings and transaction behaviour.

Recurring services

Understand active subscriptions, payment methods and customer billing dependencies.

Customisations

Identify custom hooks, themes, modules and application changes that may affect the integration.

Next step

Discuss the WHMCS and PayWay requirements

Tell us which PayWay merchant facility is used, the current WHMCS and PHP versions, existing payment gateways, recurring-billing requirements and whether installation or migration assistance is required.