All guides

Wix guide

Add crypto payments to Wix with MakePay Velo files

The MakePay Wix connector uses Velo backend files and a payment-provider package so Wix merchants can create hosted MakePay checkout links from Wix orders.

Wix7 min readUpdated 2026-04-27

Wix payment customization is code-file based rather than a traditional plugin ZIP. MakePay provides Velo backend files and payment-provider files that merchants copy into the Wix editor.

The Wix code creates MakePay payment links, stores required settings in Wix Secrets Manager, and receives signed payment updates through a backend HTTP function.

How Wix differs from self-hosted CMS platforms

Wix does not expose the same server filesystem as WordPress or Magento. Instead, MakePay’s Wix integration is a set of Velo files that implement the payment-provider behavior expected by Wix.

This model keeps the integration copyable and auditable while still letting MakePay host the actual crypto checkout experience.

Secrets and callbacks

Credentials should be stored in Wix Secrets Manager, not hard-coded inside public page code. The backend HTTP function verifies signed MakePay payment notifications before updating payment status.

Because Wix sites can be edited by multiple collaborators, restrict who can view or change secrets.

When Wix is a good fit

The Wix connector works best for stores that already use Wix and want a guided MakePay payment option without moving commerce systems.

If you need deep backend automation, consider MakePay API routes or SDKs in a separate server application.

FAQ

Is the Wix connector a normal plugin ZIP?

No. It is a Velo code package that merchants add to the Wix editor.

Where should Wix credentials be stored?

Use Wix Secrets Manager for API keys, webhook secrets, and any private MakePay configuration.