Connect checkout, renewals and payment operations.

Yes. The Paystack Advanced module is available free. It includes the checkout and gateway experience, saved payment methods, item-level renewal controls and the payment operations workspace. Your Paystack merchant account and payment processing follow the terms of your Paystack service.

Customers use Paystack-hosted card entry or another payment channel available to your setup. Returning customers can choose an eligible saved method. The checkout keeps the invoice context visible, follows any required authorization step and checks the resulting payment against its reference.

Eligible reusable card authorizations from successful payments can be stored as native WHMCS payment methods when saving is enabled. Customers can review their methods, select a default and remove a method. Their service, addon and domain renewal preferences remain separately visible.

Customers manage the eligible hosting services, addons and domains they want to renew automatically. Before scheduled capture, the gateway checks the payable recurring items across the invoice and the available saved method. A customer can also return to the invoice for a present-customer payment.

Paystack Advanced processes payments in NGN. The original WHMCS invoice retains its own currency and amount, with WHMCS conversion used where needed. Checkout can explain the NGN processing value, and the operations views preserve both the payment and invoice context.

The operations workspace brings together the payment ledger, reference detail, invoice and processor information, activity, exceptions and case notes. Staff can verify an existing reference, review analytics and export filtered information according to their assigned permissions.

Yes. Set the brand name, icon, payment labels, status wording and overlay appearance from the operations workspace. Native WHMCS email templates cover payment follow-up, authorization steps and missing methods, so the customer communication can follow your business’s wording and presentation.

Use the visible Changelog to read the module’s published releases, including their dates, new capabilities, improvements and fixes. The page shows the current published version and provides the free acquisition destination alongside the product guidance.

An attempt that has already been recorded retains its original payment reference. Browser checks, signed payment notifications, scheduled follow-up and staff verification can return to that same attempt. The billing team can inspect its recorded progress and invoice context to establish the outcome, even when the customer did not see a final checkout message.

Yes. Paystack Operations includes verification of an existing payment reference. That check follows the recorded attempt and its processor result, giving staff the invoice, accounting and activity context needed for follow-up. An operator can also add a case note so the next person reviewing the payment can see what has already been investigated.

The payment engine checks the processor reference, amount, currency, customer and invoice context before recording a successful result in WHMCS. Existing-transaction checks keep the accounting tied to the original attempt. Payments that are still pending or need review remain distinguishable in the operations workspace for the team's follow-up.

The operations views distinguish pending attempts, payments requiring review and recorded-payment outcomes. Staff can open the reference to inspect the processor result, invoice context, payment notifications and activity. This gives the team evidence for deciding the next step when a customer asks about an unresolved payment.

Yes. Analytics bring together payment attempts, recorded outcomes, pending work and review counts for the period you select. Daily charts show activity over time, while payment-source comparisons and currency views add context. Staff can move into the payment ledger when a pattern needs closer investigation.

Staff with export permission can use the payment ledger's filters and export the resulting records as CSV. This keeps a follow-up list focused on the payment activity being reviewed. The individual references remain available in the operations workspace with their invoice, processor and accounting details.

The analytics workspace includes saved-card coverage, expiry information and attachment-health views. These help the team understand the methods available for future collections and identify records needing attention. Automatic collection still depends on a usable saved method and the eligibility of the payable recurring items on the invoice.

Yes. The administration tools provide separate staff permissions for viewing payment information, performing supported operations and exporting records. You can assign access around each person's billing responsibilities. That lets the team share the payment context while keeping operational and export access under your chosen staff policy.

Yes. Setup distinguishes test and live credentials and includes controls for enabling live payment processing. The health view brings the active mode, NGN conversion, saved-method setup and scheduled activity into one place. You can review those settings and follow a representative invoice payment while preparing the gateway for your business.

A saved method requires a verified reusable card authorization from a successful payment, with saving enabled in your setup. An alternative channel being available at checkout does not itself supply that authorization. Returning customers can use a saved method only when it meets the gateway's eligibility requirements.

The gateway checks the payable recurring items across the whole invoice before scheduled capture. Automatic collection proceeds only when that invoice and the saved method meet the eligibility requirements. Customers can still return to the invoice and complete a present-customer payment through the checkout options available to your setup.

Configured retry limits and native WHMCS action emails support the follow-up. Messages can explain a payment problem, a required authorization step or a missing payment method and direct the customer to the invoice or payment settings. The customer can then take the appropriate action while staff retain the original payment context in Operations.