Browsing Partners by Category

Advisory & Strategy

Marketing & Distribution

Custody & Infrastructure

Secondary Trading

Partner Cards

RWA.xyz

Need Expert Advice? Contact Us

Note: Your role (Owner, Admin, Viewer, or Super Admin) is read-only here. To modify team roles or invite new users, go to Team Management.

The Profile card at the top of the page displays your current role and email address:

• Role: Shows your assigned role within the platform (Owner, Admin, Viewer, or Super Admin).

• Email: Your current sign-in email address.

These values are read-only on this page.

Manage how your name appears in the app and in notifications.

1. Locate the Name card.

2. View your current full name under “Current name.” If no name is set, you will see “—.”

3. Click Edit name to enter edit mode.

4. Update your First name and Last name (each up to 100 characters).

5. Click Save to apply changes or Cancel to discard.

Upon successful update, a confirmation message appears.

Change the email address used for signing in and receiving account notifications. Changing your email requires a two-step verification process.

1. In the Email Address card, click Change email.

2. Under New email address, enter a valid email (e.g. [email protected]).

3. Click Send verification code. A 6-digit code is sent to the new address.

4. Enter the 6-digit code and click Confirm.

5. If you do not receive the code, click Resend code.

Error messages and success notifications appear inline. After confirmation, your sign-in email is updated automatically.

Use the Security card to manage your account’s sign-in security:

• Change Password: Update your current password.

• Active Sessions: Review and sign out of other active sessions.

• Two-Factor Authentication: Enable or manage 2FA if your account supports it.

Follow the on-screen prompts in the Security section to update your credentials and safeguard your account.

Profile

Name

Email Address

Security

This means that referrers can only earn commission for these 4 blockchain networks, and referred users can use their discount codes only on these 4 supported networks. We are currently looking to include support for the rest of the available networks.

Using discount codes is currently possible on Token Tool's functions below:

• Create Token

• Distribute Token

• Create Token Sale

• Create Token Locker

• Create NFT (not on NFT minting)

• Distribute NFT

Referrers earn 30% commission on each transaction that takes please using their unique referrer code. Learn more about Token Tool's crypto affiliate program and start earning money easily.

Redeeming you discount

Supported Networks

Supported Functions

After you created the payment stream collection, you will see it in the overview. From there you can add individual streams to the collection.

From the Manage Stream Collection part you can add and manage streams. You can also top up the collection with tokens from here and withdraw tokens that haven't been transferred to the recipients, yet.

For each individual payment stream you need to define:

• Recipient address: this is the address that will receive the tokens from this stream

• Payment start time: from this moment onward the payment stream will be calculated. This can also be in the past. Let's assume an employee started on October 1st and you only create the stream on October 20th, you can date it back to October 1st. That way the employee will receive the full payment for October.

• Payment rate per average month: this is the amount of tokens that is streamed per month. Note that this amount is broken down in the background into a payment per second. Therefore smaller rounding errors on daily / weekly / monthly values may occur.

It's important to note that for the token recipients to actually get their tokens someone needs to click one of the two options:

• Transfer tokens to recipients: this will transfer all the tokens that have been streamed to this moment to the respective recipients. All tokens for all streams of this collection will be transferred.

• Transfer: this will only initiate the transfer of tokens for all streams of the particular recipient that you clicked on.

Anybody can click the transfer buttons. Note that when you do that, you will also pay the gas fees for the respective transactions.

If the stream collection doesn't have enough tokens, the transfers will not happen. You will need to add a sufficient amount of tokens to the collection and initiate the transfer again.

The streaming will however continue even if there isn't a sufficient balance. This means you can always catch up with the transfer after you topped up tokens.

Create Payment Stream Collection

Manage Payment Stream Collection

Create Payment Stream

Token transfer

• Error 1: Invalid wallet address

• Error 2: Duplicated address with Line X

• Error 3: Incorrect punctuation mark. Use commas between addresses, TokenID and amount and no spaces in-between

Some quick actions can be selected to resolve duplicate addresses:

• Keep duplicated addresses

• Delete duplicated records

Other errors have to be fixed manually or can be deleted automatically by using the “Delete incorrect records” function.

• Initial token distribution to investors after a primary issuance

• Sending additional tokens to token holders after a capital increase or a rights issue

• Sending dividend or coupon payments in stable coins, cryptocurrencies or asset tokens to token holders

• Conducting an airdrop of tokens to a long list of addresses

Optionally, you can also add a third attribute to the input. This allows you to attach an individual message to each transfer. This can be useful in situations where you want to add an internal reconciliation ID or a message that is necessary for regulatory purposes to each transfer. This is how an example input would look like:

Note that this Distribute Token is not supported on Ethereum Goerli testnet. However, it does work on Ethereum mainnet and all other supported chains (both main and testnets).

Manage Token Vesting Collection

Create Token Vesting

Token transfer

As the issuer of a token you normally don't hold tokens for a long time. Typically tokens are distributed to investors shortly after they are minted.

However, often additional tokens need to be minted after the primary issuance. Sometimes certain properties of tokens need to be changed. Only if you can be sure, that additional token minting, burning or other configurations will never change after the primary issuance, the issuer account key for a particular token can be deleted or token ownership can be explicitly renounced. This is a non-reversible action that disables further changes to the token configuration.

In all other cases, issuer keys need to be kept in a safe location from where transactions can be signed ideally in an automated way. At Bitbond we work with several regulated custodians and can recommend partners for you.

For robust, large-scale production deployments, we advocate for implementing a transaction authorization policy or transferring token contract ownership to a multi-signature wallet. Such precautions minimize risks associated with a singular point of failure, such as key leaks or the potential misuse of ownership rights by a malicious actor. Requiring multiple approvals from the team that oversees the token increases security. In certain scenarios, teams opt to organize themselves as a Decentralized Autonomous Organization (DAO) to further bolster decentralization and enhance transparency in their operations.

If you create tokens on an EVM chain with Bitbond Token Tool, there are the following ways to manage your issuer keys.

You can work with a custodian as described above. The custodian needs to support Web3 login through Wallet Connect. In such cases the custodian can log in to Token Tool from within their key management software and create tokens, manage tokens and distribute tokens on behalf of the issuer.

If as an issuer you want to be independent of a custodian when it comes to token management, you need to maintain a key management solution yourself. There are several secure and convenient solutions in the market, some of which are listed here.

Fireblocks is a sophisticated key management software that has very comprehensive functionality around digital assets. It can store nearly all currencies and tokens that currently exist and lets you configure sophisticated governance and approval rules.

Typically custodians would utilize Fireblocks. If you need to manage multiple keys for several tokens and need a more sophisticated approach to governance, Fireblocks is they right way to go.

With Fireblocks you can log in to Token Tool with Wallet Connect.

Ledger is one of the leading hardware wallets. You can use it with Token Tool directly or use it as a more secure way to mange keys behind Metamask and log in to Token Tool with Metamask. For institutions, Ledger Enterprise provides bank-grade key custody infrastructure.

Metamask is a simple and convenient way to log in to Token Tool. However, from a security standpoint it should not be used for transactions and tokens of higher value because it is not built for an institutional but rather a consumer context.

Safe is another secure and convenient way to manage issuer keys. It allows you to use Metamask or Wallet Connect to log in to Token Tool.

Phantom

Phantom is a popular wallet for the Solana ecosystem, offering a user-friendly interface, integrated token management, and built-in support for NFTs. It is ideal for users managing Solana-based tokens and supports the newer Token-2022 standard. While Phantom is primarily a consumer wallet, it is a practical option for Solana token issuers and investors in lower-risk scenarios.

Freighter

Freighter is a non-custodial browser extension wallet for the Stellar network. It is specifically designed to interact with Stellar-based tokens and decentralized applications. Freighter offers an easy way for issuers and investors to manage Stellar accounts and sign transactions securely. It is well-suited for token issuers working within the Stellar ecosystem who require a lightweight and secure self-custody solution.

Custodian

Self-custody

Fireblocks

Ledger Enterprise

Metamask

Safe

• Status Change Updates to offering or order status (e.g. Draft → Active, Pending → Settled).

• Bank Reconciliation Entries related to reconciliation of bank transfer payments.

• Investor Created Manual creation of an investor by an admin.

• Investor Edited Edits to an investor’s profile or KYC status by an admin.

• KYC Override Manual override of an investor’s KYC result.

• Order Created Manual order creation by an admin (including manual payment methods).

• Order Edited Edits to an existing order by an admin.

• Order Placed Orders submitted by investors through the Invest Page.

