> For the complete documentation index, see [llms.txt](https://docs.inabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inabit.com/inabit-terminal/use-cases/terminal-as-a-service.md).

# Terminal-as-a-Service

{% hint style="info" %}

### 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.
{% endhint %}

{% hint style="success" %}

### 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.
{% endhint %}

### <i class="fa-users">:users:</i>  Actors

* Platform integrator (white-label provider)
* Sub-clients (merchants, financial apps, platforms)
* End customers

### <i class="fa-sitemap">:sitemap:</i>  Integration Flow Explained

1. Integrator contacts Inabit support to enable Terminal for their main organization.\
   Implement the [Inabit Approval App](broken://pages/SSBSw4n4h4tFl8qHbYjC) to authorize API operations and widget management.
2. For each client, create a dedicated Inabit organization via admin tools or API.
3. Create [Customer Address](https://docs.inabit.com/inabit-terminal/use-cases/pages/X6jCZsAwQD43UfaoY5jJ#id-2.-customer-address-widget) or [Purchase Address](https://docs.inabit.com/inabit-terminal/use-cases/pages/X6jCZsAwQD43UfaoY5jJ#id-1.-purchase-address-widget) widgets for each organization.
4. Sub-client embeds the widgets into their checkout or product interface.
5. Each sub-client receives its own webhook events for transaction updates.
6. Integrator manages settlement, compliance, and reporting across clients.

### <i class="fa-sparkles">:sparkles:</i>  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

### <i class="fa-square-check">:square-check:</i>  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
