Integrations
Overview

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

LanguagePackage / sourceFramework entry points
Node.js / TypeScript@lunixi/node-sdk (opens in a new tab)NestJS, Express and other server frameworks
PHPlunixi/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
Golunixi-go (opens in a new tab)net/http and Go server frameworks
Javalunixi-java (opens in a new tab)Spring Boot Starter and other JVM services
Pythonlunixi-sdk (opens in a new tab)Django, FastAPI, Flask
Rubylunixi-sdk (opens in a new tab)Rails and Ruby server applications
Rustlunixi (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.

ProductCoverage
PaymentsIntent, 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 linksCreate, update, pause/resume, send, QR code, attempts, image upload
FraudDecisions, transaction event recording, decision records
Address dictionaryProvince, district and neighborhood codes
Physical POSTerminal payments, reversals, reports, end-of-day; store, register, terminal and device management
WalletPrograms, end users, wallets, transfers, withdrawals, top-ups, payments, QR codes, bulk payouts
Bank accountsBanks, connections, accounts, balances, transactions; outgoing transfers and FX
Sanctions screeningName, wallet, account, transaction, public procurement ban and adverse media screening; ongoing monitoring, entity intelligence, deny list
InsuranceProducts, quotes, orders, premium collection and refunds, policy documents, reconciliation, leads
SubscriptionsSubscriptions, plans, customers, saved cards, invoices, customer portal, products, features, add-ons, usage
KYCKYC, KYB and evidence sessions, document upload, manual review, KYC policy
Identity signalsLive-session analysis, linked accounts on a device, session history
Marketplace sub-dealersSplit 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.

PackageVersion / sourceInstallation channel
Node.js / TypeScript2.0.1 (opens in a new tab)npm (opens in a new tab)
PHP2.0.1 (opens in a new tab)Packagist (opens in a new tab)
Go2.0.0 (opens in a new tab)Go modules (opens in a new tab)
Python2.0.0 (opens in a new tab)PyPI (opens in a new tab)
.NET / C#2.0.1 (opens in a new tab)NuGet (opens in a new tab)
Java2.0.1 (opens in a new tab)Maven Central (opens in a new tab)
Ruby2.0.2 (opens in a new tab)RubyGems (opens in a new tab)
Rust4.0.0 (opens in a new tab)crates.io (opens in a new tab)
Elixir2.0.0 (opens in a new tab)Hex.pm (opens in a new tab)
Laravel2.0.0 (opens in a new tab)Packagist (opens in a new tab)
Symfony Bundle2.0.0 (opens in a new tab)Packagist (opens in a new tab)
Spring Boot Starter2.0.0 (opens in a new tab)Maven Central (opens in a new tab)

Store and billing modules

Your platformIntegration guideVersion / distribution
WordPress / WooCommerceWordPress / WooCommerce plugin1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab); no WordPress.org approval claimed
OpenCart 3OpenCart 3 payment extension1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab)
OpenCart 4OpenCart 4 payment extension1.1.0 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab)
PrestaShopPrestaShop payment module2.0.3 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab)
Magento 2 / Adobe CommerceMagento 2 payment module1.1.1 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab)
WHMCSGateway and companion admin addon1.1.1 ZIP (opens in a new tab) · SHA256SUMS (opens in a new tab)
nopCommercenopCommerce payment plugin1.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

StackIntegration
Node.js / TypeScriptNestJS provider and Express examples in the Node.js SDK repository
PHP / LaravelLaravel package
PHP / SymfonySymfony Bundle
PHP / CodeIgniterCodeIgniter 4 application
PHP / YiiYii 2 application
Java / SpringSpring Boot Starter and MVC/JDBC application
Python / DjangoDjango application
Python / FastAPIFastAPI application
Python / FlaskFlask application
Ruby / RailsRails application
.NET / ASP.NET CoreASP.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

NeedStart here
Call the API without a language wrapperREST without an SDK
Explore requests without building an applicationPostman collection
Payment form, card field, customer portal or browser KYCWeb SDK overview
Native/mobile risk collection and identity verificationMobile 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.