• Wallet Updated Investor-initiated changes to their wallet address or chain.

• Profile Updated Investor-initiated edits to profile information.

• Other Actions Any actions not covered above will appear under their raw action name.

Use the controls at the top of the page to narrow down entries:

• Search Enter part of an actor’s name or email, an action label, or an entity ID. This full-text search is applied client-side.

• Entity Type Choose All Types, Investor, or Order to filter entries by entity.

• Refresh Click the Refresh icon to reload the current filter and page.

• Pagination Navigate through pages of 30 entries each using the Prev/Next buttons.

Each row in the audit list shows:

• Timestamp The date and time when the action occurred, formatted in your browser locale.

• Actor The admin or investor who performed the action. If the system performed it automatically, the actor is shown as “System.”

• Action Label A color-coded label corresponding to the event type.

• Entity Details The type (Investor or Order) and the unique ID.

• Change Details Click an entry to expand a diff view:

  • New records: all initial values in green.

  • Updates: old values in red with a strikethrough, new values in green.

• Conduct compliance audits of investor onboarding and order processing.

• Investigate exceptions in payment reconciliation and KYC overrides.

• Monitor manual actions by admins, such as creating investors or orders.

For programmatic access to audit logs, see the interactive OpenAPI reference at https://om.bitbond.com/api/docs.

You can scope and paginate audit logs using query parameters on the /issuer/audit-logs endpoint:

• entityType (string) Filter by entity type (User for investors, Order).

• entityId (string) Filter by a specific entity ID.

• actorId (string) Filter by the ID of the admin or system actor.

• offeringId (string) Scope logs to a particular offering. Only entries for orders and investors related to that offering are returned.

• page (integer) Page number for pagination (default: 1).

• limit (integer) Number of entries per page (1–100, default: 50).

Example:

The response includes an array of log entries plus metadata:

For details on each log field, refer to the OpenAPI reference.

Accessing the Audit Trail

Event Types

Filtering and Searching

Reviewing Entries

Use Cases

API Access

With MCP, Token Tool becomes accessible to any MCP-compatible agent or environment.

Through MCP, Token Tool exposes its core functionality, including:

• Create tokens (ERC-20, SPL Token-2022)

• Manage token lifecycle (mint, burn, pause, transfer ownership)

• Create and distribute NFTs

• Configure token sales

• Interact with deployed contracts

All actions map directly to Token Tool’s underlying API and result in on-chain transactions.

• MCP Client (Agent) initiates actions

• MCP Server (Token Tool) exposes available capabilities

• Token Tool API executes the request

• Blockchain finalizes the transaction

• Automated token launches Trigger token creation based on predefined conditions

• AI-driven token operations Manage supply, distributions, or permissions programmatically

• Conversational interfaces Create and manage tokens through chat-based systems

• Workflow automation Combine token issuance with off-chain systems (e.g. KYC, analytics, notifications)

1. Set up the MCP server https://github.com/bitbond/token-tool-mcp

2. Connect an MCP-compatible agent or environment

3. Configure wallet or custody for transaction signing

4. Execute Token Tool actions via MCP

• Non-custodial Token Tool does not manage private keys. Transactions must be signed via your wallet or custody provider

• Execution layer Token Tool handles token issuance and contract interaction. External systems are responsible for compliance, distribution, and business logic

• On-chain finality All actions executed via MCP result in verifiable blockchain transactions

The MCP integration extends Token Tool into AI-native environments:

• Standardized agent access

• Programmatic token operations

• Seamless integration into automated systems

Token Tool remains the issuance and execution layer, now accessible through AI-driven interfaces.

What is MCP?

Supported Capabilities

How It Works

Example Use Cases

Getting Started

Key Considerations

MCP vs API vs UI

Summary

• Simultaneous exchange: Ensures the asset delivery and payment occur in a single, atomic transaction.

• Smart contract enforcement: Utilizes smart contracts to enforce the terms and conditions of the DvP, providing a transparent and immutable transaction record.

• Risk mitigation: Minimizes counterparty risk by ensuring that both parties fulfill their obligations simultaneously.

Below is a step-by-step guide on how to use the DvP settlement function.

1. Set the token price

   • Navigate to the DvP section and connect your wallet. Make sure you're connected to the right network on both Token Tool and in your wallet.

   • Choose the delivery token (the token that is being sold to a buyer) via the drop-down or by pasting the smart contract address. Then click continue.

   • Choose the payment token from the available options or enter a custom token address. Ensure that the token does not have holder rewards, transaction fees, or burn fees to be compatible with the DvP settlement function. If these features are available, make sure you set the rate to 0 before creating the DvP contract.

1. Set investment details

• Specify the price, indicating how many delivery tokens the buyer will get for one unit of the payment token. For example, 1 USDC = 100 NNT.

• Define the minimum and maximum investment amounts in the payment token (e.g., EURC). If no limits are required, set the value to 0.

• Set the DvP start time by selecting the date and time from the calendar.

1. Set DvP Duration

• Define the DvP duration in days, which will automatically calculate the DvP end time.

• The DvP contract owner address is by default the connected wallet. You can also change the DvP owner address to specify another wallet address that will manage the DvP settlement contract.

1. Agree to T&Cs and create DvP settlement

• Agree to the Token Tool Terms & Conditions by checking the respective box.

• Click on the "Create delivery vs payment" button to finalize and create the DvP contract.

• Confirm transaction in your wallet to pay fees. Once the transaction is processed, you will receive your DvP settlement contract details on the Token Tool Interface.

The DvP function on Token Tool is an essential feature for secure and efficient token transactions. By following the outlined steps, users can easily set up and manage DvP transactions, ensuring a seamless and risk-free exchange of digital assets and payments.

Once the DvP contract has been created and the transaction is processed, you will receive a pop-up modal displaying the DvP contract address and the blockexplorer link of the transaction. Make sure to save the DvP contract address as you will need to be able to manage the DvP contract:

To manage an existing DvP contract, simply go to the Delivery vs Payment page on Token Tool and paste the DvP contract address under the "Display existing Delivery vs Payment" section.

After that, click "Continue" and you will be redirected to the Delivery vs Payment page. This page serves as the DvP contract management section for the DvP contract owner (i.e. the seller), and as the buyer interface through which the token can be bought via the DvP contract:

In order for the buyer to be able to buy tokens, the DvP contract must first be topped up with the desired token amount. To do so, scroll down to the "Manage DvP" section and click the "Top up" button:

Insert the amount to be topped up and then click "Submit". You will need to approve access to tokens in your wallet in an initial step. Once the approval transaction is processed, click "Submit" again and approve the transaction in your wallet to finalize the top up.

After the transaction is complete, you will receive a success message and the DvP contract balance will be updated accordingly:

The DvP contract is now ready for buyers to buy the tokens. You can redirect buyers to the DvP Page Link for them to start buying your tokens. They can simply insert amount to buy and confirm the transaction in their wallet after clicking "Buy".

When a buyer buys a token from the DvP contract, the transaction is settled instantly via so-called "atomic swaps". This means that, after the transaction is processed by the network, there will be a simultaneous exchange of assets. The seller will automatically receive the funds to the wallet address owning the DvP contract; and the buyer will receive the tokens from the DvP contract address to the wallet connected.

Delivery versus Payment (DvP) Settlement function on Token Tool

Steps to create DvP settlement contract:

Funding DvP Contract

After you have specified these details click on Create NFT and sign the transaction from your wallet.

Once you have created the NFT contract, a success modal appears. Save both the URL of the NFT minting page and the NFT asset address (also called NFT smart contract address). You will need them later.

After you have saved the URLs, go to Manage NFT in order to add media via direct upload or by providing metadata links. NFTs can only be minted after media has been added. If you try to mint NFTs before you have added media, the minting will fail with an error.

Define the following parameters of your single asset NFT:

• Image file or image URL: This is the image that you would like to tokenize. It is recommended to upload your file to make sure the image is always available. Uploading will happen to IPFS. If you provide a media URL you will have to make sure that the media file is always available and its URL does not change, otherwise your NFT will not display anything.

• Name: This is the name of your NFT, use something descriptive such as Berlin wicked art exhibition ticket 2023.

• Symbol: The symbol can be something shorter such as BA2023.

• Description: Describe what the NFT is about, potentially say something about the creator or the collection.

• Enable public minting: Enables NFT minting for everybody after initial NFT creation. If this stays disabled, only the NFT creator can mint this NFT.

• Start time: From this time on your NFT can be minted. If empty, there is no time limit and NFTs can be minted immediately.

