Terminal Entities

Learn about the entities surrounding our payments terminal

Account

An Account in Inabit is the top-level entity that governs access, ownership, and identity across the platform. Each account has a single owner and can contain one or more organizations beneath it. All users are created at the account level, where their credentials (e.g., login details, authentication methods) are managed centrally. These users can then be assigned to one or multiple organizations, each with specific roles and permissions.

The mobile app and web platform operate at the account level, providing unified access and navigation across all linked organizations. This model enables clear separation of data and operations per organization, while allowing account users to manage multiple business entities from a single secure login.

Organization

An Organization in Inabit represents an isolated operational unit within an Account. It serves as a container for blockchain configurations, wallets, policies, and approval logic specific to a particular business entity, brand, or environment (such as sandbox vs. mainnet).

Each Account can have multiple organizations, allowing a single user base to manage and operate across distinct environments or clients while keeping operational and financial data completely separated. Organizations control their own blockchain settings, asset management, and custody setup.

Merchant

A Merchant refers to a specific business or client that receives crypto payments through the Inabit Terminal. Merchants operate under a parent organization and may represent a single store, a brand, or a tenant in a multi-client setup. Each merchant can have its own branding, business logic, and webhook URLs. In multi-tenant or white-label models (e.g., Terminal-as-a-Service), a separate organization can be provisioned per merchant to ensure full data and operational isolation. Merchants use widgets to accept payments and interact with their end customers.

Widget

A Widget is the core interface used to accept crypto payments. It is a lightweight, embeddable component that generates a deposit address (and QR code) and displays it to the customer. Widgets handle the entire crypto payment lifecycle—from address creation and payment detection to confirmation and status updates. Inabit supports two types of widgets:

• Purchase Address Widget: For one-time payments (e.g., a checkout or invoice)

• Customer Address Widget: For recurring or persistent use (e.g., top-up wallets)

Widgets can be created and managed via the Inabit Dashboard (no code) or the GraphQL API, and can be configured with parameters such as expiration time, confirmation threshold, and address reuse behavior.