StatusTR
Getting StartedPayment OrchestratorWalletBank AccountsInsuranceFraud & Fraud AIIdentitySanctionAutomationSDKDemo
Getting Started
Introduction

Introduction

Lunixi is a payment, risk and compliance orchestration platform. Accepting payments, wallets, fraud decisions, sanctions screening, identity intelligence and automation all run on the same control plane.

How it is put together

The products are separate API families — each has its own endpoints and its own field contract. What they share is the layer beneath: the same authentication, the same error envelope, the same correlation key, the same webhook mechanism.

Lunixi platform architectureYour application connects to a single base URL; the gateway applies shared authentication, the error envelope and the correlation key; behind it sit six separate product API families, and events come back as webhooks.webhook · signed deliveryYour applicationEd25519 private keyapi-gateway/api/v1token · one error envelopex-request-id · tenant isolationmerchantId is read from the tokenPaymentsWalletFraudSanctionIdentityAutomation/payments/wallet/fraud/sanction/identity/automation
There is no magic endpoint that does everything in one call. Each product has its own. The payoff is that they all share one authentication, error and webhook model — you integrate once, and the other products ride the same skeleton.

Learn it once, it holds across every product

Shared layerWhat it means
AuthenticationYou mint a token with your Ed25519 key; the same token works across every product. → Authentication
Error envelopeWhichever product it comes from, an error carries the same fields; you branch on code. → Error Handling
CorrelationEvery response carries x-request-id; one key is enough for a support request
WebhooksOne signature scheme, one retry policy, one replay surface. → Webhooks
Tenant isolationmerchantId is read from the token; the request body cannot spoof another tenant
Amount unitMinor-unit integers everywhere — 250000 = ₺2,500.00

This is why integrating the second product takes far less time than the first: you do not rewrite the signing, error-handling and webhook-verification code.

Products

ProductWhat it does
Payment OrchestratorMulti-provider payment lifecycle, smart routing, POS management, failover
WalletProgram-scoped accounts under your own brand — top-ups, transfers, wallet payments, QR, loyalty, and the limit and fee engines
Fraud & Fraud AIExplainable fraud decisions, a rule and flow engine, shadow testing
IdentityDevice, IP, session and behavioural intelligence across web, mobile and POS — plus KYC
SanctionName, wallet, account and transaction screening, with continuous monitoring and an analyst workflow
AutomationEvent-driven workflows connecting payments, risk and your own operational stack

What not to expect

⚠️

There is no magic endpoint that screens every risk in one call. A fraud decision is one call; sanctions screening is another. If you want, you can place sanctions screening as a node inside a fraud flow — then both run in a single call. But you compose that yourself; it is not the default. → Flows and Resolution

Where to start

  1. Quickstart — generate a key, mint a token, make your first call
  2. API Overview — base URL, envelope, idempotency
  3. The section for whichever product you need
OverviewQuickstart