Integrations
Money contract 1.0. Monetary requests use canonical minor-unit strings; JSON numbers and explicit null amounts are rejected. Upgrade guide.
Choose your application's language, store platform or framework. There are nine server language SDKs, native store/billing modules and framework packages or runnable examples. Node.js includes JavaScript and TypeScript, with NestJS and Express examples in the same SDK repository.
Each guide records its supported versions, installation method, tested behavior and limitations. A GitHub source release, package-registry publication and platform marketplace approval are separate steps; follow the selected guide rather than assuming a registry package or marketplace listing exists.
Server SDKs
| Language | Package / source | Framework entry points |
|---|---|---|
| Node.js / TypeScript | @lunixi/node-sdk (opens in a new tab) | NestJS, Express and other server frameworks |
| PHP | lunixi/php-sdk (opens in a new tab) | Laravel, Symfony, CodeIgniter 4, Yii 2 |
| .NET / C# | Lunixi.Sdk (opens in a new tab) | ASP.NET Core, workers and server applications |
| Go | lunixi-go (opens in a new tab) | net/http and Go server frameworks |
| Java | lunixi-java (opens in a new tab) | Spring Boot Starter and other JVM services |
| Python | lunixi-sdk (opens in a new tab) | Django, FastAPI, Flask |
| Ruby | lunixi-sdk (opens in a new tab) | Rails and Ruby server applications |
| Rust | lunixi (opens in a new tab) | Asynchronous Rust server applications |
| Elixir | :lunixi (opens in a new tab) | OTP, Phoenix and Plug server applications |
All nine server SDKs carry the same typed product clients; method names follow each language's own naming (directMethodPayment, DirectMethodPaymentAsync, direct_method_payment …). Read the language guide for its client and method names, explicitly signed transport support, binary/multipart limitations and native persistence requirements.
| Product | Coverage |
|---|---|
| Payments | Intent, status and list, capture/refund/void; payment methods and buyer actions, promissory notes, split payments, bank transfer exceptions, BIN and installments, stored cards, marketplace intent |
| Payment links | Create, update, pause/resume, send, QR code, attempts, image upload |
| Fraud | Decisions, transaction event recording, decision records |
| Address dictionary | Province, district and neighborhood codes |
| Physical POS | Terminal payments, reversals, reports, end-of-day; store, register, terminal and device management |
| Wallet | Programs, end users, wallets, transfers, withdrawals, top-ups, payments, QR codes, bulk payouts |
| Bank accounts | Banks, connections, accounts, balances, transactions; outgoing transfers and FX |
| Sanctions screening | Name, wallet, account, transaction, public procurement ban and adverse media screening; ongoing monitoring, entity intelligence, deny list |
| Insurance | Products, quotes, orders, premium collection and refunds, policy documents, reconciliation, leads |
| Subscriptions | Subscriptions, plans, customers, saved cards, invoices, customer portal, products, features, add-ons, usage |
| KYC | KYC, KYB and evidence sessions, document upload, manual review, KYC policy |
| Identity signals | Live-session analysis, linked accounts on a device, session history |
| Marketplace sub-dealers | Split charges across sub-dealers, dealer lifecycle, commissions, payouts, audit log |
Versions and installation channels
Use the versions below for the 1.0 string money contract. Registry installation and matching GitHub source tags are separate channels. Resolve the exact version and retain the lockfile; a 0.x package cannot substitute for a 1.0 dependency. Historical test counts and checksums in individual guides refer only to their named artifacts.
Store and billing modules
| Your platform | Integration guide | Version / distribution |
|---|---|---|
| WordPress / WooCommerce | WordPress / WooCommerce plugin | 1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab); no WordPress.org approval claimed |
| OpenCart 3 | OpenCart 3 payment extension | 1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
| OpenCart 4 | OpenCart 4 payment extension | 1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
| PrestaShop | PrestaShop payment module | 2.0.3 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
| Magento 2 / Adobe Commerce | Magento 2 payment module | 1.1.1 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
| WHMCS | Gateway and companion admin addon | 1.1.1 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
| nopCommerce | nopCommerce payment plugin | 1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab) |
OpenCart packages are separate for each major version: use the version selector. Check the exact platform/PHP/.NET compatibility and acceptance boundaries in each guide. WHMCS licensed-runtime acceptance and Adobe Commerce licensed-edition verification are described explicitly in their respective guides.
Hosted and embedded form availability follows the selected module. Eligible payment methods, multi-card payments, installments and insurance remain controlled by the merchant's Lunixi configuration and capabilities; installing a module does not enable every method automatically.
Framework packages and runnable examples
| Stack | Integration |
|---|---|
| Node.js / TypeScript | NestJS provider and Express examples in the Node.js SDK repository |
| PHP / Laravel | Laravel package |
| PHP / Symfony | Symfony Bundle |
| PHP / CodeIgniter | CodeIgniter 4 application |
| PHP / Yii | Yii 2 application |
| Java / Spring | Spring Boot Starter and MVC/JDBC application |
| Python / Django | Django application |
| Python / FastAPI | FastAPI application |
| Python / Flask | Flask application |
| Ruby / Rails | Rails application |
| .NET / ASP.NET Core | ASP.NET Core backend example |
A runnable example demonstrates a concrete integration boundary. Replace demo accounts/orders with your native authentication, authorization and business workflow; retain its transaction, webhook and stable-attempt protections. A framework sample is not necessarily a separately published framework package.
For server-rendered checkout, start with authenticated data.checkoutFormContent and an empty target: it loads the SDK and mounts the form automatically. Manual token mounting remains an alternative. See the ready-form guide. Optional redirects use the same intent’s backend paymentPageUrl.
Payment authority
Keep secret keys on the server. Create payments from trusted server order totals. A browser return or successful form display never proves payment: verify the raw signed webhook, authenticate the payment status read, match the persisted order and settlement, and apply the native order/inbox transaction atomically.
Authenticated GET may expose optional details.orderAmountMinor from trusted original creation evidence. It validates the original local order total separately from final installment/insurance totals; missing legacy evidence is not a substitute for the original sum, and the field alone does not prove capture.
Unknown outcomes keep their original attempt/key and require reconciliation. Use the selected integration's documented retention fence and durable operation rules before retrying a money-moving request. See webhooks and error handling.
Tools and client SDKs
| Need | Start here |
|---|---|
| Call the API without a language wrapper | REST without an SDK |
| Explore requests without building an application | Postman collection |
| Payment form, card field, customer portal or browser KYC | Web SDK overview |
| Native/mobile risk collection and identity verification | Mobile SDK overview |
Browser and mobile SDKs carry client evidence and display supported flows; your server remains responsible for payment and business decisions. Use publishable/session-scoped client credentials as documented, and keep signing keys and webhook secrets out of client bundles.