WHMCS · Italy

Accept Nexi XPay
payments on WHMCS

Install the free PaymentHood module for WHMCS, connect your Nexi, through your bank account, and Nexi XPay appears as a payment option at checkout. No custom gateway code, and no second integration when you add another provider later.

  • EUR
WHMCS 8.0+
2 payment methods
Free module
WHMCS
Nexi XPay
Platform
WHMCS 8.0+
Provider
Nexi XPay
Install via
Apps & Integrations
Billing
One-time & recurring
PaymentHood fee
None
Compatibility

Nexi XPay on WHMCS at a glance

WHMCS version
WHMCS 8.0+
Where you install it
WHMCS admin → Apps & Integrations
Coverage
Merchants whose bank distributes Nexi XPay. Intesa Sanpaolo (as XPay Web), Banca MPS, BPER, Banca Mediolanum and Mediobanca Premier are among the banks that do. Your own terms come from the bank, not from Nexi.
Currencies
  • EUR
Billing models
One-time checkout and recurring renewals — WHMCS generates both, and the module handles both.
Cost
The module is free and open source. You pay Nexi, through your bank's own fees, published on their pricing page (opens in new tab). PaymentHood adds nothing on top.

Coverage, currencies and payment methods as published by Nexi, through your bank, who set and update them. For the current list see Nexi, through your bank's own documentation (opens in new tab).

Payment methods

What WHMCS customers can pay with

Each method Nexi XPay supports appears in your WHMCS checkout. Enabling one is a PaymentHood dashboard setting — nothing changes on the WHMCS side.

Cards

Visa, Mastercard, American Express and Diners, as enabled on your Nexi contract

Wallets and local methods

Nexi lists Apple Pay, Google Pay, PayPal, Bancomat Pay and MyBank among its circuits; what appears on the page depends on your contract

Setup

Connect Nexi XPay to WHMCS

Four steps, no code. The full walkthrough with screenshots is in the WHMCS installation guide.

1

Use your Nexi, through your bank account

Nexi XPay runs on your own Nexi, through your bank account. Register with Nexi, through your bank if you have no account yet, and turn Nexi XPay on in your Nexi, through your bank Dashboard. Funds settle from Nexi, through your bank to your own bank account.

2

Add it in PaymentHood

Paste your Nexi, through your bank credentials into the PaymentHood dashboard. They stay server-side and never reach your storefront.

3

Install the module

Download the WHMCS module and install it from Apps & Integrations in your WHMCS admin.

4

Enable and test

Paste your PaymentHood API key into the module settings, run a sandbox order end to end, then switch to live.

Why PaymentHood

Rather than a direct Nexi XPay module

A single-provider module works until you need a second provider. These are the parts you would otherwise build and maintain yourself.

Webhook security
Received on a PaymentHood URL that carries a per-profile secret key. Nexi does not sign its notification, so it is only read for which payment it concerns and is never trusted for the status
Payment verification
Server-side read-back of the order from Nexi before an order is marked paid, so the payment's real state always comes from Nexi rather than from the notification
Credentials
The merchant's XPay API key from their Nexi back office, held server-side in PaymentHood and sent only from PaymentHood's servers to Nexi. The hosted page language is a per-merchant setting and defaults to Italian
  • Add a second provider without touching your WHMCS checkout
  • Automatic failover when Nexi XPay is unreachable, instead of a failed order
  • Idempotent charge creation, so a double-submitted order is not a double charge
  • One reconciliation view across every provider you run
  • Free and open source — read the module on GitHub (opens in new tab)
FAQ

Frequently Asked Questions

Yes, and it normally comes from your bank rather than from Nexi directly. PaymentHood needs the XPay API key from your Nexi back office; it does not open Nexi accounts and is not party to your contract.

Intesa Sanpaolo (as XPay Web), Banca MPS, BPER, Banca Mediolanum and Mediobanca Premier are among the banks that distribute it. If you are not sure what sits behind your bank's e-commerce product, the acquirer is named in the merchant information sheet your bank gives you, the foglio informativo esercenti.

Euro (EUR). Other currencies depend on your own Nexi contract and PaymentHood does not offer them for XPay yet.

On a payment page hosted by Nexi. The buyer leaves your checkout, pays on Nexi's page and returns, which keeps card data off your server and off PaymentHood's. The page is shown in Italian unless you set another language.

Yes. A refund started in PaymentHood returns what is still refundable on the capture, and it settles asynchronously, so the final status arrives a little later. A partial refund is made in your Nexi back office rather than from PaymentHood, and it leaves the payment captured.

Not today. PaymentHood takes XPay as a one-off payment, so plan for paying each invoice as it comes due.

Yes. Nexi provides a test environment with test cards after you create a free developer account, and PaymentHood has a sandbox mode for XPay alongside it.

No. PaymentHood adds nothing to what your bank and Nexi charge: no percentage, no per-transaction cut, and no volume threshold where that changes. Your bank bills you directly and you keep that relationship. PaymentHood's only paid plan is Premium at $29 a month, which adds white-label checkout branding and nothing to your transaction cost. See PaymentHood pricing.

Accept Nexi XPay on WHMCS today

Free module, no PaymentHood transaction fee, and room to add another provider whenever you need one.