> For the complete documentation index, see [llms.txt](https://docs.ibis.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ibis.app/reference/integrating-with-ibis.md).

# Support and integration

Send support, lender, borrower and privacy questions to <support@ibis.financial>, along with data requests and integration questions. You can also use the inquiry form on the [Ibis website](https://ibis.financial). For security reports, see [Security and disclosure](/reference/security-and-audits.md).

## Contacts

### What to include

For a question about a facility, position or transaction, name the facility, the network and, where there is one, the transaction hash. Never include a private key, seed phrase, password or one-time code.

{% hint style="warning" %}
Ibis never asks for private keys, seed phrases, passwords or one-time codes by email or message, and never starts a wallet connection by message. A message that asks for any of them does not come from Ibis.
{% endhint %}

### Official hosts

These are the official Ibis hosts while the Sepolia testnet is the documented network.

| Host                      | Purpose                                  |
| ------------------------- | ---------------------------------------- |
| ibis.financial            | Ibis website, including the inquiry form |
| docs.ibis.app             | This documentation                       |
| testnet.ibis.app          | Lender app for the Sepolia testnet       |
| testnet.borrower.ibis.app | Borrower app for the Sepolia testnet     |

### Notices

Published notices appear on [Networks and addresses](/reference/deployed-contracts-and-addresses.md).

## Standards and token scales

A facility's address is also the address of its share token. Facility shares are a token balance that standard wallet tooling displays. The underlying asset of every facility has 6 decimals, so the smallest asset unit is 0.000001 (bound).

| Quantity                              | Decimals | Class      |
| ------------------------------------- | -------- | ---------- |
| Underlying asset amount               | 6        | Bound      |
| Facility shares                       | 18       | Convention |
| Share price, in asset units per share | 18       | Convention |

Converting shares into an asset amount multiplies the shares by the share price and rounds down to the smallest asset unit. Converting an asset amount into shares divides by the share price and rounds down to the smallest share unit. The formulas are on [Shares and the share price](/platform/shares-and-the-share-price.md). The admitted assets on each network are listed on [Networks and addresses](/reference/deployed-contracts-and-addresses.md).

## Deposits and repayments

A facility credits deposits and repayments only through their respective operations. Each draws the asset from the paying wallet under either a token allowance given to that facility or a signed authorization from that wallet. Signed authorization works only if the facility's asset supports it; otherwise, the operation needs an allowance covering the amount.

Allowances apply per facility.

The facility screens every paying wallet and, for a deposit, the wallet receiving the shares. Any eligible wallet may repay; the borrower repayment wallet (Borrower ops) is the published one. See [Deposits and principal delivery](/platform/deposits-and-withheld-principal.md) for deposit admission, [Liquidity accounting](/platform/liquidity-accounting.md) for repayment and [Eligibility, compliance and agreements](/getting-started/compliance-perimeter.md) for screening.

{% hint style="danger" %}
A plain token transfer to a facility address is neither a deposit nor a repayment. It issues no shares and is not attributed to the sender.
{% endhint %}

A withdrawal is funded only when the facility holds cash to fund it, normally from borrower repayment.

## Onchain state and recorded history

The chain supplies current values, while an indexer derives historical figures from what each facility records. Indexed history can lag the chain; if the figures differ, the onchain state is authoritative. Integrators read it through their own node or RPC provider.

## Addresses

[Networks and addresses](/reference/deployed-contracts-and-addresses.md) publishes stable addresses for the facility directory, the approved-address registry, the compliance escrow and each listed facility.