PrestaShop guide
Add crypto payments to PrestaShop with MakePay
The MakePay PrestaShop module gives merchants a hosted crypto checkout path while preserving PrestaShop order states, shop context, and multistore-friendly configuration.
PrestaShop merchants care about stable order state transitions, multistore settings, and a module package that can be uploaded cleanly. The MakePay module is built around that shape: a payment option at checkout, a MakePay payment link behind it, and webhook-driven order updates.
Connect MakePay is the default connection path. The module links the shop to the selected MakeCrypto company and saves the webhook settings needed for payment-link creation and order updates.
Checkout and order-state model
When a shopper chooses MakePay, the module creates a PrestaShop order in an awaiting-payment state and redirects to hosted MakePay checkout. Payment metadata includes cart, order, customer, and module version information.
The signed webhook controller verifies MakePay signatures and updates the order state to paid, failed, cancelled, expired, or refunded according to the payment event.
Why multistore handling matters
PrestaShop stores can run multiple shop contexts. The MakePay module stores settings per shop context so one shop does not accidentally reuse another shop’s connection.
This keeps callback URLs, webhook secrets, and fallback API keys scoped to the right storefront.
Testing before production
Run one small order through checkout, confirm the redirect, and inspect the private order message written by the module. It should include enough payment details for support to answer customer questions.
After the test, disconnect and reconnect the app once to confirm the recovery path before using the module for live traffic.
FAQ
Does MakePay support PrestaShop multistore?
The module is structured to store credentials per shop context, which is the safer model for multistore deployments.
Where is the PrestaShop ZIP generated?
The ZIP is built during the plugins.makecrypto.io Vercel build and uploaded to Supabase Storage when the source hash changes.