# Integrating with inabit

{% hint style="info" %}

### Problem

Platforms and SaaS companies want to embed crypto payments into their own products—such as booking systems, subscriptions, or digital goods—but need a flexible, event-driven architecture that’s easy to integrate.
{% endhint %}

{% hint style="success" %}

### Solution

Inabit Terminal allows developers to create widgets tied to customer flows and receive real-time payment events via webhooks or polling APIs. This makes it easy to trigger business logic such as access provisioning, notifications, or fulfillment.
{% endhint %}

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

* Platform developer
* Platform user
* End customer

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

1. Developer contacts Inabit support to enable Terminal in sandbox or mainnet.
2. Implement the [Inabit Approval App](broken://pages/SSBSw4n4h4tFl8qHbYjC) to authorize API operations and widget management.
3. Create a [Customer Address widget](https://docs.inabit.com/inabit-terminal/use-cases/pages/X6jCZsAwQD43UfaoY5jJ#id-2.-customer-address-widget) for each platform user or transaction.
4. Embed the widget into the platform’s UI (e.g., checkout page, account dashboard).
5. Customer sends crypto to the address; Terminal detects and confirms the transaction.\
   Platform receives webhook or polls the API to get status.
6. Business logic is executed (e.g., subscription activated, content delivered, balance credited, etc.).

### <i class="fa-sparkles">:sparkles:</i>  Relevant Features

* Persistent or transaction-specific addresses
* Webhook events: pending, confirmed, expired
* Polling option via Terminal API
* Sandbox for testing and validation
* Advanced widget configuration (e.g., max confirmations, sweeping frequency)

### <i class="fa-square-check">:square-check:</i>  Benefits

* Fits seamlessly into existing SaaS workflows
* Enables automated crypto payment handling
* Supports recurring payments or on-demand events
* Minimal backend complexity


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inabit.com/inabit-terminal/use-cases/integrating-with-inabit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.