Custom integration

When no plugin fits — integrate the E-comm API directly. This page is the orientation map.

When to build custom

• You run on a platform with no official miaPOS plugin (e.g. Magento, Shopify, custom CMS).
• You need behaviour beyond what the plugin exposes (custom callback handling, multi-currency routing, split payments).
• You're building a SaaS/marketplace and need a multi-tenant integration.

Reading order

1. E-commerce checkout — the protocol overview.
2. Authentication — token/refresh dance.
3. E-comm API reference — endpoint and schema reference.
4. Webhooks — handle the signed callback correctly.
5. Signature verification — the cryptography step.

Reference paths

The single best entry point is the integration repo on GitHub: finergy-tech/mia-pay-ecomm-integration. It contains the protocol overview, the signature-verification guide (with Java and Python reference implementations), and links to every official plugin and SDK.

• If your stack is PHP — start with the open-source PHP SDK. It covers token, pay, callback verification end-to-end; copy what you need and adapt.
• If your stack is something else — read the protocol overview + signature verification guide. The latter ships with Java and Python reference code you can port directly.
• If you want to see the flow first — try the interactive demo, then return to the docs once you know what you're building.