# Overview

## Introduction

The **inabit Terminal** is your command center for managing digital assets, processing payments, and automating Web3 operations - all in one secure, intuitive interface.

Whether you're embedding crypto widgets into your platform, automating fund flows, or fueling cross-chain transactions, this documentation will guide you through everything you need to know to get started and scale confidently.

###  What Is Our Terminal?

Inabit Terminal is a crypto payment gateway that allows platforms, merchants, and service providers to accept cryptocurrency directly from their users in a secure, compliant, and customizable way.

It provides an all-in-one infrastructure for generating deposit addresses, tracking blockchain payments, and settling transactions in crypto or fiat, without needing to manage wallets, private keys, or custom smart contracts.

Think of Inabit Terminal as your crypto-native checkout engine, fully managed and easy to integrate via API or UI.

### Who Is It For?

* Payment Service Providers (PSPs) – who want to offer crypto payments to their merchants.
* Merchants and eCommerce stores – accepting crypto as part of checkout (POS or online).
* Platforms and SaaS products – embedding crypto flows inside digital apps.
* White-label/Embedded Finance Providers – offering crypto to their downstream clients (Terminal-as-a-Service).

### What Can You Do With Our Terminal?

* Generate on-chain deposit addresses (Purchase or Customer Address types)
* Monitor incoming payments in real time
* Receive webhook callbacks when payment is complete
* Accept a wide range of crypto assets across supported blockchains
* Settle in crypto or convert to fiat
* Define widget settings like confirmations, expiration, and reuse
* Use either UI (no code) or GraphQL API (developer-first)

### How It Works (High-Level Flow)

1. Enable Terminal for your organization (via support)
2. Create a widget (via the Inabit Dashboard or API)
3. Display the widget to your customer - a QR code + address will be generated
4. Customer pays in crypto
5. Inabit monitors the blockchain
6. You receive a webhook (or poll API) once confirmed
7. You fulfill the order or service, and optionally settle to fiat

You can manage the entire flow through the Inabit Dashboard - no code required.

### Types of Widgets

Inabit Terminal supports two widget types, depending on your payment model:

| Widget Type      | Use Case                         | Reuse Address? | Expiration? | Best For                        |
| ---------------- | -------------------------------- | -------------- | ----------- | ------------------------------- |
| Purchase Address | One-time purchases or invoices   | Optional       | Yes         | eCommerce, donation, QR-POS     |
| Customer Address | Persistent user/account deposits | Yes            | Optional    | Wallet top-ups, recurring users |

{% hint style="info" %}
[Read more about widget types →](https://docs.inabit.com/inabit-terminal/terminal-guide/widget-types)
{% endhint %}

### Environments

| Environment                                           | Description                          | Real Blockchain?    |
| ----------------------------------------------------- | ------------------------------------ | ------------------- |
| <i class="fa-diamonds-4">:diamonds-4:</i>   `Mainnet` | Used for live production payments    | Yes (real funds)    |
| <i class="fa-vial-virus">:vial-virus:</i>   `Sandbox` | Used for testing with testnet assets | Yes (testnet coins) |

The Sandbox environment allows you to run full end-to-end tests using real blockchain behavior, without any financial risk.

{% hint style="info" %}
Having trouble collecting assets on testnet? When testing through our APIs, inabit can provide you with testnet assets including tokens to get going with your tests! All you need to do is request tokens through our support team at: <mark style="color:blue;"><support@inabit.com></mark> or through an existing dedicated integration channel.
{% endhint %}

### Why Should You Use Our Terminal?

| Benefit                        | Description                                                           |
| ------------------------------ | --------------------------------------------------------------------- |
| ✅ Simple Integration           | Use low-code UI or API; no smart contracts or wallet setup required   |
| ✅ Self-Custody by Default      | You control your wallets and funds                                    |
| ✅ Fully Customizable           | Define confirmations, expiration, gas logic, etc.                     |
| ✅ Real-Time Visibility         | Webhooks and dashboard give full payment transparency                 |
| ✅ Multi-Org, Multi-Chain Ready | Easily support different merchants and chains with one infrastructure |
| ✅ Built-in Compliance Tools    | Governance settings and reporting help meet regulatory needs          |

### Taking The Next Steps

> [Get Started with Terminal](https://docs.inabit.com/inabit-terminal/how-to-get-started/enable-terminal)

> [Understand Widget Types](https://docs.inabit.com/inabit-terminal/terminal-guide/widget-types)

> [View Use Cases](https://docs.inabit.com/inabit-terminal/use-cases)

> [Explore API Reference](https://docs.inabit.com/inabit-terminal/api-reference)

> [Read FAQ](https://docs.inabit.com/inabit-terminal/how-to-get-started/support-and-faq)

<br>


---

# 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/overview.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.