InSales connects not through a plugin but through a small Node.js relay service: the store sends the buyer to its address, the service creates the payment in MulenPay, and after payment it records the transaction on the InSales order.
How the flow works
- The buyer places an order and picks MulenPay as the payment method.
- InSales redirects them to your service at
/payments/paywith the order parameters. - The service creates the payment in MulenPay and redirects the buyer to the payment page.
- After payment MulenPay posts a notification to
/webhooks/mulenpay. - The service creates a transaction on the matching InSales order.
The link between payment and order rests on the InSales order id — it is passed in the uuid field when the payment is created.
What you need to run it
- A server with Node.js 18 or newer, reachable from the internet over HTTPS.
- MulenPay credentials: API key, shop id and the signing secret.
- InSales API credentials: store domain, key and application password.
What to keep in mind
The service is a separate application, not a store extension: it has to live somewhere and stay up. If it goes down, buyers cannot reach the payment page, and notifications about payments already made never reach the orders.
For simpler cases look at the payment API directly or at payment links — neither needs a server of your own.
