E-commerce plugins
Blesta gateway
Install and configure the official Blesta gateway for hosted MakePay checkout on client invoices.
MakePay Blesta Gateway
The official MakePay Blesta gateway lets clients pay Blesta invoices through hosted crypto checkout. Blesta creates and owns the invoice. MakePay creates the checkout link and sends payment updates back to Blesta.
Recurring billing stays inside Blesta. When Blesta creates a renewal invoice, the gateway handles it like any other invoice payment.
Before You Start
You need:
- Blesta 5.x or newer
- HTTPS Blesta installation
- Administrator access to Blesta payment gateways
- MakePay settlement and branding configured
Install The Gateway
Download the latest package:
https://plugins.makecrypto.io/downloads/blesta/latest.zip
Extract the ZIP and upload the makepay folder to:
Blesta/components/gateways/nonmerchant/makepay
In Blesta, open Settings > Payment Gateways, choose Available, find MakePay, and install it as a non-merchant gateway.
Connect MakePay
Open the MakePay gateway settings in Blesta and click Connect MakePay.
The connection flow:
- Opens the MakePay connection page.
- Lets you choose the company that should receive payments.
- Returns you to Blesta after approval.
- Saves the gateway connection for this Blesta installation.
After connecting, create a small test invoice and pay it from the client area.
Manual API Key Fallback
Connect MakePay is the recommended setup. Manual API-key setup is available for stores that cannot complete the guided connection.
For manual setup, set connection method to Manual API key and enter:
- MakePay company ID
- API key ID
- API key secret
- Webhook signing secret
Keep the callback URL shown in Blesta reachable from the public internet.
Checkout Flow
When a client chooses MakePay for a Blesta invoice, the gateway:
- Reads the invoice amount, currency, client ID, and invoice metadata.
- Creates a hosted MakePay payment link.
- Shows a Pay with MakePay button.
- Sends the client to hosted checkout.
- Receives a signed callback when the payment status changes.
The payment link includes metadata such as:
| Field | Purpose |
|---|---|
source=blesta | Identifies the integration |
orderId=blesta_invoice_<invoiceId> | Maps MakePay activity back to Blesta |
invoiceId | Primary Blesta invoice ID |
clientId | Blesta client ID when available |
Invoice States
| MakePay status | Blesta behavior |
|---|---|
paid, completed, confirmed, succeeded | Records an approved transaction |
pending, waiting, confirming | Keeps the payment pending |
failed, expired, cancelled | Records a declined payment |
Blesta remains responsible for service activation and recurring billing automation after the invoice is paid.
Security Notes
Use HTTPS, keep Blesta administrator access limited, and disconnect the gateway from the MakePay dashboard if an administrator account or server backup is exposed. Reconnect after changing the Blesta domain so callback and return URLs match the live installation.
Troubleshooting
If Connect MakePay cannot start, confirm the Blesta callback URL is public and the gateway is installed as a non-merchant gateway.
If invoices do not update, check that the callback URL shown in settings is reachable and that the webhook signing secret is present.
If clients see a checkout error, confirm MakePay is connected and the selected invoice currency is supported by your MakePay setup.