# Support and  FAQ

### Support

If you need assistance at any stage of your integration:

* Email: <support@inabit.com>
* Enterprise Clients: Use your dedicated support channel (Slack/Telegram), as well as our ticket system in our help center at: <https://support.inabit.com/>
* [General Documentation](https://docs.inabit.com)
* For enabling the terminal feature for your inabit account/organization, please contact our support with a request for activation (applicable for both sandbox and mainnet environments).

### Frequently Asked Questions (FAQ)

#### Getting Started

{% hint style="info" %}
**Q:** How do I enable the Inabit Terminal on my organization?
{% endhint %}

{% hint style="success" %}
**A:** Contact the Inabit support team with your organization ID. Terminal access is available in both mainnet and sandbox (testnet) environments.&#x20;
{% endhint %}

{% hint style="info" %}
**Q:** How do I test the Terminal integration?
{% endhint %}

{% hint style="success" %}
**A:** Use the sandbox environment, which operates on public testnets .You can fund test wallets with testnet tokens and perform end-to-end integration with real blockchain behavior.
{% endhint %}

#### Widget Types

{% hint style="info" %}
Q: What is the difference between Purchase Address and Customer Address widgets?
{% endhint %}

{% hint style="success" %}
**A:**

* Purchase Address Widget: Creates a new address for each transaction. Ideal for one-time payments or invoices.
* Customer Address Widget: Provides a reusable address per customer. Ideal for recurring payments or wallet top-ups.

[More about widget types →](https://docs.inabit.com/inabit-terminal/terminal-guide/widget-types)
{% endhint %}

{% hint style="info" %}
**Q:** Can I reuse a Purchase Address for multiple payments?
{% endhint %}

{% hint style="success" %}
**A:** Yes. Enable the reuseAddress setting when creating the widget. Otherwise, the address will expire after a defined time or a single payment.
{% endhint %}

#### Transactions & Confirmations

{% hint style="info" %}
**Q:** How many confirmations are required before a payment is marked as complete?
{% endhint %}

{% hint style="success" %}
**A:** The default number of confirmations depends on the blockchain (e.g., 1 on Ethereum, 2 on Bitcoin).\
You can request Inabit Support to customize confirmation thresholds per blockchain, or configure them dynamically based on transaction amount ranges and blockchain.
{% endhint %}

{% hint style="info" %}
**Q:** What happens if the customer pays after the widget expires?
{% endhint %}

{% hint style="success" %}
**A:** The payment will still be detected by the Terminal, but it will not be associated with any active purchase. You will need to manually retrieve unlinked payments via the API and associate them with a customer or transaction on your end.
{% endhint %}

{% hint style="info" %}
**Q:** What is a partial payment, and how is it handled?
{% endhint %}

{% hint style="success" %}
**A:** Partial payments (i.e., when a customer sends less than expected) are not automatically accepted. You should handle such cases manually and decide whether to fulfill or refund.
{% endhint %}

#### Webhooks & API

{% hint style="info" %}
**Q:** How do I get real-time updates when a payment is received?
{% endhint %}

{% hint style="success" %}
**A:** When creating the widget, you need to set the webhook URL on widget creation or edit that you will receive payment events.\
Terminal will send POST requests to this URL with updates such as pending, confirmed, expired.
{% endhint %}

{% hint style="info" %}
**Q:** Can I pull transaction status instead of using webhooks?
{% endhint %}

{% hint style="success" %}
**A:** Yes. You can use the Terminal API to retrieve widget status and monitor incoming payments programmatically.
{% endhint %}

{% hint style="info" %}
**Q:** What happens if my webhook endpoint is temporarily unavailable?
{% endhint %}

{% hint style="success" %}
**A:** Inabit automatically retries failed webhook deliveries using exponential backoff. You can also fetch the latest status using the API to reconcile.
{% endhint %}

#### Security & Compliance

{% hint style="info" %}
**Q:** Does Inabit Terminal hold custody of funds?
{% endhint %}

{% hint style="success" %}
**A:** No. Inabit Terminal is a self-custody platform. All deposit addresses are controlled by your organization, and you retain full access to funds.
{% endhint %}

#### Advanced Configuration

{% hint style="info" %}
**Q:** Can I configure expiration, confirmations, and reuse behavior?
{% endhint %}

{% hint style="success" %}
**A:** Yes. When creating a widget, you can define:

* Expiration time (in minutes)
* Confirmation threshold (per blockchain or by amount tier
* Reuse behavior (true or false)
  {% endhint %}

{% hint style="info" %}
**Q:** Can I manage multiple client environments?
{% endhint %}

{% hint style="success" %}
**A:** Yes. You can create and manage separate organizations per client using Inabit’s Terminal-as-a-Service model. Each org has its own API keys, widgets, and webhook endpoints.
{% endhint %}

<br>