E-commerce plugins
Invision Community gateway
Install and configure the official Invision Community 5 Commerce gateway with native OAuth, DPoP-bound tokens, hosted MakePay checkout, and signed webhooks.
MakePay Invision Community Gateway
Overview
The official MakePay Invision Community application adds hosted crypto checkout to Invision Community 5 Commerce. Commerce creates the invoice and transaction, MakePay creates the hosted payment link, and signed webhooks update the transaction after payment events.
Use Connect MakePay for normal setup. Manual API-key credentials remain available as a fallback.
Before You Start
- Invision Community 5.0 or newer
- Commerce application installed
- PHP 8.1 or newer
- HTTPS community URL
- A MakePay company where you can manage payment settings
Install The Application
Download the latest TAR package:
https://plugins.makecrypto.io/downloads/invision-community/latest.tar
Install it from the Invision AdminCP application manager.
Connect MakePay
Open Commerce payment settings and add MakePay as a payment method. Choose Connect MakePay. The application:
- Opens MakeCrypto in a browser tab.
- Asks you to sign in and choose the company that should receive payments.
- Shows the permissions needed by the Invision Community gateway.
- Returns you to Invision after approval.
- Saves the community connection in encrypted Invision settings.
- Configures the MakePay webhook callback URL.
Configure MakePay
Keep Connection Method set to the default connected mode after connection. Review:
- Payment method availability
- MakePay company ID
- Webhook callback URL
- Debug/request logging
- Manual API-key fallback credentials
Manual fallback requires a MakePay Company ID, API key ID, API key secret, and webhook secret.
Checkout Flow
When a member chooses MakePay, Invision creates a Commerce transaction and the application creates a MakePay payment link with invoice metadata.
| Field | Purpose |
|---|---|
source=invision | Identifies the integration |
externalId=invision_invoice_<id> | Maps MakePay activity back to Commerce |
invoiceId | Invision Commerce invoice ID |
transactionId | Invision Commerce transaction ID |
moduleVersion | Installed MakePay application version |
The member is redirected to hosted MakePay checkout and returns to the community after payment or cancellation.
Commerce States
The webhook endpoint verifies X-MakePay-Signature before changing Commerce
transaction state.
| MakePay status | Invision transaction state |
|---|---|
paid, completed, confirmed, succeeded | Approved |
failed, expired | Refused |
cancelled, canceled | Refused |
refunded | Refunded |
| Other statuses | Pending |
Each webhook writes a private invoice message with the MakePay status, payment UID, and hosted payment URL when available.
Security Notes
The application stores connection details in encrypted Invision settings. Keep AdminCP access limited to trusted operators, and disconnect the gateway in MakeCrypto if an administrator account or server backup is exposed.
The connection asks for these permissions:
company:readmakepay:payment-links:readmakepay:payment-links:writemakepay:customers:readmakepay:customers:writemakepay:settings:readmakepay:settings:write
Troubleshooting
If Connect MakePay cannot start, confirm the community base URL is HTTPS and publicly reachable. If checkout redirects fail, confirm Commerce is installed and MakePay has either a saved connection or manual API-key fallback credentials. If invoices do not update, compare the MakePay webhook callback URL with the community webhook URL and rotate the webhook secret.