Card payments through PayWay
Accept supported credit and debit card payments through the configured WHMCS gateway workflow.
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.
Accept supported credit and debit card payments through the configured WHMCS gateway workflow.
Support automated recurring billing for suitable services and authorised payment methods.
Use supported PayWay tokenisation features for payment-method references within the integration.
Configure supported settings and review available module transaction information through WHMCS.
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.
WHMCS PayWay integration for customers with an applicable Bank of Melbourne merchant facility.
WHMCS PayWay integration for customers with an applicable St.George merchant facility.
WHMCS PayWay integration for customers with an applicable Westpac merchant facility.
Pricing, licence duration, included updates, installation and support entitlements are confirmed for the selected module and current WHMCS environment.
Discuss a PayWay ModuleSubmit supported real-time card payment requests through the configured PayWay integration.
Support suitable recurring-payment workflows for subscription and service billing.
Use supported references supplied through the PayWay environment rather than storing raw card details in the module.
Configure and test the module using the applicable test environment before production activation.
Review module and WHMCS transaction information available for payment investigation and administration.
Configure supported currency options where the merchant facility and WHMCS environment permit.
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.
Confirm the installed WHMCS version, PHP environment, theme and relevant customisations.
Maintain an approved PayWay merchant facility for the selected financial-institution brand.
Obtain the applicable merchant identifier, API credentials and other required settings from the provider.
Confirm the available test credentials and production activation requirements.
Review current payment gateways, recurring services, stored methods and customer billing dependencies.
Prepare suitable WHMCS and database backups before installation or configuration changes.
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.
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.
Review WHMCS, PHP and module versions before upgrades or platform changes.
Review authorised credentials, test mode, card settings and transaction behaviour.
Understand active subscriptions, payment methods and customer billing dependencies.
Identify custom hooks, themes, modules and application changes that may affect the integration.
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.