• End time: The NFT can be minted until this time. If empty, there is no time limit.

• Mint price: This is the price to mint one NFT specified in the native cryptocurrency of the selected blockchain (e.g. ETH if Ethereum has been selected, MATIC if Polygon has been selected etc.). If the price is set to 0, minting is free. Fees are paid by the wallet that is minting the NFT and are transferred directly to the creator’s wallet. Token Tool does not receive the mint price.

• Max NFT mint amount per user: Maximum amount of this NFT that can be minted per user. If set to 0, there is no limit and an infinite number of NFTs can be minted per user. The NFT creator can always mint an unlimited amount of the NFT (up to the global maximum).

• Global max mint amount: This is the global total maximum supply of this NFT. If set to 0, there is no limit and an infinite number of NFTs can be minted.

After you have specified these details, you can create your NFT. Your wallet will notify you and you will be asked to confirm the transaction.

After the NFT has been created successfully, you will see a modal with a NFT minting page and the NFT asset address which links to the block explorer.

The NFT minting page is particularly important. From here you can view your NFT and mint it. You can also send your audience to this page so that they can mint your NFT.

Share this page with users who you want to make NFT minting accessible to. You can also embed this page into your website via an iframe.

In case you missed the modal or forgot to save the NFT minting page, you can go to Manage NFT to see and manage all your NFTs.

Create NFT collection

Create NFT from single asset

1. You sign up and pick a plan Create your issuer account at https://om.bitbond.com and choose a plan:

   • Free: 1 offering, up to 5 investors, up to 3 team members, cannot publish live offerings, no custom domain, no payment processing, Bitbond branding shown on the invest page.

   • Professional Monthly or Professional Annual: up to 5 offerings, up to 1,000 investors, up to 3 team members, can publish live offerings, supports custom domains, payment processing enabled, no Bitbond branding.

   • Enterprise: unlimited offerings, investors, and team members; includes all Professional features, plus dedicated support and custom contractual terms. You can upgrade Free → Professional from the . For Enterprise inquiries, contact .

2. You configure your setup Add your bank details, connect payment providers (bank transfer, card via Checkout.com, hosted crypto via Coinbase Commerce, direct on-chain stablecoin), configure KYC integration with or , and set your investor wallet policy (byo_only, investor_choice, or custodial_only with Tangany).

3. You create an offering Define token details, pricing, investment limits, sale dates, payment methods, and compliance requirements.

4. You customize the Invest Page Use the Invest Page Builder (on the Invest Page tab) to add a project description, team members, roadmap, documents, and external links.

5. Optionally generate an embeddable widget Create a checkout or portfolio widget to integrate the investment flow on your own website.

6. Investors visit your invest page or widget and invest They sign up, complete KYC, choose a payment method, and place their order. Investors can also view their positions in the portfolio page or via the portfolio widget.

7. You manage orders and distribute tokens Track payments, reconcile bank transfers via CSV upload, and export a CSV of funded investor addresses for token distribution via the Bitbond Token Tool.

8. Optional manual operations Administrators can manually create or update investor profiles (including KYC status), add or modify orders using manual payment methods in the Orders tab, and make other adjustments as needed.

If you have questions about using the Offering Manager, refer to the sections in this documentation. For technical issues or account-related requests, contact the Bitbond support team.

Who Is It For?

Key Capabilities

How It Works

Getting Help

Below the summary cards, a breakdown chart shows confirmed (paid) revenue by payment method. For each method—bank transfer (SEPA/wire), card payments via Checkout.com, crypto payments via Coinbase Commerce, direct on-chain stablecoins, or Manual—you can see:

• Total amount received

• Number of orders

This helps you compare which rails are most popular with your investors.

Below the charts, a table lists each offering with these columns:

• Offering name and status The name of the offering and its current status (Draft, Active, or Closed).

• Confirmed Total confirmed (paid) investment for the offering.

• Pending Total pending investment awaiting payment or confirmation.

• Progress Percentage and progress bar showing how much of the hard cap has been reached.

• Orders / Days left Total number of orders (across all statuses, including pending, paid, refunded, and cancelled) and days remaining until the offering ends (or “Ended”).

Click View on any offering to open its detail page, where you can:

• Manage offering settings (including support for multiple blockchain networks such as EVM and Solana and configure your investor wallet policy—BYO-only, investor choice, or custodial-only via Tangany).

• View, filter, and manually create orders (select Manual as the payment method).

• Review offering-scoped activity in the Audit Trail.

• Edit the investor Invest Page in the Invest Page Builder tab and configure KYC requirements (powered by or ).

• New Offering — Create a new token sale.

• View — Open an individual offering’s detail page.

Use the sidebar to access all sections:

• Dashboard — Overview page described above.

• Offerings — List and manage all offerings; view details, orders, and settings.

• Investors — View, edit, and create investor profiles; manage KYC status.

• Audit Trail — Review platform and offering activity logs, with offering-scoped filtering.

• Partners — Manage partner organizations and referral relationships.

• Team — Manage team members with account access.

• Billing — View your current plan, upgrade self-serve from Free to Professional, or contact sales for Enterprise.

• Settings — Configure organization details, payment methods (bank transfers, card payments via , crypto payments via , and on-chain stablecoin payments), and KYC integrations (Sumsub and Blockpass).

For full API reference, see the interactive OpenAPI spec at https://om.bitbond.com/api/docs.

Issuer Dashboard

Summary Cards

Payment Method Breakdown

Offerings Table

Quick Actions

Navigating the Admin Panel

Start by selecting the network of choice and connecting your wallet. After heading to the "Airdrop Token" page, select the "Airdrop" tab.

Next, choose whether you want to distribute an equal amount of tokens to each holder regardless of their current token holdings. Or, if you would like to airdrop an amount that is proportional to the token holder's balances (pro-rata distribution).

Insert the contract address of the token based on which you wish to Airdrop funds to its holders. Please note that the Airdrop will only work, if the base token has less than 5,000 holders. If the base token has more holders, the transaction will not work. Get in touch with us in this case.

Then insert the amount that each holder will receive.

After that, specify the contract address of the token that you want to airdrop to holders. You have to hold a sufficient amount of this token in your wallet so that you can airdrop it.

Once the information is extracted from the network, you will see the list of addresses that will be receiving the token, alongside the amounts. Double check whether everything is correct and proceed to approve and send the transaction.

If you selected the option to airdrop funds proportionally (pro-rata) based on the token holder balances, insert the total number of tokens you wish to be airdropped pro-rata across all holders based on their holdings.

Once the information of holders balances is retrieved from the network, you will get the list of recipient addresses, alongside the amount they will receive based on their holdings. Double check whether everything is correct and proceed to approve and send the transaction.

Review details and click continue. You will then be redirected to the next page where you will find the list of recipients and the amounts. You can decide to manually remove certain addresses from receiving the distribution of funds.

You can then review all details in the summary section. Once ready, click on "Approve" and sign the transaction in your wallet to give access to the token.

After the transaction is processed and you give access of tokens to the contract, click on "Send" and the tokens will be sent to holders after you confirm transaction in your wallet and pay fees. You will get a message that tokens were successfully sent. You can copy the list of addresses and amounts that were distributed to token holders and store it separately for your own reference.

Mainnets:

• Ethereum

• BNB Smart Chain

• Base

• Avalanche

• Fantom

• Optimism

• Arbitrum

• Polygon PoS

Testnets:

• Ethereum Sepolia

• Avalanche Fuji

• Base Sepolia

• Optimism Sepolia

Autofill recipients: equal amounts

Autofill recipients: proportional amounts

Sending approval and confirmation

Supported Networks

Current Plan

Active Discounts

Change Billing Cycle

Cancel Subscription

Upgrade Options

Payment Methods

Billing Details

Invoice History

Usage & Add-Ons

Data Export

Withdraw tokens from the locker

Verifying locker contract source code

Navigating Gas Fees in Token Tool Usage

Token Tool contract addresses

Test Token Tool for free on testnets

These chains are all share the technical foundation and compatibility with the Ethereum Virtual Machine. You can find a comprehensive list of EVM chains here. The ones listed below are the ones that are supported by Bitbond Token Tool.

Ethereum is a global, open-source platform for decentralized applications (dApps) on which you can write code (usually referred to as a smart contract) that controls digital value and runs exactly as programmed. The Ethereum mainnet is the most popular blockchain for asset tokenization because of the apps you can write on top of it.

Etherum is also the most popular blockchain that uses smart contracts. Etherum is the best choice whenever we need to set parameters for the smart contracts. The most popular applications for the Ethereum blockchain are decentralized finance (DeFi) and asset tokenization.

