Terminal-as-a-Service
An example use case of how the Terminal can be utilized.
Problem
White-label providers and embedded finance platforms want to offer crypto payments as part of their services, with tenant-level separation, compliance, and customization—without managing blockchain infrastructure internally.
Solution
Inabit Terminal supports multi-organization setup, allowing the integrator to create separate environments (sandbox or mainnet) per client. Each client has its own widgets, webhooks, settlement flows, and settings—all centrally managed.
Actors
Platform integrator (white-label provider)
Sub-clients (merchants, financial apps, platforms)
End customers
Integration Flow Explained
Integrator contacts Inabit support to enable Terminal for their main organization. Implement the Inabit Approval App to authorize API operations and widget management.
For each client, create a dedicated Inabit organization via admin tools or API.
Create Customer Address or Purchase Address widgets for each organization.
Sub-client embeds the widgets into their checkout or product interface.
Each sub-client receives its own webhook events for transaction updates.
Integrator manages settlement, compliance, and reporting across clients.
Relevant Features
Full organizational isolation per client
Custom webhook URLs, policies, and widget configuration
Central management for compliance and analytics
Widget branding per sub-organization
Crypto-to-fiat off-ramp options per tenant
Benefits
Scalable crypto payment infrastructure for platforms with many clients
Complete white-label capability
Segregated data and flows per tenant
Centralized control over technical and financial flows
Last updated
Was this helpful?