DEVELOPER
Development tools for building on KozenOS and managing KOZEN devices at scale.
This page should explain the integration layer more clearly: Kozen SDK for payments and device capabilities, component access for terminal-side modules, and the management interfaces that connect implementation teams back to live estates.
TOOLCHAIN
Build against payment, device, component and estate capabilities in one stack.
Kozen SDK is the main integration layer for teams building on top of KOZEN terminals, and the PPT makes the surrounding structure clearer: SDK framework, terminal manager modules and component capabilities belong to one connected developer system.
INTEGRATION FLOW
From Kozen SDK integration to managed device estate.
Financial SDK, Terminal Manager SDK and Component SDK should read as one connected path: build payment and device features first, then connect the deployed estate back into management, policy execution and remote operational control.
From payment capability to broader device control.
Kozen SDK should be presented as the core toolkit for payment acceptance, scanner, printer, card reader, screen and other terminal-side capabilities needed by integration teams.
More operational control for deployed estates.
Terminal Manager SDK extends beyond app-side integration into estate control, including device information, permissions, resource installation and management-side actions.
Reusable hardware and interface components.
Component SDK should help teams move faster when they need ready access to device-side modules such as printer, scanner, secondary display and other reusable components.
Production-oriented resources ready to download.
Customers should be able to quickly identify where to get Kozen SDK packages, management SDKs, component documents and implementation guides for real project work.
CAPABILITY GROUPS
Core capability areas teams expect from Kozen SDK.
WHERE TO START
Three entry points for different integration tasks.
The SDK story should feel expandable, not locked to a single terminal flow.
The KozenOS material makes this clearer: the developer layer spans SDK framework, terminal manager modules, app-level extensibility and a component system that can keep evolving with the portfolio.
Administrative control layers for secure device estates.
Terminal Manager SDK is the bridge from development into deployment, exposing the control surfaces needed to manage terminals after they are live in the field.
Kozen SDK, Terminal Manager SDK, Component SDK and supporting documents should be clearly grouped so technical teams know exactly where to start.
Management-side controls that matter after integration is complete.
Developer visitors also need to see what happens after go-live: remote authorization, app network firewall control, cloud configuration and efficient estate-side response.
The main developer product customers should remember.
For most technical visitors, Kozen SDK is the simplest mental model: it is the primary integration layer for building on KOZEN terminals, while the other SDKs extend into components and deployment control.
Developer builds with Kozen SDK first, then connects live estates back into management through the Terminal Manager side of the platform. See Angel Watch TMS
The Developer module should feel like the integration doorway into the larger software platform described in Ecosystem, especially the open ecosystem and controllable management layers shown in the KozenOS material.