Avalanche has four basic interrelated mechanisms that compose structural support of the consensus tool. These four mechanisms are Slush, Snowflake, Snowball, and Avalanche.

By using randomized sampling and metastability to ascertain and persist transactions, It represents a new protocol family. Although the original paper focused on a single protocol, namely Avalanche, it implicitly introduced a broad spectrum of voting-based, or quorum-based consensus protocols, called the Snow family.

While Avalanche is a single instantiation, the Snow family seems to be able to generalize all quorum-based voting protocols for replica control. Unlike prior quorum-based work, the Snow family enables arbitrarily parametrizable failure probability at the quorum intersection level.

Standard quorum-based protocols define this failure probability to be precisely zero, but by introducing errors in the quorum intersection, a larger set of consensus protocol design is available.

The Polygon PoS (Proof of Stake) network is Ethereum-native, aligned to be interoperable with all of Ethereum’s existing and even future infrastructures while offering a framework for its interoperability with other layer-2 solutions, sidechains and sovereign blockchains.

The Polygon network is thus also categorized as a layer-2 aggregator, aiming to create a multichain ecosystem of Ethereum-compatible blockchains with superior interoperability.

BNB Chain is an innovative solution to bring programmability and interoperability to the Binance Chain. BNB Chain (formerly Binance Smart Chain or BSC for short) relies on a system of 21 validators with Proof of Stake Authority (PoSA) consensus that can support short block time and lower fees.

The most bonded validator candidates of staking will become validators and produce blocks. The double-sign detection and other slashing logic guarantee security, stability, and chain finality.

BNB Chain also supports EVM-compatible smart contracts and protocols. Cross-chain transfer and other communication are possible due to native support of interoperability.

Binance DEX remains a liquid venue of the exchange of assets on both chains. This dual-chain architecture will be ideal for users to take advantage of the fast trading on one side and build their decentralized apps on the other side.

Arbitrum is a Layer 2 scaling solution for Ethereum that offers increased speed, efficiency, and privacy. It uses off-chain computation and on-chain enforcement to process transactions quickly and securely.

The platform supports a wide range of use cases and is interoperable with Ethereum-based solutions. This allows for seamless communication and opens new opportunities for developers.

Arbitrum's combination of speed, efficiency, and privacy make it a leading platform in the decentralized space.

Optimism is a Layer 2 scaling solution for Ethereum, designed to bring increased speed, efficiency, and scalability to the Ethereum network.

It uses an innovative technique called Optimistic Rollups to process transactions off-chain, reducing congestion on the main Ethereum network. Optimism also offers increased security compared to traditional Ethereum-based solutions.

This makes it an ideal platform for decentralized finance and other high-volume use cases. With its commitment to Ethereum compatibility, Optimism is poised to become a leading platform in the decentralized space.

Base is an Ethereum Layer 2 (L2) network designed to be secure, affordable, and developer-friendly. Built on top of the OP Stack developed by Optimism, Base leverages the security of the Ethereum blockchain while offering faster transaction processing and lower fees. This makes it an attractive platform for building and deploying decentralized applications (dApps).

One of Base's key features is its focus on ease of use for developers. It integrates seamlessly with Coinbase products and tools, providing developers with access to a large user base and various resources.

These chains are built on protocols that are independently developed and technically different from the Ethereum protocol and the Ethereum Virtual Machine.

Stellar was created in 2014, after Bitcoin but before Ethereum. Stellar uses a more environmentally-friendly consensus mechanism than many other chains and was designed specifically for remittances and payments. Therefore it has “cash-like” delays between transactions (i.e. very short) and it’s more or less free to use (transactions cost way less than a penny).

Like Ethereum, Stellar allows you to issue other custom assets or tokens (say, a digital representation of a dollar or a peso) and to trade them very easily within the network.

Stellar has the Stellar Decentralized Exchange (SDEX) built directly into the protocol which provides a convenient way for secondary trades.

Solana is a high-performance blockchain known for its fast transaction throughput and low fees, making it particularly well-suited for consumer-facing applications and high-frequency trading environments. It achieves this performance through innovations like Proof of History (PoH), which allows the network to process thousands of transactions per second. Solana supports multiple token standards, including the original SPL (Solana Program Library) standard and the newer Token-2022, which introduces advanced features like transfer hooks, interest-bearing tokens, and enhanced access control. Due to its scalability and growing ecosystem, Solana is increasingly considered for asset tokenization and DeFi applications, despite not being EVM-compatible.

XRPL is a public blockchain and decentralized Layer 1 protocol that is optimized for the efficient transfer of value. It is known for fast settlement times, low transaction costs, and a mature ecosystem focused on payments, tokenization and financial use cases. XRPL was designed with asset issuance and exchange in mind. It enables the creation of custom tokens directly on-chain and provides built-in functionality that can be useful in tokenization scenarios, especially where efficiency, predictable transaction costs and reliable settlement are important. Due to these characteristics, XRPL is increasingly relevant for tokenization use cases involving real-world assets, utility tokens and payment-related applications. It offers an alternative to both EVM-compatible networks and other non-EVM chains, depending on the specific requirements of the issuer and the intended user experience.

Protocols

EVM blockchains

Ethereum

Avalanche

Polygon PoS

BNB Chain

Arbitrum

Optimism

Base Chain

Non-EVM blockchains

Stellar

Solana

XRPL

Many leading wallet solutions make the integration significantly easier by via a SDK or UI to provide the smart contract ABI. This allows smart contract functions to be called directly. Operators are able to review the details of the transaction prior to giving approvals and custodians can apply predetermined organisational governance policies.

Token Tool is engineered with an API-first approach, ensuring a seamless and direct interface for all interactions. Just as the ERC20 token lifecycle actions allow direct API interactions, the same applies to other features offered by Token Tool. These include NFTs creation and management, token sales, and payment automation contracts – all of which are readily accessible and manageable via the Token Tool API.

Custody-agnostic solution

Token lifecycle actions

API-centric approach

After sending the invitation, the new member will appear in the team table with Status = Pending until they accept the invite and complete their sign-in. The invited person will receive an email with instructions and a link to the Accept Invite page. They can choose to sign in with email/password or Google SSO. Once they’ve accepted, their status changes to Active and they gain the access level associated with their role.

In development mode, the invite response includes an inviteUrl field so you can copy the invitation link directly.

Only the account owner (or a super-admin) can invite team members. Seat limits apply only to Issuer Admin roles; you can invite unlimited Issuer Viewers on any plan.

The team table shows all current, invited, and former team members with the following information:

• Member — Name (or a placeholder “—” if no name provided) and email address

• Role — Issuer Admin or Issuer Viewer

• Status —

  • Active — has accepted the invite and can log in

  • Pending — invited but has not yet accepted (no password set)

  • Deactivated — access revoked after acceptance

• Joined — The date the member was added

• Actions —

  • 🔄 Resend Invite (for Pending invitations only)

  • 🗙 Deactivate (for Active members)

Invited members who have not yet accepted appear as Pending, with Resend Invite and Delete Permanently actions available. Your own account is marked with You in the Actions column and cannot be deactivated or deleted.

If a team member was invited but has not yet joined (inactive and no password set), you can resend their invitation:

1. Click the resend icon (🔄) next to the member’s name

2. A new email will be sent, invalidating any previous invite link

In development mode, the API response includes the new inviteUrl for easy testing.

To revoke a team member’s access without deleting their data:

1. Click the deactivate icon (🗙) next to the member’s name

2. Confirm the action

Deactivated members can no longer log in, but their historical data (such as any actions they performed) is preserved for audit purposes.

Only the account owner (or a super-admin) can deactivate other members. You cannot deactivate yourself while you are the account owner — you must transfer ownership first.

If a previously deactivated member needs to regain access:

1. Click the reactivate icon (✔️) next to the member’s name

Their access is restored immediately and they can log in again.

You can permanently remove a team member’s account only if they are Pending or Deactivated and have no order history. Permanent deletion frees the email address so it can be used to register with another organization.

1. Click the delete icon (🗑️) next to the member’s name

2. Confirm the permanent deletion

This action cannot be undone.

Account owners (and super-admins) can change the role of an Active team member at any time:

1. Click the change role icon (🔁) next to the member’s name

2. In the dialog, select Issuer Admin or Issuer Viewer

3. Confirm the change

Promoting a user to Issuer Admin is subject to your plan’s seat limit. If you’ve reached the limit, you’ll see an error suggesting you invite as a Viewer or upgrade your plan.

