Creating clearing-ready POS widgets through our interface
POS Widgets in inabit’s Terminal are embeddable components that enable merchants to accept cryptocurrency payments directly from users. These widgets are highly customizable and connected to your organization’s internal wallet infrastructure, giving you full control over supported assets, payout behavior, fees, expiration rules, and more.
A POS (Point of Sale) Widget is a payment interface you can generate inside your Terminal to receive deposits from end users or customers in a specific cryptocurrency. You can configure it to:
Support specific assets (e.g., USDT on Tron or Ethereum)
Sweep funds to your wallets automatically
Apply expiration and confirmation logic
Choose who pays the fees (merchant or customer)
These widgets are ideal for:
Subscription billing
Pay-per-use tools
Partner platforms
In-app payments
From the Terminal dashboard:
Click the blue “Add New Widget” button on the top right.
A widget creation drawer will appear on the right side with the following fields:
1. Widget Name
A unique name to identify your widget (e.g., Basic Plan Payment).
Visible internally and optionally to users.
2. Description
A short explanation of what this widget is used for.
Optional but helps for internal tracking.
3. Merchant Name (Optional)
Name of the merchant displayed to the end user (if applicable).
4. Assets (Supported Assets)
Select which cryptocurrencies the widget will accept.
Example: USDT (TRC20), USDC (ERC20), ETH.
Dropdown field with multi-select options.
You can also search for a specific asset code you're looking for using the search bar.
This defines how and when collected funds will be transferred from the widget deposit addresses to your organization wallet.
Options:
Daily – Sweeps once per day to the configured wallet.
Weekly – Sweeps once per week.
On-Demand – Funds are swept only when triggered via API or Terminal manually.
Choose based on your operational and liquidity needs.
Select the wallet address to which collected funds will be swept.
Dropdown field pulling from your organization's wallet list.
Choose who pays the gas/processing fee when sweeping occurs:
Charge Merchant (Myself) – Your organization covers the sweep cost.
Charge Customer – Fees are deducted from the user's deposit amount.
Once all the fields are set:
Click “Create Widget”
Your new POS Widget will be added to the list and ready for use.
That's it! You can now embed it, monitor its activity, and manage its funds directly from the Terminal.
To learn more about how and review the implementation steps, refer .
You can also click on the "Preview Widget" to review your changes live, the widget will then appear on your screen as an example to how it will be shown on your application/website:
Learn more about the types of POS Widgets our Terminal offers
Inabit Terminal provides two widget types to support a wide range of payment scenarios. Both handle deposit address generation, blockchain monitoring, and transaction confirmation. The main difference lies in how deposit addresses are assigned and reused.
Used for single-use or transaction-specific payments. This widget generates a unique deposit address for each new payment flow, enabling easy matching of transactions to specific purchases.
eCommerce checkout flows
Invoices with expiration windows
Donations or one-time contributions
Payment links in emails or support chats
A new deposit address is generated each time the widget is created.
The customer sends crypto to this unique address.
The widget listens for an on-chain deposit and triggers a webhook or terminal API callback.
After the specified number of confirmations, the transaction is marked as complete.
Unique address per transaction for clean reconciliation
Supports expiration windows and partial payments
Enables reuse of addresses across different purchases to reduce network fees
Automatic rate refresh upon expiration (when enabled)
Designed for long-term use, this widget assigns a persistent deposit address to a specific customer or account. All incoming payments to that address are monitored over time, allowing flexible, account-based payment handling.
Recurring user payments
Wallet or account top-ups
Subscription billing (manual)
Developer platforms or marketplaces
A customer-specific deposit address is created once and reused for that customer.
The address is monitored continuously by Inabit Terminal.
Each incoming transaction to the address is tracked, confirmed, and pushed to your system via webhook or API.
Multiple payments can be made to the same address over time.
Persistent deposit address per customer or account
Optimized for recurring or ongoing payments
Simplifies deposit handling in user/account-based systems
Configurable expiration, confirmation count, and other options
Both widget types are created via the Inabit Terminal GraphQL API or from the Inabit Dashboard.
All widgets support:
Blockchain and asset selection
Confirmation threshold configuration
If payment is not received in time, the widget can expire and optionally generate a new quote or address.
Best for real-time, time-limited payments
Highly auditable and secure
Ideal for customer wallets, balances, or prepaid models
Donations with tracking per campaign
Purchase Address Widget
Payment links sent via email or chat
Purchase Address Widget
API-based integration for programmatic payouts
Customer Address Widget
Service credit recharge by end users
Customer Address Widget
Expiration timeouts
Partial payment tolerance
Widgets can be embedded in web or mobile applications.
Real-time payment updates are available via webhook or by polling the Terminal API.
Sandbox and mainnet environments are supported for safe development and production deployments.
One-time eCommerce checkout
Purchase Address Widget
Physical store QR code payment
Purchase Address Widget
Invoice with expiration (e.g., due in 30 minutes)
Purchase Address Widget
Subscription top-ups or account funding
Customer Address Widget
Multi-user platform that tracks deposits per user
Customer Address Widget
Recurring customer payments with the same address
Customer Address Widget
Embed it into your app, website, or customer flow
Advanced settings of our POS widgets before creation
This feature is only applicable for Purchase Address widget type.
Enabled – The same deposit address will be used for each transaction.
Useful for recurring or identifiable customers.
Can be reused for new deposits without creating a new widget.
Disabled – A new, unique deposit address is generated per session/transaction.
This feature is only applicable for Purchase Address widget type.
Set a time window (in minutes) for how long the widget will remain valid after being opened.
This can be changed per blockchain as well, depending on the setting
Example: 15 minutes, 60 minutes.
This feature is only applicable for Purchase Address widget type.
What should happen when the widget expires?
Fail the request – The transaction is invalidated.
Update the rate of the POS transaction – The widget remains usable, but the rate will refresh based on current market price.
This feature is only applicable for Purchase Address widget type.
Enabled – The widget will accept any amount deposited, even if it doesn’t match the target amount.
Use this when the deposit can vary or when customer balance might be uncertain.
Partial deposits will still be marked successful and trigger webhook notifications if applicable.
This field is where you enter the URL where the customer will be sent upon successful purchase.
inabit will be add the identifier to the redirect URL.
inabit will use this URL to send back webhook callbacks/notifications to this address.
