Support and FAQ

Support

If you need assistance at any stage of your integration:

• Email: [email protected]

• 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

• 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

Q: How do I enable the Inabit Terminal on my organization?

A: Contact the Inabit support team with your organization ID. Terminal access is available in both mainnet and sandbox (testnet) environments.

Q: How do I test the Terminal integration?

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.

Widget Types

Q: What is the difference between Purchase Address and Customer Address widgets?

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 →

Q: Can I reuse a Purchase Address for multiple payments?

A: Yes. Enable the reuseAddress setting when creating the widget. Otherwise, the address will expire after a defined time or a single payment.

Transactions & Confirmations

Q: How many confirmations are required before a payment is marked as complete?

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.

Q: What happens if the customer pays after the widget expires?

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.

Q: What is a partial payment, and how is it handled?

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.

Webhooks & API

Q: How do I get real-time updates when a payment is received?

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.

Q: Can I pull transaction status instead of using webhooks?

A: Yes. You can use the Terminal API to retrieve widget status and monitor incoming payments programmatically.

Q: What happens if my webhook endpoint is temporarily unavailable?

A: Inabit automatically retries failed webhook deliveries using exponential backoff. You can also fetch the latest status using the API to reconcile.

Security & Compliance

Q: Does Inabit Terminal hold custody of funds?

A: No. Inabit Terminal is a self-custody platform. All deposit addresses are controlled by your organization, and you retain full access to funds.

Advanced Configuration

Q: Can I configure expiration, confirmations, and reuse behavior?

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)

Q: Can I manage multiple client environments?

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.