To transfer account ownership to another Active Issuer Admin:

1. Click the transfer ownership icon (👑) next to the member you want to make the new owner

2. Confirm the transfer

After transfer, the selected member becomes the account owner and you lose owner privileges (you remain an Issuer Admin). You cannot transfer ownership to a Pending or Deactivated member.

All team management operations are exposed via the public API. You can explore and test these endpoints in the interactive OpenAPI reference: https://om.bitbond.com/api/docs

The main endpoints include:

• List members — GET /api/issuer/team

• Invite member — POST /api/issuer/team/invite

• Resend invitation — POST /api/issuer/team/:id/resend-invite

• Deactivate member — DELETE /api/issuer/team/:id

• Reactivate member — PATCH /api/issuer/team/:id/reactivate

• Change member role — PATCH /api/issuer/team/:id/role

• Transfer ownership — POST /api/issuer/team/:id/transfer-ownership

• Permanently delete member — DELETE /api/issuer/team/:id/permanent

If you need to review an audit trail of team actions, see the Audit Log page for offering-scoped filtering and a complete history of administrative activity.

Inviting a Team Member

Viewing Team Members

Resending an Invitation

Deactivating a Team Member

Reactivating a Team Member

Permanently Deleting a Team Member

Changing a Team Member’s Role

Transferring Account Ownership

API Endpoints

• Tangany (tangany.com)

• Fireblocks (fireblocks.com)

Each offering can override the default wallet policy:

1. Go to Offerings and select an existing offering or create a new one.

2. Open the Invest Page tab in the Invest Page Builder.

3. In the Wallet Policy section, choose one of:

   • BYO only (byo_only)

   • Investor choice (investor_choice)

   • Custodial only (custodial_only)

4. Click Save.

The wallet options displayed during checkout depend on the policy:

• BYO only (byo_only): Investors must connect an external wallet (e.g. MetaMask) to complete a purchase.

• Investor choice (investor_choice): Investors can either connect their own wallet or opt for a custodial wallet without an external connection.

• Custodial only (custodial_only): A custodial wallet is created automatically after KYC approval. No external wallet connection is required.

• Tangany supports EVM chains only. For details, visit Tangany.

• Fireblocks supports a wide range of chains (EVM, Solana, and others) and all assets available in your Fireblocks vault. Use the Chain Asset Overrides field in the integration settings to select which asset ID to use on each chain.

1. After an investor completes KYC (via Sumsub or Blockpass), a custodial account is created automatically.

2. When the investor places their first order on a new chain, a custodial wallet for that chain is provisioned in the background.

3. Provisioning runs asynchronously; the status updates to active or failed once complete.

4. You can also manually provision or retry provisioning in the Admin UI.

• To provision a custody account before checkout:

  1. Go to Admin > Investors and select an investor.

  2. In the Custody section, click Provision Now.

     Note: The investor must have an approved KYC status before provisioning can succeed. This action is idempotent — if an account already exists, it will return the existing account.

• To retry failed provisioning jobs:

  1. In the same Custody section, locate the failed account or wallet.

  2. Click Retry to re-queue all failed account and wallet provisioning jobs for that investor.

• Investors list: Navigate to Admin > Investors, select an investor, and open the Custody section to view:

  • Account status (pending, active, failed)

  • Wallet list with chain, address, status, and error details

  • Retry controls for failed items

• Orders list: Under Admin > Offerings > select an offering > Orders, open an order to see:

  • Custodial wallet address (if used)

  • Provisioning status and retry options for the associated wallets

For details on custody endpoints, see the interactive OpenAPI reference at https://om.bitbond.com/api/docs.

Configure a Custody Provider

Set the Investor Wallet Policy per Offering

Investor Checkout Experience

Supported Chains

Custodial Wallet Provisioning Lifecycle

Manual Provisioning and Retry

Monitor Custody Status

API Reference

• {tenantId} – first 8 characters of your tenant ID

• {userId} – first 8 characters of the investor’s user ID

Fireblocks

Profile settings

Profile completion

Tokens

NFTs

Swaps

I forgot my password. How do I reset it? Use the password reset link on the login page (/admin/forgot-password) to receive a reset email. Follow the link in the email to open the Reset Password page (/admin/reset-password) and set a new password. If you logged in with Google SSO, you do not have a separate password — simply use the Google sign-in option.

I set up two-factor authentication and lost my authenticator app. What do I do? Use one of the backup codes that were provided when you enabled 2FA. Each backup code can only be used once. If you have no remaining backup codes, contact Bitbond support for assistance.

Can I switch from email/password login to Google SSO? Yes. If your account email matches a Google account, you can use either login method. The system links both methods to the same account automatically.

I received an invitation to join the Offering Manager. How do I accept it? Follow the link in the invitation email to open the Accept Invitation page (/admin/accept-invite). Complete the form to set your login credentials. Once accepted, you can log in to the admin panel.

How do I update my account details? Go to Account in the admin sidebar or navigate to /admin/account to update your name, email, and profile settings.

What is the difference between a soft cap and a hard cap? The soft cap (funding target) is the minimum amount you aim to raise. The hard cap is the absolute maximum the offering will accept. The progress bar on the investor Invest Page shows progress toward the hard cap.

What is the Invest Page Builder? The Invest Page Builder is the admin interface for customizing your offering’s Invest Page. On the Invest Page tab of an offering, you can edit text, images, colors, and layout that investors see when they visit your Invest Page.

Can I edit an offering after it is active? Yes, you can update most offering settings while it is active, including payment methods, documents, discount tiers, and Invest Page content. However, changing fundamental parameters (such as pricing or caps) on a live offering should be done carefully, as it may affect existing investors’ expectations.

What is the investor wallet policy? When creating or editing an offering, you can choose the investor wallet policy:

• byo_only – Investors must bring their own wallet address.

• investor_choice – Investors can choose between their own wallet or a custodial wallet.

• custodial_only – Investors are provided a custodial wallet by your configured custody provider. To use custodial wallets, configure Tangany () in Settings. Custodial wallets are currently supported on EVM-compatible chains only.

What happens when I change an offering's status to Closed? Closing an offering prevents new investments. Existing orders are not affected — pending orders remain pending, and paid orders remain paid. You can still manage orders, send reminders, and process refunds after closing.

How do I make an offering visible to investors? Change the offering status from Draft to Active. Only active offerings are accessible to investors via their Invest Page URL:

Can I embed a checkout widget on my website? Yes. Each offering provides an embeddable widget at:

You can include this URL in an iframe or script tag to integrate the investment flow directly into your own site.

How can I view the audit history for an offering? On the offering detail page, click Audit Trail to see all events related to that offering, including configuration changes, document uploads, and status updates. You can filter by date or event type.

Why is a payment method greyed out when I create an offering? A payment method is unavailable if the required credentials have not been configured in Settings. For example:

• Bank transfer requires bank details (bank name, IBAN, BIC).

