WHMCS MPGS Payment Gateway

It connects WHMCS to Mastercard Payment Gateway Services for card payments, with Direct Pay and tokenised modes, optional Direct Pay 3-D Secure, refund support, checkout branding and gateway diagnostics.

Yes. Your bank or payment provider must supply the MPGS gateway hostname, merchant ID and API credentials. Confirm that the account supports the payment operations and optional capabilities you intend to use.

No. Configuration is based on the MPGS host and merchant credentials supplied by your provider. For any Australian or overseas provider, confirm the required API version, payment operations, currency and enabled merchant capabilities before using the module.

Direct Pay requires customers to enter card details for each payment. The optional 3-D Secure setting applies to this mode in the current module.

With Tokenised selected, the first successful payment creates a stored token and later payments can use the saved card. Your acquirer must enable tokenisation for the merchant account.

The configured tokenised workflow uses a stored token for subsequent payments. A token is a payment reference rather than a full card number. Follow the module and WHMCS documentation for your installation’s storage and payment configuration.

Yes, optionally for Direct Pay. The merchant must support 3DS, the callback URL must be reachable, and an issuer challenge or redirect is used when required. Enable and test it with your provider’s configuration.

No. The current module settings explicitly apply the 3DS flow to Direct Pay only. Stored-card/tokenised payments do not use that flow.

Yes. The module supports full and partial refunds from WHMCS, including multiple partial refunds against an invoice. Refund approval and processing remain subject to your merchant provider’s rules.

Yes. Settings include Generic (MPGS) branding, bank presets, a custom name and logo URL, checkout help text and a Powered by MPGS toggle.

The WHMCS Gateway Transaction Log shows timestamps, the gateway, diagnostic data and results. Invoice/client references help staff investigate outcomes. Card/token fields are excluded or sanitised; review any exported logs for customer and merchant details before sharing.

Use debug logging when you need additional diagnostics and review your normal production logging policy after troubleshooting. The module settings describe sanitised output, but logs can still contain invoice or client references.

Leave SSL certificate verification enabled in production. The Disable SSL Verification option is for testing or troubleshooting; resolve certificate/connectivity issues before taking live payments.

Yes. Obtain test credentials or a sandbox account from your provider, configure the appropriate host and version, and test payments, invoice results, refunds and any enabled authentication or tokenisation features before switching to production.

Do not assume that existing MiGS tokens can be reused with MPGS. Confirm migration options with your provider and plan for customers to re-enter card details where required. Snowtech can assist with testing, cutover and customer communications.

Check the current release’s installation guide for its supported WHMCS/PHP versions and ionCube Loader requirements. The gateway also needs valid merchant credentials and outbound connectivity to the configured MPGS host.

No. Module licence pricing is separate from merchant account, processing and other charges set by your bank or payment provider.

Leased pricing is $14.95 AUD per month or $149 AUD per year, with updates while subscribed. The owned licence is $349 AUD as a one-time purchase, including 12 months of updates. Further update access is $59 AUD per year.

No. The update renewal is optional. You can continue using your licensed version without renewing updates; $59 AUD provides another 12 months of update access.

A 30-day refund is available on new licences, excluding installation and custom work. Refer to the current Snowtech purchase terms for applicable conditions.