• Card payments require Checkout.com keys (https://www.checkout.com).

• Coinbase Commerce requires an API key (https://www.coinbase.com/commerce).

• Stablecoin requires an extended public key for each supported chain (EVM-compatible, Solana, etc.).

Configure the missing credentials in Settings and the payment method will become available.

How does bank transfer reconciliation work? When investors pay by bank transfer, they are given a unique reference code (e.g., OM-1234-ABCD) to include in their transfer subject line. To reconcile payments, export a CSV from your bank, then upload it on the offering detail page. The system matches transactions by reference code and automatically marks matching orders as Paid.

What if an investor sends a bank transfer without the reference code? The automatic reconciliation will not match the transaction. You will need to manually identify the payment and update the order status to Paid from the Orders page.

How are Coinbase Commerce payments verified? When an investor pays through Coinbase Commerce, the system uses webhooks to receive payment status updates. Once a matching payment is confirmed, the corresponding order is automatically marked as Paid. Failed or pending payments must be reviewed on the Orders page.

How are stablecoin payments verified? Each investor receives a unique deposit address derived from your extended public key. The system monitors multiple chains (EVM-compatible, Solana, and others) for incoming transactions to that address. When a matching deposit is detected and confirmed, the order is automatically updated. Payments that do not match the expected amount are flagged for manual review.

What is the “Manual” payment method and when should I use it? The Manual payment method lets you record offline or custom payment arrangements. No automatic reconciliation is performed — you create the order and later mark it as Paid or update its status manually from the Orders page.

Which KYC providers are supported? The Offering Manager integrates with Sumsub (https://sumsub.com) and Blockpass (https://www.blockpass.org). You can configure one or both in Settings and require verification on a per-offering basis.

Is KYC required for all offerings? No. KYC is optional per offering. When creating or editing an offering, you can choose whether to require KYC verification. If disabled, investors can invest without identity verification.

What are blocked countries? Blocked countries are jurisdictions whose residents are prevented from investing in your offering. This is enforced during the KYC verification process. You configure the blocked country list when creating or editing an offering.

What is the cancellation period? The cancellation period is the number of days an investor has to cancel their order after placing it. For example, a 14-day cancellation period means investors can cancel within 14 days. This is often required by financial regulations. Set it to 0 if no cancellation period applies.

Where can I view the system activity and audit trail? The Audit Trail page in the admin panel (/admin/audit-trail) shows all system events, including offering updates, order status changes, investor profile edits, and more. Use the filters to scope entries by offering, investor, or event type.

How do I filter the audit log by offering? On the Audit Trail page, open the Offering filter dropdown and select the offering you want to inspect. The log will refresh to show only events related to that offering.

How do I filter the audit log by investor? On the Audit Trail page, open the Investor filter dropdown and select the investor you want to inspect. The log will refresh to show only events related to that investor.

How do I manually create an investor? Go to Investors in the admin sidebar and click New Investor. Fill in the investor’s details, including name, email, wallet addresses, and KYC status. The investor record is created immediately and appears in the list.

Can I edit an investor’s profile or KYC status after creation? Yes. On the Investors page, open an investor’s profile to update details such as wallet addresses, contact information, and KYC status. All changes are logged in the audit trail.

Which blockchain wallets can I store for an investor? You can add multiple wallet addresses per investor across supported chains, including EVM-compatible chains (Ethereum, BSC, etc.) and Solana. Specify the chain for each address when creating or editing the investor profile.

How do I manually create an order for an investor? Navigate to an offering’s Orders page and click Create Order. Select the investor, enter the amount, choose a payment method (including Manual), and set the status. The new order appears in the list and is tracked like any other order.

Can I manually mark an order as Paid? Yes. On the Orders page, click the status update button next to a Pending or Processing order to mark it as Paid. This action is logged in the audit trail.

How do I send a payment reminder to an investor? On the Orders page, click the email icon next to a Pending order. The system sends a reminder email to the investor with their order details and payment instructions.

What does a “flagged” stablecoin payment mean? A stablecoin payment is flagged when the received amount does not match the expected amount (either overpaid or underpaid). Flagged payments require manual review — check the transaction details on the blockchain explorer and update the order status as appropriate.

How do I export investor wallet addresses for token distribution? Navigate to the offering detail page and click Export CSV. The export generates a CSV file with columns: address, amount, and chain. Only investors with a confirmed (Paid) payment and a valid wallet address are included. Use this file with the Bitbond Token Tool for bulk token distribution.

Are my API keys and credentials stored securely? Yes. All sensitive credentials (API keys, extended public keys, webhook secrets) are encrypted with AES-256 before being stored in the database. They are never exposed to the frontend or included in API responses.

Can I use a custom domain for my investor pages? Yes. Go to Settings and enter your custom domain in the Custom Investor Domain section. You will need to configure a CNAME DNS record pointing your domain to om.bitbond.com. Once DNS propagates, your investor pages will be accessible at your custom domain.

How do I generate a new API key? Go to Settings, scroll to the API Access section, and click Generate New API Key. The key is shown once — copy it immediately.

How do I view billing information and manage my subscription? Go to Billing in the admin sidebar or navigate to /admin/billing to view invoices, payment methods, and your current subscription plan.

What plans are available and what are their limits?

• Free – 1 offering, up to 5 investors, up to 3 team members, cannot publish offerings live, no custom domain, no payment processing, Bitbond branding shown on the Invest Page.

• Professional Monthly & Annual – Up to 5 offerings, up to 1,000 investors, up to 3 team members, can publish offerings live, custom domain supported, payment processing enabled, no Bitbond branding on the Invest Page.

• Enterprise – Unlimited offerings, investors, and team members; all Professional features included, plus dedicated support and custom contractual terms.

How can I upgrade my plan?

• To upgrade from Free to Professional (Monthly or Annual), go to Billing in the admin sidebar or navigate to /admin/billing.

• For Enterprise inquiries, contact Bitbond sales at https://www.bitbond.com/contact.

Where can I find the public API documentation? The public API is documented as an interactive OpenAPI reference at https://om.bitbond.com/api/docs.

What is the base URL for the public API? All public API requests use the base URL:

What access do team members have? All team members within a tenant have full access to the admin panel, including offerings, investors, orders, settings, and team management. There are no role-based permission differences among team members.

How do I invite a new team member? Go to Team in the admin sidebar and click Invite Team Member. Enter the member’s email address and send the invite. They will receive an email with a link to accept the invitation and set their login credentials.

How do I accept an invitation to join the Offering Manager? Follow the link in the invitation email to open the Accept Invitation page (/admin/accept-invite). Complete the form to set your login credentials. Once accepted, you can log in to the admin panel.

Can I remove a team member without losing their data? Yes. Deactivating a team member revokes their login access but preserves all historical data associated with their account. If you need to permanently delete a team member (e.g., invited by mistake), you can do so only if they have no associated order history.

General

Account & Login

Offerings

Payment Methods

KYC & Compliance

Activity & Audit Log

Investors & Orders

Settings & Security

Plans & Limits

API & Integrations

Team Management

After signing up, you’ll be taken to the admin login page. Use the email and password you provided, or click Sign in with Google if you signed up via Google SSO.

If a team member is invited as an administrator, they will receive an email with a link to the Accept Invitation page. On that page, they can either:

• Set a password for email/password login, or

• Sign in with Google using Single Sign-On (SSO)

Once they complete this step, they can use either login method on subsequent visits.

Access the Offering Manager admin at https://om.bitbond.com/admin/login or by clicking Login on the homepage.

Sign in with:

• Email and password — Enter the email address and password associated with your account.

• Google SSO — Click Sign in with Google and authenticate with the same Google account you used at signup or invite acceptance.

• Forgot password — If you forget your password, click Forgot password?, enter your registered email, and follow the link in the email to reset your password. After resetting, you’ll see a confirmation banner on the login page prompting you to sign in with your new password.

• Session expiration — If your session has expired from inactivity, a banner will prompt you to sign in again.

If you have two-factor authentication (2FA) enabled, you’ll be prompted to enter a 6-digit code from your authenticator app (TOTP). If you don’t have access to your authenticator, click Use a backup code on the verification screen and enter one of your one-time backup codes.

When you log in for the first time, you may see a Welcome page that suggests quick actions:

• Create your first offering

• Invite your team

• Read the documentation

• Get support

Click Go to Dashboard or Create your first offering to proceed.

Before creating your first offering, complete these essential setup steps:

Go to Account to update your email address, change your password, and configure two-factor authentication (2FA). You can enable or disable 2FA and view your one-time backup codes on this page.

Go to Billing to view your current plan and upgrade or downgrade. To move from Free to Professional Monthly or Annual, you can self-serve in the Billing area. To explore Enterprise, contact Bitbond sales at https://www.bitbond.com/contact.

Navigate to Settings → Organization and confirm your organization name and reply-to email address. The reply-to email is used as the sender for all investor-facing emails (order confirmations, payment reminders, etc.).

If you plan to accept bank transfers (SEPA or wire), go to Settings → Payments and enter:

• Bank name

• Account holder name

• IBAN

• BIC / SWIFT code

These details appear to investors during bank transfer checkout.

In Settings → Payments, set up any of the following:

• Checkout.com (https://www.checkout.com) — For card payments. Enter your secret key, public key, and webhook secret.

• Coinbase Commerce (https://www.coinbase.com/commerce) — For hosted crypto payments. Enter your API key and webhook shared secret. You can choose to settle proceeds in crypto or withdraw to fiat manually.

• On-chain Stablecoin Payments

  • EVM-compatible networks — Provide an Extended Public Key (xPub) from your HD wallet (e.g., Ledger, Trezor) to generate unique addresses per investor.

  • Solana — Provide a Solana public key to receive stablecoin deposits.

• Manual — Enable admin-entered manual payments for off-platform methods (e.g., cash, wire transfers not processed through a PSP).

If you want to provision wallets for investors, under Settings → Payments in the Custody Provider section, enter your Tangany credentials:

• Tangany (https://tangany.com) — API key and secret.

Per offering, you’ll select an investor wallet policy: BYO only, Investor choice, or Custodial only.

To verify investor identities, configure KYC providers in Settings → KYC:

• Sumsub (https://sumsub.com) — App token and secret key.

• Blockpass (https://www.blockpass.org) — API key and secret.

You can configure both and choose one per offering.

If others need admin access, go to Team and invite them by email. They’ll receive an invitation and can log in via email/password or Google SSO.

• Go to Investors to view, invite, or manually create investor profiles. You can edit details and update KYC status at any time.

• In Offerings, select an offering, open the Orders tab, and create or view orders. Use Create Order to manually record an order; select Manual if it’s an off-platform payment.

Track all admin actions in Audit Trail. Use filters to view entries by offering, team member, or action type.

The Offering Manager exposes a public REST API. Browse the interactive OpenAPI spec at https://om.bitbond.com/api/docs. The base URL for public API requests is:

Once your settings are configured, create your first offering in the Managing Offerings guide.

Sign up for an Offering Manager account

Accepting an Invitation (Additional Administrators)

Logging In

First Steps After Login

1. Manage Your Account

2. Manage Your Subscription

3. Review Organization Details

4. Add Bank Details

5. Configure Payment Providers

6. Configure Custodial Wallet Provider (Optional)

7. Set Up KYC Integration

8. Invite Team Members

9. Manage Investors and Orders

10. Review the Audit Trail

11. Explore the API

Next Steps

The Token Sale link Is the page where investors will submit their investments. Important: Investors should only invest using the official token sale page. They must not send funds directly to the token sale contract address.

The Token sale sharing/iframe embedding section under the Token sale information provides a code snippet that you can easily attach the public sale page to your website via an iframe.

For an additional cost, you can enable custom theme for your token sale page. This allows you to customize the colors of the token sale investor interface to fit your branding/website theme.

To enable custom branding, click on "Enable custom theme" and pay fees in your wallet. Once the transaction is complete, you will be provided with the customization assistant tool to help you set up the token sale page based on your requirements.

You can use it to generate the required link/iframe with the custom branding for your own use. Below is a overview example for which fields customize which parts of the sale UI:

You can see an example of how the iframe is implemented in this how to create a token presale blog post. Of course you can edit the parameters such as height and width.

This way you can create a website that describes your project, team, roadmap, use of proceeds etc. and embed the Token Sale page according to your own branding without the need to send investors to a separate website.

If you look for guidance on the to manage investor on-boarding, please go to this section of the Create Token Sale documentation.

To add investors to the whitelist you can either paste one or multiple addresses in the input field that opens after you click Add addresses. Alternatively you can upload a CSV file or a spreadsheet with all addresses.

Sometimes investors want to cancel their investment. In this case you may either want to grant a refund out of fairness or you may even be required to do so by law. In Germany for instance private investors have a right to cancel online purchases / investments for 14 days.

There are two ways how you can handle refunds:

• Blacklist the wallet address of the investor and send them their money back. In this case they won't be able to claim their tokens after the token sale is finished.

• When the token sale is over and the investor has claimed their tokens, ask them to send the tokens back to you and issue the refund in return.

Token sale is automatically finished when either of the two conditions occur:

• Specified sale duration is finished. The total investment is either above or below the softcap.

• Sale ends early due to all available tokens getting purchased (hardcap reached).

It is recommended to remind investors in any case after the token sale finishes. This way they will know that they can claim their tokens (if softcap was reached) or claim their funds (if softcap was not reached).

Investors simply claim their tokens or funds respectively from the same page where they invested.

As the token sale organizer you will want to withdraw the invested funds (if softcap was reached after the token sale ended or immediately after the hardcap was reached) or withdraw tokens (if softcap was not reached) from the token sale contract. If the softcap was reached but the hard cap was not reached, there will also be some remaining tokens. You can withdraw these as well under the Manage Token Sale functionality.

The following buttons are visible when you scroll all the way down. Note that the buttons become active after the token sale ends and the conditions for the withdrawals are met.

In the case you activated the "Burn unsold tokens" feature upon creating the token sale, you will need to manually click the burn button under the withdrawals section of the manage token sale:

If you enabled Auto Liquidity Listing during token sale creation, the management flow differs slightly from a standard token sale:

• You must ensure liquidity is provided according to the sale parameters.

• Once the sale ends, the creator has 7 days to trigger automatic liquidity addition on the token sale page. Failing to do so results in failure of the token sale. In such cases, investors will be able to claim refunds.

• After liquidity is added, investors are able to claim their tokens and directly start trading it. The creator can withdraw LP tokens from the manage token sale page.

In addition to the general standard token sale settings, token sales with auto listing have liquidity management settings:

When the sale ends, you must add liquidity

After adding liquidity, you can withdraw their LP tokens from the manage token sale. If LP tokens are locked, withdrawing will be possible once unlock date is reached:

Similarly to the standard token sale, you can withdraw funds and remaining tokens (or burn in case enabled).

Once completed, investors can claim their tokens from the same page they invested in. Your token is also immediately tradable on the chosen DEX.

Standard token sale (without auto listing)

Token sale information and token transfer

General settings

Public token sale page for investors

Investor on-boarding

Refunds

Finishing the token sale

Token Sale with Auto Liquidity Listing

Automatically adding liquidity

Withdrawing LP tokens

Basic token settings

Settings for the Core Token

Settings for the Advanced Token

Settings for the Asset Token

Open it by clicking at the transaction hash and then go to Internal txns. The address that's highlighted in the screenshot is the NFT contract address. Copy it and paste it into the field under Manage NFT to enter.

The first function that you will see under Manage NFT is the Verify token button.

Clicking this button will trigger the verification service for the smart contract in the main block explorer of the selected chain (e.g. Etherscan or polygonscan). When the token contract is verified, everybody can read and verify the smart contract of your token.

This is common practice and we recommend doing this. Here is an example of a verified NFT contract. Note that token verification may not always work on Fantom and testnets.

Note that in some cases for older NFTs the verification might not work because we have updated our smart contracts in the meantime. If you need your token contract to be verified nevertheless, contact us under one of the listed channels. When you send us the contract address of your token we will be able to trigger the contract verification manually.

The Verify token button remains visible after the verification has been completed successfully.

When you use single asset minting, you have already uploaded or linked your media file in the Create NFT step. With collection, NFTs adding media and further attributes is a separate step that you have to do under Manage NFT. This section describes how to do that.

Equally to single asset NFTs you will want to add one or most likely multiple media files in one of the following formats: img, jpg, png, gif or mp4. This is the media that you show on your NFTs.

You can have the media files on a regular web server. Then you will need to have the URL to each media file.

However, instead of hosting your media on a web server, we recommend uploading your files to IPFS. This way many other nodes will have a copy of your media which reduces the risk that your NFT will end up without its core graphical part.

Therefore, prepare to upload everything to IPFS by storing all media files in one folder and use ascending numbers as file names. If your media files are PNGs for example, name them 0.png, 1.png, 2.png etc. Use the same naming convention for other file types, e.g. 0.mp4, 1.mp4, 2.mp4 etc.

Each NFT needs to have a description. Describe what can be seen in the media or send a message to your audience. If the NFT represents a certain right or loyalty points, you add basic terms or a web address to further information to the description.

Moreover, most NFTs also have further attributes in a standardized format. In the screenshot you can see the attributes of Bored Ape #7292 on OpenSea. They include Background, Clothes and other attributes.

If you want to add similar attributes, you will have to use a separate JSON metadata file for each NFT. The file has to follow the JSON format. Here is the JSON metadata file for the Bored Ape #7292 above:

You can see that the image attribute contains an IPFS URI for the media file. If you want to open the image in a browser, you can do it via this link

https://ipfs.io/ipfs/QmXgtpxm5rMLkBqj9xbQb5w4GSy8vrLWvUP8kgenonYa4n

The fact that the JSON file includes the path to the media file means you can only complete your JSON files after you have uploaded your media files to IPFS. You will learn how to do that in the next section.

Just like you should have all your media files readily prepared in one folder, you will also need to have all your JSON files in one folder. Name them in a similar way to the media files: 0.json, 1.json, 2.json etc. You can skip the .json part in the file name but we do recommend to use it so that it's easier to see the file type.

There are several ways to upload data to IPFS. You are free to use whichever tool you want. Here is a selection of tools that let you do that (note: if you're an enterprise customer of Bitbond we can do the upload for you): Pinata, Moralis.

The most important aspect here is that both, your media files and your JSON files are in a folder (aka directory).

This could for example be the URI to your folder with image files (note that is just illustrative and not a real URI):

ipfs://qwertzuiop

Then this is what the image URIs will look like:

ipfs://qwertzuiop/0.png ipfs://qwertzuiop/1.png ipfs://qwertzuiop/2.png

The qwertzuiop part is called the CID (content identifier). When you upload media files as a folder, the CID for each file will be the same and only the last part of the URI changes.

The same goes for the JSON files where the folder would look something like this:

ipfs://asdfghjk

The list of JSON files would look like this:

ipfs://asdfghjk/0.json ipfs://asdfghjk/1.json ipfs://asdfghjk/2.json

The content of a fairly simple JSON file would look like this:

When you create the JSON files, it's up to you whether you customize the description and attributes for each NFT. You will however have to make sure to have the correct image URI in each JSON metadata file.

There are different ways to add media and metadata to your NFTs. The most important distinctions are Add one and Add many. If you have a larger collection you can go straight to Add many.

When you click Add one, you are adding media files to your collection one by one. You can add a custom description for every media file that you add.

You can also add the same image several times. One collection could for example consist of 12 NFTs. If you want to use 3 different images and for each image you want to have an equal amount of tokens, you will need to upload each image 4 times.

After you click the Submit button you will see this view:

It's important that you click Confirm addition. Only after you have done that and confirmed the transaction from your wallet, the metadata will be added to your NFT smart contract.

When you mint the NFTs later, the media that you added first will also be used for the first NFT. The minting follows the first in first out principle.

Instead of uploading the media files (images, videos etc.) via Token Tool you can also insert a link to your metadata that you uploaded to IPFS previously. For this you need to enable the I have a metadata link toggle:

The input field accepts two formats. One is a full web URL (using the example JSON structure from above):

A direct IPFS URI without the https part is however also sufficient:

You can also add and mint NFTs as you go. This means you can add one metadata link and then already go ahead and mint the NFT. After that you could add one more metadata link and then mint this NFT and so on. You are not required to add all metadata links for your entire collection at once.

If you have a large collection of dozens or even thousands of NFTs using the Add many option is much more efficient.

Here you can simply paste the full list of JSON URIs at once:

After you click Submit you will have to confirm this action from your wallet. Note that if you add hundreds of line items at once, the whole process is done in batches of several dozen each (the exact number depends on the used blockchain). You will need to confirm each batch from your wallet separately.

Don't forget to Confirm addition after you submitted the the list:

After you added the NFT metadata to your NFT smart contract with this method, you can either continue with managing the minter whitelist or go straight to minting if you didn't activate the whitelist requirement.

If you activated the minter whitelist at the time of NFT creation, you need to add addresses to the whitelist. You can add them one by one in the input field or upload an entire CSV file. You can also remove address from the whitelist again.

Now you (and your audience) can finally mint NFTs. Open the page that is linked to from the NFT minting page. When you scroll all the way down you will find the minting button:

As the NFT creator you can always mint NFTs (even if you activated the whitelisting). You are also not limited by the maximum amount of NFTs per address. The only limit you have as the creator is the global maximum amount of NFTs.

For NFT collections the global maximum is simply equal to the amount of media / metadata entries that you have already added to the NFT.

Other users will only be able to mint NFTs if they are on the whitelist (only if this was activated) and as long as they don't mint more that the maximum amount of NFTs per user.

Step 1: Enter the Manage NFT function

Step 2: Verify token

Step 3: Prepare your media and metadata for collection NFTs

Media files

Metadata files with NFT descriptions and attributes

Upload files and folders to IPFS

Step 4: Add media and metadata to a collection NFT

Upload media via Add one

Add media and metadata via Add many

Step 5: Manage your minter whitelist (allowlist)

Step 6: Mint NFTs via the NFT minting page

Click Save after making changes.

The Integrations section covers all payment rails, KYC/KYB providers, crypto wallet configuration, and investor custody settings.

If you accept bank transfer payments, add one or more company bank accounts here. The platform supports three account kinds, so you can collect investor wires in their local currency:

• SEPA (Europe) — IBAN + BIC, typically denominated in EUR.

• United States — ACH routing (9 digits), optional wire routing, account number, and account type (checking/savings), typically denominated in USD.

• United Kingdom — Sort code (12-34-56) + 8-digit account number, typically denominated in GBP. You may also store an IBAN/BIC on the same record so the account doubles as a SEPA fallback.

For each account you can set:

• Label — A short internal name (e.g. “Main EUR account”).

• Currency — The 3-letter ISO currency code; investor offerings denominated in this currency are routed to this account.

• Primary — Exactly one account may be marked primary. The primary account is used as a fallback when no account matches an offering’s currency.

• Bank name/address and Beneficiary address — Optional, shown to investors on the wire‐instructions screen and in confirmation/reminder emails.

1. Match the offering’s base_currency to a bank account currency (case-insensitive).

2. If no exact match exists, fall back to the primary account.

3. If no match and no primary is configured, the order is rejected at checkout.

Add at least one account to enable the Bank Transfer payment method when creating or editing offerings.

Tenants who previously had a single SEPA IBAN/BIC configured at the tenant level are automatically migrated to a primary SEPA bank account on first deploy of this feature. The legacy fields remain readable on the API for one release for backwards compatibility but are no longer editable from the UI — manage all bank accounts from this section instead.

[Checkout.com] processes credit and debit card payments (Visa, Mastercard) for your offerings. Configure:

• Secret Key (sk_…) — Your secret API key. Found under Settings → Keys in the Checkout.com Dashboard.

• Public Key (pk_…) — Used to initialize the card payment widget on the investor checkout page. It’s safe to expose this on the frontend.

• Webhook Secret — Used to verify incoming payment notification webhooks. Found under Settings → Webhooks in the Checkout.com Dashboard.

• Processing Channel ID — Optional channel identifier for routing transactions within Checkout.com. Found under Settings → Processing Channels in your Checkout.com Dashboard.

[Coinbase Commerce] is our recommended hosted PSP for accepting crypto payments. You can choose to keep proceeds as cryptocurrency or settle to fiat manually.

• Coinbase Commerce API Key — Found under API keys in your Coinbase Commerce dashboard.

• Coinbase Commerce Webhook Secret — Used to verify incoming webhooks. Set this under Webhook subscriptions in the Coinbase Commerce dashboard.

• Accepted Assets — A comma-separated list of asset symbols (e.g. USDC, USDT).

• Accepted Chains — A comma-separated list of blockchain names for hosted checkout (e.g. ethereum, polygon).

• Settlement Preference — Choose keep_crypto or cashout_manual to control how Coinbase settles proceeds.

Extended public keys (xPub) allow the system to generate unique deposit addresses for each investor without exposing private keys. The Offering Manager never holds or has access to your private keys.

• EVM xPub (HD Wallet) — Export your xPub from your HD wallet (e.g., Ledger, Trezor, or any BIP-44 compatible wallet). This is used to derive unique Ethereum/EVM deposit addresses for stablecoin payments (USDC, USDT, etc.).

Once an EVM xPub is configured, the direct Stablecoin payment method becomes available when creating or editing offerings.

You can choose one or both supported providers to verify investor identity before they can invest:

Sign up at [Sumsub] and generate your credentials:

• App Token — Generated under Developers → Integration in the Sumsub dashboard.

• Secret Key — Generated alongside the App Token. Used to sign API requests and verify webhooks.

• Webhook Secret — Copy or generate this in your Sumsub Webhook settings to validate incoming notifications.

• KYC Level — Select the verification level (e.g. basic, enhanced).

• KYB Level — If you perform business verification, select the appropriate level.

Sign up at [Blockpass] and create a service:

• Client ID — Found in your Blockpass service dashboard.

• Webhook Secret — Set and copy this secret in your service’s webhook configuration.

Click Save after entering or updating any credentials.

You can require investors to bring their own wallet (BYO), let them choose, or provision a custodial wallet via a supported custody provider. Select your provider under Custody Provider, then configure credentials for Tangany or Fireblocks.

Link: Tangany

Tangany is a custodial solution for EVM-compatible chains and stablecoins.

• Custody Provider — Select Tangany to enable custodial wallets.

• Default Investor Wallet Policy — Choose one of:

  • byo_only — Investor must use their own wallet.

  • investor_choice — Investor may select BYO or custodial.

  • custodial_only — A custodial wallet is provisioned for the investor.

• Tangany Subscription — Your Tangany subscription ID.

• API Base URL — Your Tangany API base endpoint (e.g. https://api.tangany.com).

• Auth Base URL — Your Tangany authentication endpoint.

• Client ID & Client Secret — Credentials from your Tangany dashboard.

• Wallet Label Template — A naming template for custodial wallets (e.g. {{ investor.email }}).