# Overview

Browse the topics below or chat with the customer support to ask anything you need help with.

{% hint style="info" %}
To get in touch with the Lisk customer support, use the Lisk chatbot at the bottom left, or the contact button at the top right corner.
{% endhint %}

### Search All Help Articles

<button type="button" class="button primary" data-action="search" data-icon="magnifying-glass">Search…</button>

### Quickstart

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f680">🚀</span> Quickstart</h3></td><td align="center">Your Onboarding Journey to Lisk</td><td><a href="/quickstart">Quickstart</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="2705">✅</span> KYB</h3></td><td align="center">by Entity Type and Jurisdiction</td><td><a href="/guides/getting-started/kyb-by-entity-type-and-jurisdiction">KYB by Entity Type and Jurisdiction</a></td></tr><tr><td align="center"><h3>🌐 Countries</h3></td><td align="center">Where is Lisk available?</td><td><a href="/supported-countries">Supported Countries</a></td></tr><tr><td align="center"><h3> 💳 Payment Methods</h3></td><td align="center">Which rails are available?</td><td><a href="/supported-payment-methods">Supported Payment Methods</a></td></tr></tbody></table>

### FAQ

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h3>Early Access</h3></td><td align="center">Everything you need to know regarding Early Access on Lisk.</td><td><a href="/faq/early-access">Early Access</a></td></tr><tr><td align="center"><h3>Lisk App</h3></td><td align="center">Frequently asked questions about the Lisk App.</td><td><a href="/faq/lisk-app">Lisk App</a></td></tr><tr><td align="center"><h3>USDL</h3></td><td align="center">Frequently asked questions about the USDL stablecoin.</td><td><a href="/faq/usdl">USDL</a></td></tr><tr><td align="center"><h3>LSK Token</h3></td><td align="center">Frequently asked questions regarding the LSK Token.</td><td><a href="/faq/lsk-token">LSK Token</a></td></tr><tr><td align="center"><h3>Lisk Chain Closure</h3></td><td align="center">Everything you need to know regarding the Lisk Chain Closure.</td><td><a href="/faq/lisk-chain-closure">Lisk Chain Closure</a></td></tr><tr><td align="center"><h3>DAO Cessation</h3></td><td align="center">Everything you need to know regarding the Lisk DAO Cessation.</td><td><a href="/faq/dao-cessation">DAO Cessation</a></td></tr></tbody></table>

### Guides

<table data-view="cards"><thead><tr><th align="center"></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f331">🌱</span> Getting Started</h3></td><td><ul><li><a data-mention href="/guides/getting-started/sign-up-on-lisk">Sign Up on Lisk</a></li><li><a data-mention href="/guides/getting-started/set-up-the-lisk-mobile-app">Set Up the Lisk Mobile App</a></li><li><a data-mention href="/guides/getting-started/complete-business-verification-kyb">Complete Business Verification (KYB)</a></li></ul></td><td><a href="/guides/getting-started">Getting Started</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f3db">🏛️</span> Workspace Management</h3></td><td><ul><li><a data-mention href="/guides/workspace-management/create-an-account">Create an Account</a></li><li><a data-mention href="/guides/workspace-management/invite-members">Invite Members</a></li><li><a data-mention href="/guides/workspace-management/add-a-contact">Add a Contact</a></li></ul></td><td><a href="/guides/workspace-management">Workspace Management</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f4b8">💸</span> Transactions &#x26; Payments</h3></td><td><ul><li><a data-mention href="/guides/transactions-and-payments/deposit-funds">Deposit Funds</a></li><li><a data-mention href="/guides/transactions-and-payments/send-money">Send Money</a></li><li><a data-mention href="/guides/transactions-and-payments/transfer-funds-between-accounts">Transfer Funds between Accounts</a></li><li><a data-mention href="/guides/transactions-and-payments/withdraw-funds">Withdraw Funds</a></li></ul></td><td><a href="/guides/transactions-and-payments">Transactions and Payments</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f464">👤</span> User Settings</h3></td><td><ul><li><a data-mention href="/guides/user-settings/change-your-email-address">Change Your Email Address</a></li><li><a data-mention href="/guides/user-settings/reset-two-factor-authentication">Reset Two-Factor Authentication</a></li></ul></td><td><a href="/guides/user-settings">User Settings</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="2699">⚙️</span> Roles &#x26; Permissions</h3></td><td><ul><li><a data-mention href="/guides/roles-and-permissions/remove-a-member-from-a-workspace">Remove a Member from a Workspace</a></li><li><a data-mention href="/guides/roles-and-permissions/transfer-workspace-ownership">Transfer Workspace Ownership</a></li></ul></td><td><a href="/guides/roles-and-permissions">Roles and Permissions</a></td></tr><tr><td align="center"><h3><span data-gb-custom-inline data-tag="emoji" data-code="1f517">🔗</span> Lisk Chain</h3></td><td><ul><li><a data-mention href="/guides/lisk-chain/celo-migration">Celo Migration</a></li></ul></td><td></td></tr></tbody></table>


# Quickstart

Your Onboarding Journey to Lisk

A quick map of the 5 stages between signing up and running your business on Lisk day to day.

Each stage below shows the steps you'll take to complete it, what it unlocks, and a few things partners in early testing found useful to know. For the full click-by-click details, follow the linked guide.

```mermaid
%%{init: {"flowchart": {"htmlLabels": true, "padding": 16, "nodeSpacing": 45, "rankSpacing": 65, "wrappingWidth": 260}}}%%
flowchart LR
    A["<b>1. Welcome</b><br>Sign up + mobile + 2FA"] --> A1["✓ Workspace access<br>✓ Sign in & approve"]
    A --> B["<b>2. KYB</b><br>Verify your business"]
    B -->|Unlocks| B1["✓ Virtual bank accounts<br>✓ IBAN / ACH / SEPA<br>✓ Stablecoin transfers"]
    B --> C["<b>3. Workspace setup</b><br>Members, accounts,<br>contacts"]
    C -->|Unlocks| C1["✓ Org structure<br>✓ Clean tracking<br>✓ Multi-sig resilience"]
    C --> D["<b>4. First transfer</b><br>Send, receive,<br>or move money"]
    D -->|Unlocks| D1["✓ Live payments<br>✓ Reconciliation flow"]
    D --> E["<b>5. Ongoing use</b><br>Manage & grow"]
```

### 👋 Stage 1 → Welcome&#x20;

Guide: [Sign up on Lisk](/guides/getting-started/sign-up-on-lisk) · [How do I set up the Lisk mobile app?](/guides/getting-started/set-up-the-lisk-mobile-app)

**Steps**

1. Sign up with your email (or Google/Apple) on **web**
2. Create your workspace
3. Invite your first members (or skip for now and do that later)
4. Turn on 2FA with an authenticator app
5. Install the Lisk mobile app and sign in with the same email
6. Create your passkey (fingerprint, face scan, or device passcode)

{% hint style="info" %}
**Good to know:**

* The steps above describe signing up in the browser. You'll still need the mobile app partway through to finish setup (for example, creating your passkey) - switching over at that point is expected, not a sign something went wrong. For signing up directly on mobile, see [How do I set up the Lisk mobile app?](/guides/getting-started/set-up-the-lisk-mobile-app).
* Creating your workspace and inviting your first members both happen here in Stage 1. The fuller setup comes later, in **Stage 3** - and you don't have to wait for verification to start it: departments, categories, contacts, and crypto withdrawal methods can all be done while KYB is under review.
  {% endhint %}

### 🛂 Stage 2 → Verify your business (KYB)&#x20;

Guide: [How do I verify my business (KYB)?](/guides/getting-started/complete-business-verification-kyb)

**Steps**

1. Gather your company, ownership, and identity documents
2. Open **Verification** from the "Verify now" text box at the top of the website, or go to **Settings → Verification**
3. Enter your business details and business activity
4. Add owners, directors, and their identity documents
5. Upload your company documents
6. Review the summary and submit
7. Respond to any follow-up requests from reviewers

{% hint style="info" %}
**Good to know:**

* Gather every document up front and submit in one sitting - this is the single biggest time-saver.
* Keep your legal company name written identically across every document (incorporation, ownership, bank, address) - mismatches are the most common cause of delays.
* On a slower connection, submitting a large batch of documents can take a little longer than expected. If you see a message that it's taking longer than usual, give it a moment before trying again rather than resubmitting immediately.
* You don't have to wait idle while your review is underway. Jump ahead to **Stage 3** and get the groundwork done - invite members, assign roles, set up departments, categories, and contacts - so everything's ready the moment verification comes through.
  {% endhint %}

### ⚙️ Stage 3 → Set up your workspace&#x20;

Guides: [How do I invite members to my workspace?](/guides/workspace-management/invite-members) · [How do I create an account in my workspace?](/guides/workspace-management/create-an-account) · [How do I add a contact?](/guides/workspace-management/add-a-contact)

**Steps you can take right away (even while KYB is under review)**

1. Invite your team members and assign roles (Admin or Member)
2. Set up departments to mirror your org (e.g. Marketing, Operations)
3. Set up categories for expense tracking
4. Add key contacts (vendors, suppliers)
5. Add your crypto withdrawal methods

**Steps that need KYB verification first**

1. Configure your bank withdrawal methods
2. Create an account per department or use case, and set its approvers

{% hint style="info" %}
**Good to know:**

* Where you can, set up more than one approver per account - it avoids a single person becoming a bottleneck or single point of failure.
* Roles matter: **Admins** manage the whole workspace (all accounts, members, audit log); **Members** only see the accounts they're added to and payments awaiting their approval. Decide who needs which role before inviting, and check each person's role after they join.
* Promoting someone to Admin (or any role change) is itself an approval - it gets signed on mobile just like a payment.
* Give each account a clear, specific name (e.g. "Marketing Budget" rather than relying on a department tag alone) so accounts stay easy to tell apart as you add more.
  {% endhint %}

### 💸 Stage 4 → Make your first transfer&#x20;

Guides: [How do I add money to my workspace?](/guides/transactions-and-payments/deposit-funds) · [How do I send money?](/guides/transactions-and-payments/send-money) · [How do I move money between my own accounts?](/guides/transactions-and-payments/transfer-funds-between-accounts)

**Steps**

1. **Start by adding money to your workspace (a deposit);** see [How do I add money to my workspace?](/guides/transactions-and-payments/deposit-funds)
2. Once funded, pick your next workflow: paying someone or moving money between your own accounts
3. Add the recipient in Contacts if you haven't already (bank details or wallet address)
4. Initiate the transfer, attaching an invoice if you want it reconciled
5. Sign the transaction on your phone — if the account has more than one approver configured, the transfer needs enough signatures to meet that account's approval quorum before it goes through

{% hint style="info" %}
**Good to know:**

* Crypto transfers currently run on the Base network only, with USDC and USDT supported - the app flags this on deposit and send screens.
* If you deposit USDC or USDT, it's credited to your balance as USDL (displayed as USD in the app) - that conversion is expected, not an error.
* Your balance updates automatically on web. On mobile, pull down to refresh if a new transaction doesn't appear right away.
* Any payment started on web still needs to be signed on your phone before it goes through - that applies even if you're the only approver.
  {% endhint %}

### 🔁 Stage 5 → Ongoing use&#x20;

Once Stages 1-4 are done, there's no more setup left - this is simply what using Lisk day-to-day looks like:

* **Move money as needed**: make further internal transfers between your own accounts, or send external payments to new contacts
* **Stay on top of activity**: monitor transactions, approvals, and the audit log
* **Approve on the go**: sign approvals as they come in on mobile
* **Keep your workspace current**: add new contacts as relationships grow, and adjust accounts or approvers as your team evolves

{% hint style="info" %}
**Good to know:**

**Transaction statuses**

* **Pending** - still waiting for enough approvals
* **Processing** - approved, settlement under way
* **Completed** - settled
* **Declined** - an approver rejected it
* **Failed** - something went wrong (e.g. an invalid address)
* **Refunded / Canceled** - money returned or the transaction was called off

**Staying organized**

* Use the transaction type filter (incoming/outgoing) to quickly separate what's coming in from what's going out.
* Admins see every transaction across the workspace; Members only see their own and what's awaiting their approval.
* Every action in the workspace - approvals, role changes, account edits - is recorded in the audit log under **Settings**, so you always have a full trail.
  {% endhint %}


# Supported Countries

Where is Lisk available?

Lisk supports businesses registered in over 100 jurisdictions.

### Where the full Lisk experience is available

* Cayman Islands
* British Virgin Islands
* United States of America
* Switzerland
* Singapore
* United Arab Emirates

Businesses registered in the above countries get the full experience today: stablecoin deposits and withdrawals, and payment rails in SEPA (EUR) and ACH/wire (USD).

In the United States, businesses whose primary operating address is in New York are currently not supported.

### Countries we also support

Beyond our initial focus markets, Lisk also supports eligible businesses registered in the countries below.

{% hint style="info" %}
Eligibility depends on where your workspace is registered, meaning where the business behind it is incorporated:

* **Workspaces registered outside the EEA:** supported, if the country is listed on this page.
* **Workspaces registered in the EEA:** not supported yet.
* **Team members located in the EEA:** can join and use workspaces registered outside the EEA.

The European Economic Area (EEA) covers the EU member states plus Iceland, Liechtenstein, and Norway.
{% endhint %}

Every listed country outside the EEA supports stablecoin deposits and withdrawals. Payment rails are shown per country: EUR runs over SEPA and USD over ACH/wire.

| Country                                      | Payment rails  |
| -------------------------------------------- | -------------- |
| Albania                                      | SEPA, ACH/wire |
| American Samoa                               | SEPA, ACH/wire |
| Andorra                                      | SEPA, ACH/wire |
| Angola                                       | SEPA, ACH/wire |
| Anguilla                                     | SEPA, ACH/wire |
| Antarctica                                   | SEPA, ACH/wire |
| Antigua and Barbuda                          | SEPA, ACH/wire |
| Argentina                                    | SEPA, ACH/wire |
| Armenia                                      | SEPA, ACH/wire |
| Aruba                                        | SEPA, ACH/wire |
| Australia                                    | SEPA, ACH/wire |
| Austria                                      | Available soon |
| Azerbaijan                                   | SEPA, ACH/wire |
| Bahamas                                      | SEPA, ACH/wire |
| Bahrain                                      | SEPA, ACH/wire |
| Bangladesh                                   | SEPA           |
| Barbados                                     | SEPA, ACH/wire |
| Belgium                                      | Available soon |
| Belize                                       | SEPA, ACH/wire |
| Benin                                        | SEPA, ACH/wire |
| Bermuda                                      | SEPA, ACH/wire |
| Bhutan                                       | SEPA           |
| Bolivia                                      | SEPA, ACH/wire |
| Bonaire, Sint Eustatius and Saba             | SEPA, ACH/wire |
| Bosnia-Herzegovina                           | SEPA, ACH/wire |
| Botswana                                     | SEPA, ACH/wire |
| Bouvet Island                                | SEPA, ACH/wire |
| Brazil                                       | SEPA, ACH/wire |
| British Indian Ocean Territory               | SEPA, ACH/wire |
| British Virgin Islands                       | SEPA, ACH/wire |
| Brunei                                       | SEPA, ACH/wire |
| Bulgaria                                     | Available soon |
| Burkina Faso                                 | SEPA, ACH/wire |
| Cabo Verde                                   | SEPA, ACH/wire |
| Cambodia                                     | SEPA, ACH/wire |
| Cameroon                                     | SEPA, ACH/wire |
| Canada                                       | SEPA, ACH/wire |
| Cayman Islands                               | SEPA, ACH/wire |
| Central African Republic                     | ACH/wire       |
| Chad                                         | SEPA, ACH/wire |
| Chile                                        | SEPA, ACH/wire |
| Christmas Island                             | SEPA, ACH/wire |
| Cocos (Keeling) Islands                      | SEPA, ACH/wire |
| Colombia                                     | SEPA, ACH/wire |
| Comoros                                      | SEPA, ACH/wire |
| Cook Islands                                 | SEPA, ACH/wire |
| Costa Rica                                   | SEPA, ACH/wire |
| Croatia                                      | Available soon |
| Curaçao                                      | SEPA, ACH/wire |
| Cyprus                                       | Available soon |
| Czechia                                      | Available soon |
| Denmark                                      | Available soon |
| Djibouti                                     | SEPA, ACH/wire |
| Dominica                                     | SEPA, ACH/wire |
| Dominican Republic                           | SEPA, ACH/wire |
| Ecuador                                      | SEPA, ACH/wire |
| Egypt                                        | SEPA, ACH/wire |
| El Salvador                                  | SEPA, ACH/wire |
| Equatorial Guinea                            | SEPA, ACH/wire |
| Eritrea                                      | ACH/wire       |
| Estonia                                      | Available soon |
| Eswatini                                     | SEPA, ACH/wire |
| Ethiopia                                     | SEPA, ACH/wire |
| Falkland Islands (Malvinas)                  | SEPA, ACH/wire |
| Faroe Islands                                | SEPA, ACH/wire |
| Fiji                                         | SEPA, ACH/wire |
| Finland                                      | Available soon |
| France                                       | Available soon |
| French Polynesia                             | SEPA, ACH/wire |
| French Southern Territories                  | SEPA, ACH/wire |
| Gabon                                        | SEPA, ACH/wire |
| Gambia                                       | SEPA, ACH/wire |
| Georgia                                      | SEPA, ACH/wire |
| Germany                                      | Available soon |
| Ghana                                        | SEPA, ACH/wire |
| Gibraltar                                    | SEPA, ACH/wire |
| Greece                                       | Available soon |
| Greenland                                    | SEPA, ACH/wire |
| Grenada                                      | SEPA, ACH/wire |
| Guam                                         | SEPA, ACH/wire |
| Guatemala                                    | SEPA, ACH/wire |
| Guernsey                                     | SEPA, ACH/wire |
| Guinea                                       | SEPA, ACH/wire |
| Guyana                                       | SEPA, ACH/wire |
| Haiti                                        | SEPA           |
| Heard Island and McDonald Islands            | SEPA, ACH/wire |
| Honduras                                     | SEPA, ACH/wire |
| Hong Kong                                    | SEPA, ACH/wire |
| Hungary                                      | Available soon |
| Iceland                                      | Available soon |
| India                                        | SEPA, ACH/wire |
| Indonesia                                    | SEPA, ACH/wire |
| Ireland                                      | Available soon |
| Isle of Man                                  | SEPA, ACH/wire |
| Israel                                       | SEPA, ACH/wire |
| Italy                                        | Available soon |
| Jamaica                                      | SEPA, ACH/wire |
| Jersey                                       | SEPA, ACH/wire |
| Jordan                                       | SEPA, ACH/wire |
| Kazakhstan                                   | SEPA, ACH/wire |
| Kenya                                        | SEPA           |
| Kiribati                                     | SEPA, ACH/wire |
| Kosovo                                       | SEPA           |
| Kuwait                                       | SEPA, ACH/wire |
| Kyrgyzstan                                   | SEPA, ACH/wire |
| Laos                                         | SEPA, ACH/wire |
| Latvia                                       | Available soon |
| Lesotho                                      | SEPA, ACH/wire |
| Liechtenstein                                | Available soon |
| Lithuania                                    | Available soon |
| Luxembourg                                   | Available soon |
| Macao                                        | SEPA, ACH/wire |
| Madagascar                                   | SEPA, ACH/wire |
| Malawi                                       | SEPA, ACH/wire |
| Malaysia                                     | SEPA, ACH/wire |
| Maldives                                     | SEPA, ACH/wire |
| Mali                                         | ACH/wire       |
| Malta                                        | Available soon |
| Marshall Islands                             | SEPA, ACH/wire |
| Mauritania                                   | SEPA, ACH/wire |
| Mauritius                                    | SEPA, ACH/wire |
| Mexico                                       | SEPA, ACH/wire |
| Micronesia, Federated States of              | SEPA, ACH/wire |
| Moldova                                      | SEPA, ACH/wire |
| Monaco                                       | SEPA, ACH/wire |
| Mongolia                                     | SEPA, ACH/wire |
| Montenegro                                   | SEPA, ACH/wire |
| Montserrat                                   | SEPA, ACH/wire |
| Morocco                                      | SEPA           |
| Mozambique                                   | SEPA           |
| Namibia                                      | SEPA, ACH/wire |
| Nauru                                        | SEPA, ACH/wire |
| Nepal                                        | SEPA           |
| Netherlands                                  | Available soon |
| New Caledonia                                | SEPA, ACH/wire |
| New Zealand                                  | SEPA, ACH/wire |
| Nicaragua                                    | SEPA, ACH/wire |
| Niger                                        | SEPA           |
| Nigeria                                      | SEPA, ACH/wire |
| Niue                                         | SEPA, ACH/wire |
| Norfolk Island                               | SEPA, ACH/wire |
| North Macedonia                              | SEPA, ACH/wire |
| Northern Mariana Islands                     | SEPA, ACH/wire |
| Norway                                       | Available soon |
| Oman                                         | SEPA, ACH/wire |
| Pakistan                                     | SEPA           |
| Palau                                        | SEPA, ACH/wire |
| Panama                                       | SEPA, ACH/wire |
| Papua New Guinea                             | SEPA, ACH/wire |
| Paraguay                                     | SEPA, ACH/wire |
| Peru                                         | SEPA, ACH/wire |
| Philippines                                  | SEPA, ACH/wire |
| Pitcairn                                     | SEPA, ACH/wire |
| Poland                                       | Available soon |
| Portugal                                     | Available soon |
| Puerto Rico                                  | SEPA, ACH/wire |
| Qatar                                        | SEPA           |
| Republic of the Congo                        | SEPA, ACH/wire |
| Romania                                      | Available soon |
| Rwanda                                       | SEPA, ACH/wire |
| Saint Barthélemy                             | SEPA, ACH/wire |
| Saint Helena, Ascension and Tristan da Cunha | SEPA, ACH/wire |
| Saint Kitts and Nevis                        | SEPA, ACH/wire |
| Saint Lucia                                  | SEPA, ACH/wire |
| Saint Pierre and Miquelon                    | SEPA, ACH/wire |
| Saint Vincent and the Grenadines             | SEPA, ACH/wire |
| Samoa                                        | SEPA, ACH/wire |
| San Marino                                   | SEPA, ACH/wire |
| Sao Tome and Principe                        | SEPA, ACH/wire |
| Saudi Arabia                                 | SEPA, ACH/wire |
| Senegal                                      | SEPA, ACH/wire |
| Serbia                                       | SEPA, ACH/wire |
| Seychelles                                   | SEPA, ACH/wire |
| Sierra Leone                                 | SEPA, ACH/wire |
| Singapore                                    | SEPA, ACH/wire |
| Sint Maarten (Dutch part)                    | SEPA, ACH/wire |
| Slovakia                                     | Available soon |
| Slovenia                                     | Available soon |
| Solomon Islands                              | SEPA, ACH/wire |
| South Africa                                 | SEPA, ACH/wire |
| South Georgia and the South Sandwich Islands | SEPA, ACH/wire |
| South Korea                                  | SEPA, ACH/wire |
| Spain                                        | Available soon |
| Sri Lanka                                    | SEPA, ACH/wire |
| Suriname                                     | SEPA, ACH/wire |
| Svalbard and Jan Mayen                       | SEPA, ACH/wire |
| Sweden                                       | Available soon |
| Switzerland                                  | SEPA, ACH/wire |
| Taiwan                                       | SEPA, ACH/wire |
| Tajikistan                                   | SEPA, ACH/wire |
| Tanzania                                     | SEPA, ACH/wire |
| Thailand                                     | SEPA, ACH/wire |
| Timor-Leste                                  | SEPA, ACH/wire |
| Togo                                         | SEPA, ACH/wire |
| Tokelau                                      | SEPA, ACH/wire |
| Tonga                                        | SEPA, ACH/wire |
| Trinidad & Tobago                            | SEPA, ACH/wire |
| Turkey                                       | SEPA, ACH/wire |
| Turkmenistan                                 | SEPA, ACH/wire |
| Turks and Caicos Islands                     | SEPA, ACH/wire |
| Tuvalu                                       | SEPA, ACH/wire |
| U.S. Virgin Islands                          | SEPA, ACH/wire |
| Uganda                                       | SEPA, ACH/wire |
| Ukraine                                      | SEPA, ACH/wire |
| United Arab Emirates                         | SEPA, ACH/wire |
| United States Minor Outlying Islands         | SEPA, ACH/wire |
| United States of America                     | SEPA, ACH/wire |
| Uruguay                                      | SEPA, ACH/wire |
| Uzbekistan                                   | SEPA, ACH/wire |
| Vanuatu                                      | SEPA, ACH/wire |
| Vatican City                                 | SEPA, ACH/wire |
| Vietnam                                      | SEPA, ACH/wire |
| Wallis and Futuna                            | SEPA, ACH/wire |
| Western Sahara                               | SEPA, ACH/wire |
| Zambia                                       | SEPA, ACH/wire |

Countries not listed above are not supported today. Supported countries and rails can change over time as regulations and partner coverage evolve.

### Where Lisk is not available

Due to legal, regulatory, and compliance requirements, Lisk cannot serve businesses located or registered in the following places:

Afghanistan, Algeria, Belarus, Burundi, China, Cuba, the Democratic Republic of the Congo, the Gaza Strip, Guinea-Bissau, Iran, Iraq, Japan, Lebanon, Libya, Myanmar, North Korea, Russia, Somalia, South Sudan, Sudan, Syria, Tunisia, the occupied Ukrainian territories (Crimea, Sevastopol, Donetsk, Kherson, Luhansk, Zaporizhzhia), Venezuela, the West Bank, and Yemen.

In the United States, businesses whose primary operating address is in New York are currently not supported.

For the supported jurisdictions listed above, final eligibility is confirmed during onboarding.

### How do I know if my country is supported?

[Request Early Access](https://lisk.com/early-access) and tell us where your business is registered. We will come back to you within a few business days with a clear answer for your setup, before you commit to anything.

### My entities are in different countries. Which one counts?

Lisk is built for businesses operating across multiple entities and jurisdictions, so this situation is the normal case, not the exception. Each entity you onboard is assessed separately, based primarily on its country of registration. Other factors, including its operating address, may also affect eligibility. Tell us about your structure during onboarding and we will guide you through the process.

### Does every rail work in every country?

No. Lisk currently supports EUR payments through SEPA and USD payments through ACH and wire. Availability by jurisdiction is indicated in the table above. Eligibility depends primarily on where your business is registered and is confirmed during onboarding. Additional location-based restrictions may apply.

### What if my country is not supported?

Supported jurisdictions and additional regional payment rails will expand over time. If your country is not supported today, you can still reach out through the [Early Access request](https://lisk.com/early-access) and tell us where you are incorporated. It helps us understand where we can best serve.

### Related articles

* [What is USDL?](/faq/usdl)
* [Which networks, stablecoins, and payment rails does Lisk support?](/supported-payment-methods)

Not sure whether your setup qualifies? [Request Early Access](https://lisk.com/early-access) and tell us about your business.

<br>


# Supported Payment Methods

Which networks, stablecoins, and payment rails does Lisk support?

Lisk gives you one place for your money across bank and stablecoin rails. A bank transfer and a stablecoin deposit land in the same account, as one balance. This page lists what you can deposit and send today.

### Stablecoin deposits

| Asset | Network | Status    |
| ----- | ------- | --------- |
| USDC  | Base    | Supported |

Support for more networks and tokens is planned.

### Bank transfers in

Your account includes virtual accounts with real account details. Share them with a client or counterparty like any bank details, and their transfer lands in your balance.

| Method                | Currency | Status    |
| --------------------- | -------- | --------- |
| SEPA and SEPA Instant | EUR      | Supported |
| Wire                  | USD      | Supported |
| ACH                   | USD      | Supported |

### Payments out

You can pay out to any external bank account. Fees are shown before you confirm, and every payment follows the approval policy you set.

| Type                             | Status    |
| -------------------------------- | --------- |
| Bank payout in EUR (SEPA)        | Supported |
| Bank payout in USD (ACH or wire) | Supported |
| Stablecoin send (USDC on Base)   | Supported |

### When are more networks and rails coming?

Supported networks and rails will improve over time. If a rail you need is not listed, tell us during onboarding or contact support. Rails are enabled once your business completes verification during onboarding.

### Related articles

* [What is USDL?](/faq/usdl)
* [Where is Lisk available?](/supported-countries)

Still have questions? [Contact our support team](https://lisk.com/contact/).

<br>


# FAQ

Frequently asked questions about Lisk.


# Early Access

Everything you need to know regarding Early Access on Lisk.

### Getting started

#### How do I request early access?

You can request early access through this [link](https://lisk.com/early-access/) and a member of our team will be in touch within a few business days.

#### What does "early access" actually mean?

Early access lets you use Lisk before it opens more widely. You'll be part of a small, invite-only group, and all it takes to request access is your email.

What comes with being early:

* No subscription fees. During early access you only pay standard transaction fees. Subscription plans come later, and early access users will hear about pricing first.
* The team, close by. Being in a small first group means even more hands-on time as you get set up and running.
* What you share shapes where Lisk goes next. Notice a problem Lisk could solve, or somewhere it could do more? Share it during early access and it can directly inform what we prioritize and build.

#### What can I actually do on the platform today?

On day one, Lisk gives you one place to hold and move money across bank and stablecoin rails:

* One balance, automatically managed. Everything you receive lands in your main account as a single balance, so fiat and stablecoins don't live in two different places.
* Receive bank transfers into virtual accounts with real account details you can share with counterparties, settled into your balance as stablecoins.
* Pay out to any external bank account through bank rails, with fees shown before you confirm, and every payment routed through your account's approval policy.
* Controls underneath it all: admin and member roles, approval workflows, and a full activity history.

More is in the pipeline, and early access users will experience new features first.

#### Is there a cost to join early access?

There's no fee to join early access.

#### What will Lisk cost after early access?

During Early Access there are no subscription fees. Standard transaction fees apply as usual. After Early Access, pricing moves to seat-based subscription plans, with zero onboarding fees. We'll share full pricing details well before subscription fees apply, and Early Access users will hear it first.

#### Where is Lisk available?

Lisk is available in over 100 jurisdictions through our regulated partners.

### Who it's for

#### Who is Lisk built for?

Businesses operating at the intersection of crypto and fiat. If your finance team works across multiple currencies, regions, and entities, this was made with you in mind.

#### My company only has one entity. Can I still use it?

Yes. Operating across many entities is where Lisk shines, but a single-entity business is welcome and fully supported.

#### We operate 100% in crypto. Is this for us?

Absolutely. Lisk bridges crypto and fiat, so you can run entirely in crypto today and tap into fiat rails whenever you need them.

### Onboarding & verification

#### What can I expect from the onboarding process?

Onboarding starts with KYB, which verifies your business and unlocks the full product. We ask for everything upfront rather than drip-feeding requests, so you're not stuck in weeks of back-and-forth.

#### Can I use Lisk without completing KYB?

Not today. Completing KYB is what activates your account, including crypto deposits, virtual fiat accounts, bank rails, and payouts. We've designed the process to be as fast as possible.

#### What is KYB and why is it required?

KYB (Know Your Business) is the business equivalent of KYC (Know Your Customer). It verifies your company so we can safely enable fiat functionality and meet our compliance obligations.

#### I am an individual without a company. Can I use Lisk?

Lisk is built for businesses, and getting set up involves verifying a company (KYB), so we're not able to support individual accounts today. If you're planning to incorporate or already run a business, we'd love to hear from you.

#### How long does onboarding take?

It varies depending on your setup, the functionality you need, and verification.

#### Will I have support during onboarding?

Yes, you’ll receive direct, hands-on support as you get set up. Reach out and we'll work with you through the process.

### Moving money

#### Do I need to migrate funds to get started?

No. Lisk doesn't require you to move your treasury over on day one. You can start by routing a single flow — one entity's inbound payments, one recurring payout — and expand from there.

### Custody & security

#### Is my money and crypto safe? Who actually holds it?

Lisk never holds your money. Crypto in your account is self-custodied meaning the funds are yours, onchain, and Lisk cannot access or move them. Fiat services, including virtual bank accounts and payouts, are provided by [Bridge](https://www.bridge.xyz/), a Stripe company, and other regulated financial services providers. On top of that are the controls you set: roles, approval policies, and a full activity history.

#### Who can move money in my workspace?

Only the people you authorize. Deposits are admin-only. Withdrawals and payments are limited to admins and members you’ve explicitly authorized, and every outgoing payment runs through the approval policy set for the account it comes from. Sensitive details like account wallet addresses are visible to admins only, and every action lands in the audit log with a name attached.

#### Who is Bridge?

[Bridge](https://www.bridge.xyz/), a Stripe company, is our financial infrastructure partner. Within Lisk, Bridge powers our stablecoin orchestration and payment flows, including the banking rails for virtual fiat accounts and payouts

#### Is Lisk a bank? Is my money insured?

Lisk is a financial technology company, not a bank. Your account runs on [Bridge](https://www.bridge.xyz/), a Stripe company, and its regulated financial partners. Balances on Lisk are not bank deposits, so deposit insurance like FDIC protection does not apply. Instead, funds on Lisk sit as stablecoins in your own wallet, held by you and no one else, not even Lisk. While money is moving on bank rails, such as an incoming transfer or an outgoing payout, it is handled by Bridge under the [Bridge User Terms](https://www.bridge.xyz/legal/overview).

#### What happens to my funds if Lisk or a partner shuts down?

Your funds are protected by design, not by trust in any single company. Balances on Lisk are held as stablecoins in your own wallet, which Lisk never controls, so they stay yours and you can withdraw them to an external wallet at any time. Fiat only enters the picture while a payment is in motion, such as an incoming bank transfer or an outgoing payout. Money in transit moves through [Bridge](https://www.bridge.xyz/), a regulated financial provider, under the conditions set out in [Bridge's terms](https://www.bridge.xyz/legal/overview).

#### Can my workspace be frozen or closed?

Only in limited situations, such as activity that breaches our terms or those of our partners, or where we're legally required to act. Even then, it applies to your workspace, not your funds. Balances on Lisk are held as stablecoins in your own wallet, which Lisk never controls, so you can withdraw them to an external wallet at any time. Money in transit on fiat rails, such as an incoming bank transfer or an outgoing payout, moves through Bridge, a regulated financial provider, under its terms. You can read the full conditions in [our terms](https://lisk.com/legal/terms/) and [Bridge's terms](https://www.bridge.xyz/legal/overview).

#### Who controls the keys? Is this self-custody?

For crypto, yes. Your Lisk wallet is non-custodial, Lisk never holds the keys, and you can withdraw to an external wallet at any time. Funds you move onto fiat rails work differently: virtual accounts and bank payouts run through [Bridge](https://www.bridge.xyz/), a regulated financial provider, and money on those rails is governed by [Bridge's terms](https://www.bridge.xyz/legal/overview) rather than held in your wallet.

### Working with us

#### What do I do if I have questions before signing up?

Reach out through the [early access request](https://lisk.com/early-access/). We'll get back to you within a few business days.

<br>


# Lisk App

Frequently asked questions about the Lisk App.

### What do I need to start using Lisk?

Lisk is a workspace-based platform for teams and businesses to manage funds, make payments, and manage approvals together. To get started you need a few things:

* **A business or organization.** Lisk is for businesses, not individuals - setting up requires verifying a company through **KYB (Know Your Business)**. A single-person or single-entity business is fine; you just can't sign up as an individual.
* **An authenticator app.** During sign-up you set up two-factor authentication (2FA) using a TOTP authenticator app (for example, one that generates a rotating 6-digit code).
* **The Lisk mobile app.** You approve and sign transactions on your phone. The web app is for viewing data and starting transactions; signing always happens on mobile, using your device's security (Face ID, fingerprint, or passcode). Your device needs to support passkeys.

#### What is KYB, and when do I need it? <a href="#what-is-kyb-and-when-do-i-need-it" id="what-is-kyb-and-when-do-i-need-it"></a>

KYB (Know Your Business) is the check that confirms your organization's identity. You complete it as a multi-step form covering your business details, activity, beneficial owners and directors, and company documents (such as articles of incorporation and proof of address). Any deposits and withdrawals stay locked until your KYB is approved. Some documents, such as financial statements and proof of address, must be dated within the last 90 days.

### How long does it take to get set up on Lisk?

Setting up your Lisk user account itself is quick - usually a few minutes. Sign-up walks you through a short sequence: verify your email, enter your name, create your workspace, invite your team, and set up two-factor authentication. You'll also pair the mobile app and create your signing passkey so you can approve payments.

Any deposits and transactions require **business verification (KYB)**. This is the part that can take longer, especially if extra documents are requested during review. You can keep exploring and setting up your workspace while KYB is under review.

### Is Lisk free to use?

Setting up and running your Lisk workspace doesn't cost anything on its own. Creating a workspace, adding accounts, inviting your team, and completing verification are all part of getting started at no charge.

When a fee applies to an outgoing payment - for example when a payout is converted to a local currency and sent to a bank account - Lisk shows you the fee before you confirm, so there are no surprises.

For the full picture of when fees apply and what they cover, see [#what-fees-does-lisk-charge](#what-fees-does-lisk-charge "mention")

### What fees does Lisk charge?

During early access, Lisk does not charge a platform fee for using the Lisk app and its services (including on/off ramping).

Certain outgoing transactions may still involve third-party costs, such as blockchain network fees, payment-rail fees or currency-conversion costs. Where applicable, the relevant fee or exchange rate will be displayed before you confirm the transaction.

Lisk may introduce or update our pricing in the future. Any applicable fees will be clearly disclosed before they take effect.

### How is Lisk different from a traditional bank?

Lisk is not a bank. It's a workspace-based financial platform that lets a team hold funds, send payments, and manage approvals together, using crypto infrastructure behind the scenes. It connects to your existing bank accounts for moving money in and out, but the funds themselves are held as a stablecoin rather than as a traditional bank balance.

Here are the main differences a new user notices:

* **Funds are held as a stablecoin, not a bank deposit.** Money in your Lisk accounts is held as USDL, a stablecoin, on the Base network. You can move it out to a bank account or a crypto wallet whenever you need to.
* **You and your team control the accounts.** Lisk accounts are multi-signature: you set how many approvers must sign off before a payment goes through. No single person can move funds on their own unless you configure it that way.
* **Roles instead of account signatories.** A workspace has an Owner, Admins, and Members, each with clearly defined permissions over accounts and transactions.
* **It works alongside your bank.** You fund accounts by bank transfer (ACH/wire or SEPA) or by crypto, and you pay out to bank accounts or crypto wallets. Lisk sits between traditional banking and crypto rails.
* **Approvals are built in.** Every payment follows an approval flow. All assigned approvers sign from the mobile app.

#### Is my money insured the way a bank deposit is? <a href="#is-my-money-insured-the-way-a-bank-deposit-is" id="is-my-money-insured-the-way-a-bank-deposit-is"></a>

No. Balances held through the platform are not traditional bank deposits and are not covered by deposit-insurance schemes such as the FDIC.

The platform uses stablecoin and payment infrastructure provided by regulated financial-services partners. Stablecoins and digital assets involve different protections and risks than funds held in a traditional bank account. Please review the applicable terms and risk disclosures for further information.

Note that all accounts on Lisk are non-custodial, so no one except the signers you assigned to an account can move the funds in them.


# USDL

Frequently asked questions about the USDL stablecoin.

### What is USDL?

USDL is the dollar stablecoin behind every balance in a Lisk account. It is issued by [Bridge](https://www.bridge.xyz/), a Stripe company and Lisk's financial infrastructure partner, and backed by USD-denominated reserves. In Lisk, it simply appears as a dollar balance.

### Why Lisk uses USDL

Lisk connects fiat deposits, stablecoin deposits, payment accounts, bank payouts, crypto payouts, and internal transfers. USDL is the internal asset that lets all of them land in one place.

Without it, you would have to think about which stablecoin you hold, which blockchain it lives on, and whether a conversion needs to happen. With it, you get one dollar balance, regardless of whether the money arrived as a bank transfer or a stablecoin.

### What you see in the product

You see dollars. Deposits, payments, withdrawals, transfers, and transaction statuses are all shown as dollar amounts. You see $500, not "500 USDL."

### What happens when money moves

When fiat or a supported stablecoin is deposited, it converts into USDL and shows up as a dollar balance. When you send a payment, USDL converts back into whatever the destination requires, fiat or other stablecoins.

### Is there a fee for conversion?

No. Lisk covers the cost of USDL conversion and network gas fees, so there is no separate charge for a conversion having happened.

Other partner or rail fees may still apply depending on the transaction type. Any that apply are shown as a fee line before you confirm.

### How long do conversions take?

Conversion is automated but not always instant, because it can involve a crypto rail or a fiat rail.&#x20;

Typical timings:

| Flow                         | Typical timing            |
| ---------------------------- | ------------------------- |
| Supported stablecoin deposit | Around 30 minutes         |
| SEPA Instant deposit         | Around 35 minutes         |
| Wire deposit                 | Around 2.5 hours          |
| ACH deposit                  | Next business day         |
| Withdrawal to fiat           | Similar timing in reverse |

Banking hours, cutoffs, weekends, holidays, and large transactions can extend these.&#x20;

### Who holds my money?

Balances on Lisk are held as stablecoins in your own wallet, which Lisk never controls. While money is moving on bank rails, such as an incoming transfer or an outgoing payout, it is handled by [Bridge](https://www.bridge.xyz/) under the [Bridge User Terms](https://www.bridge.xyz/legal/overview).&#x20;

### Related articles

* [Which networks, stablecoins, and payment rails does Lisk support?](/supported-payment-methods)
* [Where is Lisk available?](/supported-countries)

Still have questions? [Contact our support team](https://lisk.com/contact/).

<br>


# LSK Token

Frequently asked questions regarding the LSK Token.

### General

#### What is changing for the LSK token?

LSK continues, with a new role. As the Lisk Chain and the DAO wind down, LSK becomes Lisk's loyalty token. Going forward, it lives on Ethereum.&#x20;

#### Do I need to do anything with my LSK right now?

That depends on where you hold it. If your LSK is on Ethereum or on an exchange, no action is needed. If it is on the Lisk Chain, or staked, you will need to move it to Ethereum before the Chain closes on October 31, 2026. For stakers, unlocking is now penalty-free. A 3-day waiting period applies before you can unstake, and bridging to Ethereum takes around 8 days, so allow at least 11 days in total. Claim any outstanding staking rewards before the Chain shuts down. We recommend starting immediately. Step by step instructions are in the [Lisk Chain Closure](/faq/lisk-chain-closure) FAQ.

#### Where LSK lives

Which networks is LSK on? Going forward, LSK lives on Ethereum. The canonical token contract stays on Ethereum, unchanged. LSK also remains on the Lisk Chain until the Chain shuts down on October 31, 2026.

Is there a token swap, redenomination, or new contract? No. The LSK token contract is unchanged, and there is no swap. Your holdings stay the same LSK. Moving LSK off the Lisk Chain before the shutdown is a bridge transfer, not a swap.

#### Will my exchange keep listing LSK?&#x20;

Listings are being maintained. The token contract on Ethereum is unchanged, and the 100M LSK token burn is a single onchain event rather than a migration, so existing listings keep working exactly as they do today.&#x20;

#### Where can I trade LSK?

LSK trades on major exchanges including [Binance](https://www.binance.com/), [OKX](https://www.okx.com/), and [Kraken,](https://www.kraken.com/) and on decentralized exchanges on Ethereum.

### Staking

#### Can I still stake, and do I keep earning rewards? Where does staking happen?

New staking is no longer possible, but existing positions continue to earn rewards until the Chain shuts down on 31 October 2026. In the Lisk Portal, you can now only unstake your LSK or claim your rewards. To exit, unlock your position, wait 3 days, then unstake and bridge your LSK to Ethereum. Unlocking is penalty-free. Claim any outstanding staking rewards before the shutdown.

#### Has the unstaking penalty changed?

Yes. The DAO proposal passed and the staking contract has been updated, so unlocking is now penalty-free. You can unlock your position at any time, then a 3-day waiting period applies before you can unstake.

#### What do I need to do with my staked LSK before the shutdown?

Unlock it, wait 3 days, unstake it, then bridge it to Ethereum before 31 October 2026. It is not returned automatically. Claim any outstanding staking rewards too. Bridging takes around 8 days, so allow at least 11 days in total and start now. We recommend starting immediately.

### Supply and burns

#### What is happening to total supply?&#x20;

The DAO proposal has passed, and the one-time burn of 100 million LSK is now in progress. Once it completes, total supply moves from 400 million to 300 million.

#### Will more tokens be burned after this?&#x20;

No. No further burns are planned beyond the one-time 100 million burn. Once it completes, the total holds at 300 million.

### The token's role going forward

#### What is LSK's new role?

LSK becomes Lisk's loyalty token. Businesses will earn rewards for running their money operations on Lisk and for referring other businesses to it, and over time they will be able to receive those rewards in LSK and pay their in-app fees with it. As the product grows and its rewards expand, so does LSK's role.

#### Do I need LSK to use Lisk?

No. The product works on its own terms. LSK is the loyalty and rewards layer that will run alongside it, not a requirement for access.

#### If holding LSK is optional, why does it matter?

As Lisk grows, more activity flows through the product, and more of that activity can run through LSK in rewards and fees. The token's usefulness is designed to grow alongside the product.

#### When do the LSK earn-and-spend features go live?

They roll out in phases, layered on top of the product's existing features. Receiving rewards in LSK comes first, starting with referrals. Paying in-app fees in LSK follows. Points-style rewards and more will become redeemable in LSK as the product matures. The sequence is set, though specific dates follow product releases.

### The DAO

#### I hold LSK for a say in governance. What happens to that?&#x20;

The Lisk DAO winds down on the timeline set in the [DAO proposal](https://lisk.degov.ai/proposal/0xbf96e9b2362a11c31ef5dc6db9f2f4bda2caf727c18df3595e1c93d967e8334a), so onchain governance concludes with it.

#### Where do I find official updates?&#x20;

You can find all updates on official Lisk channels including our[ blog](https://lisk.com/blog/),[ X](https://x.com/Lisk?lang=en) and[ LinkedIn](https://www.linkedin.com/company/lisk/).

### Related articles

* [Lisk Chain Closure](/faq/lisk-chain-closure)

<br>

<br>


# Lisk Chain Closure

Everything you need to know regarding the Lisk Chain Closure.

{% hint style="warning" %}
**Action required**: Withdraw all assets from Lisk Chain by 31 October 2026. The Lisk Chain is shutting down. If you hold LSK, ETH, stablecoins, bridged assets, DeFi positions, or any other assets on Lisk Chain, please withdraw them as soon as possible and no later than 31 October 2026. We will never ask for your seed phrase or private keys. Use bridge.lisk.com only, and type it yourself rather than trusting a link from anyone else.
{% endhint %}

#### What is being announced?

Lisk is winding down the Lisk Chain on October 31st, 2026, following the announcement of our new product. For projects considering what comes next, we've put together a [guide](/guides/lisk-chain/celo-migration) to exploring a move to Celo. Projects remain free to redeploy wherever they choose. This FAQ covers what's changing, the timeline, and the options available to projects, partners, and users.

#### Why is this happening?

This wasn't a decision we made lightly. A lot of teams have put real time and energy into building on the Lisk Chain, and we don't take that for granted. With the announcement of our new product, we've made the strategic decision to commit fully to that direction. Winding down the Lisk Chain is a difficult but deliberate part of that, and we're committed to supporting projects through the transition with clear communication and a path to explore what comes next.

#### What does this mean for projects building on Lisk?

Projects currently building or deployed on Lisk can review their options and decide what path makes the most sense for their product, users, and team. If you're interested in exploring a path to Celo, you can complete this form to share your project, current deployment, and technical considerations with the Celo team.

#### When is the Lisk Chain shutting down?

The Lisk Chain will be shut down on October 31st, 2026. We'd encourage any project still building or deployed on the chain to review its options and, if relevant, begin exploring a path forward well ahead of that date.

#### Do I need to move my LSK before shutdown?

Only if you hold it on the Lisk Chain or have it staked. LSK on Ethereum or an exchange is unaffected and needs no action.

#### What happens to my LSK on the Lisk Chain after it shuts down?

Once the Lisk Chain shuts down on 31 October 2026, there is no way to withdraw or recover LSK left on it. If you hold LSK on the Lisk Chain, or have it staked, you must move it to Ethereum before that date. Bridging takes around 8 days. If you are staking, unlock your position first. Unlocking is now penalty-free, and a 3-day waiting period applies before you can unstake, so allow at least 11 days in total. Claim any outstanding staking rewards before the Chain shuts down. Start now rather than waiting until the final weeks.

#### How do I move LSK off the Lisk Chain?

You bridge it back to Ethereum using the Lisk Bridge at [https://bridge.lisk.com](https://bridge.lisk.com/). It is the only bridge that still works, so do not rely on any other route.\
\
The most important thing to get right is that you are bridging LSK to LSK, not swapping LSK for ETH. The bridge opens with Ethereum and ETH preselected, so you need to change both rows before you enter an amount.

1. Open [https://bridge.lisk.com](https://bridge.lisk.com/) and connect your wallet.
2. Click the top row (the "from" side). Select the Lisk network, then select LSK as the token.
3. Click the bottom row (the "to" side). Select the Ethereum network, then select LSK as the token.
4. Check that the screen now reads Lisk LSK on top and Ethereum LSK below. Enter the amount and confirm the withdrawal.
5. About an hour later, return to the bridge and submit the "prove" transaction on Ethereum. The 7-day countdown starts at this step, not the first one, so do not skip it.
6. After the 7-day challenge period, submit the final transaction to claim your LSK on Ethereum.

You will need a small amount of ETH on Ethereum to pay for the prove and claim transactions. The whole process takes around 8 days, so we recommend starting immediately.

#### How do I unstake my LSK?

1. Go to the [Lisk Portal ](https://portal.lisk.com/staking/unstake)(portal.lisk.com/staking/unstake) and connect your wallet.
2. Unlock your position. There is no penalty.
3. Wait 3 days, then unstake. Your LSK returns to your wallet on the Lisk Chain.
4. Claim any outstanding staking rewards.
5. Bridge your LSK to Ethereum using the steps above.

Allow at least 11 days in total, and start as soon as possible.

#### How do I move WETH off the Lisk Chain?

WETH itself can’t be bridged back to Ethereum through the native Lisk bridge. The way to move it is to first unwrap the WETH into native ETH on Lisk, and then bridge the ETH back to Ethereum as usual.

1. Open the WETH contract on Blockscout: <https://blockscout.lisk.com/address/0x4200000000000000000000000000000000000006>
2. Connect the wallet holding the WETH.
3. Go to Write Contract → withdraw.
4. Enter the amount to unwrap in wei — e.g. 1 ETH = 1000000000000000000 wei.
5. Confirm the transaction. The corresponding native ETH should then appear in the same wallet.
6. The ETH can then be bridged back to Ethereum through <https://bridge.lisk.com/>.

#### Are projects required to migrate to Celo?

No. Migration is optional. Each project should decide independently whether Celo is the right fit for its product, users, and roadmap.

#### Is every project eligible to apply for migration to Celo?

Yes. Migration is open to every Lisk ecosystem project. Any team interested in exploring a migration or redeployment can submit the interest form.

#### How can projects express interest?

Projects interested in exploring a migration or redeployment path to Celo should complete the migration interest form. The form will help Celo understand the project, current deployment, technical setup, user or liquidity considerations, and potential next steps.

#### What happens after a project submits the form?

The Celo team will get in touch to share relevant resources and work through timing, redeployment, technical requirements, and what makes sense for the project’s users.

#### What information should projects prepare?

Projects should be ready to share basic information such as:

* Project name and description
* Website and social links
* Main contact
* Current deployment status on Lisk
* Smart contract addresses, if relevant
* User, liquidity, or asset considerations
* Key technical dependencies
* Any specific questions or migration needs

#### Will Celo provide technical migration support?

The Celo team is committed to supporting projects that choose to migrate and has prepared resources to help teams get set up in the Celo ecosystem. The specific support provided will depend on each project’s technical requirements and migration approach.

#### Will there be funding or incentives for projects that migrate?

No funding or incentives should be assumed. Any potential support will be reviewed on a project-by-project basis and must be confirmed directly by the relevant team.

#### Who can projects contact with questions?

Projects should use the [migration interest form](https://docs.google.com/forms/d/e/1FAIpQLSe_hWNMi7A_6l6k8VQEprVvQ0cMc0UzvGQF6G0FWgx24Vh_Mw/viewform) as the first step.

The Celo team will then follow up with relevant resources, questions, and next steps.

<br>


# DAO Cessation

Everything you need to know regarding the Lisk DAO Cessation.

### The chain shutdown and the DAO

#### When is the Lisk Chain shutting down?

The Lisk Chain will shut down on 31 October 2026.

#### Why is the Lisk DAO being discontinued?

The Lisk DAO runs on the Lisk Chain, so closing it brings the DAO's work to a natural end.

#### How does this affect the governance infrastructure?

It winds down with the Lisk Chain. The Lisk Governance Forum and the DeGov voting integration will both be retired.

### Your staked LSK

#### What happens to my staked LSK?

You can unlock your position at any time, and unlocking is now penalty-free. The DAO proposal passed and the staking contract has been updated. We recommend starting soon, because getting your funds off the Lisk Chain takes a few steps. First you unlock your position, then after a 3-day waiting period you unstake it. Then you bridge your LSK to Ethereum, which takes around 8 days. Taken together, that means starting at least 11 days before the Chain shuts down on 31 October 2026. We recommend starting immediately. Claim any outstanding staking rewards before the shutdown too.

For the withdrawal, use the Lisk Bridge at [https://bridge.lisk.com](https://bridge.lisk.com/). It is the only bridge that still works. Make sure you bridge LSK to LSK, with Lisk on the top row and Ethereum on the bottom row, and LSK selected as the token on both. The [Lisk Chain Closure](/faq/lisk-chain-closure) FAQ walks through the process step by step. We will never ask for your seed phrase or private keys. Type bridge.lisk.com yourself rather than trusting a link from anyone else

### The DAO treasury

#### What will happen to the LSK tokens held in the Lisk DAO treasury?

With the DAO proposal passed, 100,000,000 LSK, a quarter of the total supply, has been burned, permanently reducing the supply of LSK to 300,000,000. ... The remaining balance of approximately 46,500,000 LSK has been transferred to Lisk Ltd.

### Programs and the Lisk DAO Fund

#### What is the Lisk DAO Fund?

Approved by the Lisk DAO in October 2025, the Lisk DAO Fund was a dedicated investment vehicle designed to move the DAO from grant-giving toward strategic investments that generate real upside for the LSK treasury. It launched with a 4,000,000 LSK budget, was managed by the team behind Superchain Eco, and backed teams via SAFEs and SAFTs, with proceeds intended to buy and burn LSK. In its first months, it made three investments: LovCash, Cr3dentials, and Jamit.

#### What will happen to the programs and initiatives started by the Lisk DAO?

Most of them wind down with the DAO, including the Lisk DAO seasons and the Lisk DAO Fund. The exception is liquidity. Lisk Ltd will take over the Arrakis vaults previously managed by the DAO and continue providing onchain liquidity on Ethereum, so LSK stays tradable with low price impact.

#### What is happening to the Fund?

The Lisk DAO Fund has closed ahead of its planned two-year run. As Lisk narrows fully to its new product, the DAO Fund team and Lisk jointly concluded that folding the Fund's resources and investments into Lisk's entities is the best path forward for the ecosystem, LSK holders, and the founders backed. The legal handover and closing were completed in May 2026. This is part of the broader DAO wind-down described in the announcement post.

#### What happens to the companies the Fund invested in?

LovCash, Cr3dentials, and Jamit moved to Onchain Ventures AG. They stay within the Lisk family.

#### What happens to the capital that wasn't invested?

All residual capital was returned to Lisk Ltd, minus early termination costs.

<br>


# Legacy L1 LSK

FAQ regarding LSK tokens from the Lisk L1 legacy chain that weren't claimed on Lisk L2

### I held LSK on the Lisk L1 legacy chain and never claimed it. Can I still claim it?

The claim window closed on 21 May 2026. Legacy LSK can no longer be claimed or reimbursed.<br>

### Do these FAQ apply to me?

It applies if your LSK were held at an address in one of these formats:

| Format     | Looks like                                     | Used         |
| ---------- | ---------------------------------------------- | ------------ |
| Legacy L1  | Numbers ending in L, for example 456938290123L | 2016 to 2021 |
| Updated L1 | 41 characters starting with lsk                | 2021 to 2024 |

If your LSK are at an address starting with 0x, you are on the current Ethereum standard and this article does not apply to you.

### What happened to the Lisk L1 legacy chain?

Lisk moved from its own Layer 1 blockchain to an Ethereum Layer 2 in May 2024, and LSK became an ERC-20 token on Ethereum. A snapshot of all balances was taken at block height 24,823,618 on 21 May 2024. Every holder at that height could claim the same amount of LSK on the new network, one for one.

### How long did holders have to claim?

Two years, from 21 May 2024 to 21 May 2026. The claim window and the snapshot height were announced in April 2024, ahead of the snapshot.

### Can I still claim, or be reimbursed?

No. After the migration window expired on 21 May 2026, it is not possible, without any exception, to claim LSK tokens from the Lisk L1 legacy chain or to have them reimbursed in any kind or form. This applies regardless of the amount involved or the reason the claim was missed.

### How do I check whether I claimed?

If you hold LSK today in an Ethereum wallet or on an exchange account, your tokens were migrated. Most exchanges handled this automatically for balances held with them at the time of the snapshot.

If your LSK only ever sat in Lisk Desktop or the Lisk Migration Wallet, and you never signed and submitted a claim through the Lisk Portal, the claim was not completed.

### What happened to tokens that were never claimed?

Unclaimed tokens were transferred to the Lisk DAO treasury at the end of the claim period, as set out in the April 2024 migration announcement.

### Can I still see my old account data?

Historical data from the Lisk L1 legacy chain remains available through the [Lisk legacy chain service](https://docs.lisk.com/lisk-l1/legacy-chain-service). It is a record only and does not enable claiming.

### My LSK is on the Lisk L2 Chain right now. Is this the same thing?

No, and this one still has a deadline. The Lisk L2 Chain is shutting down on 31 October 2026. If you hold LSK, ETH, stablecoins, bridged assets or DeFi positions on the L2, [withdraw them](https://lisk.com/blog/posts/withdraw-assets-from-lisk-chain/) as soon as possible and no later than that date.

Start at least 11 days early. If you are staking, unlock your position first. A 3-day waiting period applies before you can unstake. Bridging to Ethereum then takes around 8 days. Claim any outstanding staking rewards before the shutdown too.

### Related articles

* [Lisk Chain Closure](/faq/lisk-chain-closure)
* <https://lisk.com/blog/posts/withdraw-assets-from-lisk-chain/>

<br>


# Guides

Step-by-step guides that help you to achieve a specific goal, grouped by category.


# Getting Started

Guides for getting set up on Lisk.


# Sign Up on Lisk

How to Sign up for Lisk on the browser or the mobile app.

You can start signing up on **either the web(browser) or the mobile app** - pick whichever you have handy.

The one thing to know up front: **Lisk uses both apps by design.** The web app is where you set up and administer your workspace (including business verification), and the mobile app is where you approve transactions. So whichever device you start on, you'll switch to the other one at a certain point:

* **Start on mobile** → you finish sign-up on your phone, then go to the **web app** to verify your business (KYB) and set things up.
* **Start on web** → you set up your workspace on the web, then switch to the **mobile app** to create your signing passkey so you can approve transactions.

### Before you start

* Have the **Lisk mobile app** (App Store (iPhone) or Google Play (Android)) and an **authenticator app** (Google Authenticator, 1Password, Authy, etc.) available - you'll need both regardless of where you start.
* Make sure your phone has a screen lock (fingerprint, face scan, or passcode); your passkey relies on it.

***

### Route A - Start on the mobile app

Everything through the end of sign-up happens on your phone.

1. Open the Lisk app on your phone.
2. **Login or signup** - enter your email and tap **Continue** (or use **Sign in with Google / Apple**).
3. **Enter confirmation code** - type the 6-digit code from the email. Use **Resend** if needed (short cooldown).
4. **What's your name?** - enter your full name and tap **Continue**.
5. **Create a workspace** - name your workspace and tap **Continue**.\
   A workspace is your team's shared home in Lisk. It's where you manage accounts, payments, members, and settings for your business.
6. **Create a passkey** - tap **Continue**, then use your **fingerprint, face scan, or device passcode**. This passkey is how you'll approve transactions.
7. **Enable 2FA** - scan the QR code with your authenticator app (or copy the setup code), tap **Continue**, then on **Enter verification code** type the current 6-digit code. On **Success**, you land on the dashboard.

**➡️ Switch to the web app to finish onboarding.** Your account is ready, but your workspace starts empty and unverified. To do anything meaningful - **verify your business (KYB)** to unlock bank features, create accounts, add funds, and invite your team - open the **Lisk web app**. KYB and those setup tasks are only available on the web. See [Complete Business Verification (KYB)](/guides/getting-started/complete-business-verification-kyb).

***

### Route B - Start on the web app

Sign-up and workspace setup happen in your browser, then you pair your phone.

1. Open the Lisk app in your browser: <https://app.lisk.com>
2. **Login or signup** - enter your email and select **Continue** (or **Sign in with Google / Apple**).
3. **Enter confirmation code** - type the 6-digit code from the email (**Resend** available after a short countdown).
4. **What's your name?** - enter your full name and continue.
5. **Create a workspace** - name your workspace and continue.\
   A workspace is your team's shared home in Lisk. It's where you manage accounts, payments, members, and settings for your business.
6. **Invite your team** - add teammates by email, or skip for now (you can invite people later).
7. **Enable 2FA** - when prompted, set up two-factor authentication with your authenticator app and confirm the 6-digit code.
8. **Approve transactions on mobile** - the web app then shows a prompt: *"Your workspace is ready. To approve transactions, you'll need the Lisk mobile app."* It displays a **QR code / download link** for the app.

**➡️ Switch to the mobile app to create your signing passkey.** Install the Lisk mobile app (scan the QR code or use the download link), open it, and **sign in with the same email**. On your phone you'll **create your passkey** (with your fingerprint, face scan, or passcode) - this is what lets you approve transactions. Full steps are in [Set Up the Lisk Mobile App](/guides/getting-started/set-up-the-lisk-mobile-app).

Once your phone is paired, you're set up. Business verification (**KYB**) to unlock bank features is done back in the web app whenever you're ready - see [Complete Business Verification (KYB)](/guides/getting-started/complete-business-verification-kyb).

***

### What to expect

* **Both routes end the same way:** an account, a workspace, a signing passkey on your phone, and 2FA. The difference is only *where you start* and *which device you switch to*.
* **Future sign-ins:** after your email code, you'll also enter the 6-digit code from your authenticator app.
* **Why two apps:** the web app is for setup and administration; the mobile app is required to approve (sign) any transaction. Neither replaces the other.
* **Next step:** To make deposits or transfer any money, it is required completing **KYB** on the web app. Check the guide [Complete Business Verification (KYB)](/guides/getting-started/complete-business-verification-kyb) for more information.

### Troubleshooting

* **"My confirmation code doesn't work."** Codes expire and are single-use. Select **Resend** and use the newest email.
* **"I didn't receive the code."** Wait a moment, check spam, then select **Resend**.
* **"My device doesn't support passkeys."** Update your phone's operating system, or use a supported device, then try creating the passkey again.
* **"My 2FA code isn't accepted."** Authenticator codes refresh every 30 seconds - use the current one. Make sure your phone's clock is set automatically.

### Related

* [Set Up the Lisk Mobile App](/guides/getting-started/set-up-the-lisk-mobile-app)
* [Complete Business Verification (KYB)](/guides/getting-started/complete-business-verification-kyb)
* [Reset Two-Factor Authentication](/guides/user-settings/reset-two-factor-authentication)


# Set Up the Lisk Mobile App

How to set up the Lisk mobile app.

The Lisk mobile app is where you **approve transactions and other requests** - payments, withdrawals, transfers, and workspace changes are all signed on your phone. It's also your secure way to sign in. Setting it up takes a few minutes: you install the app, sign in, create a **passkey**, and turn on **two-factor authentication (2FA)**.

### Before you start

* You need a Lisk account. If you don't have one yet, see **How do I sign up for Lisk?** - you can start on the web or directly in the mobile app.
* Have an **authenticator app** installed on your phone (for example Google Authenticator, 1Password, or Authy). You'll use it for 2FA.
* Make sure your phone has a screen lock set up (fingerprint, face scan, or passcode) - your passkey relies on it.

### Steps

#### 1. Install and open the app

1. Install the **Lisk** app from the App Store (iPhone) or Google Play (Android).
2. Open the app. You'll land on the **Login or signup** screen.

#### 2. Sign in

1. Enter your email address and select **Continue**. (You can also choose **Sign in with Google** or **Sign in with Apple** if that's how your account was created.)
2. On the **Enter confirmation code** screen, type the 6-digit code Lisk emails you.
   * Didn't get it? Select **Resend** - it's available again after a short countdown.

If you're brand new, the app will also ask for your name and workspace first. See [Sign Up on Lisk](/guides/getting-started/sign-up-on-lisk) for those steps.

#### 3. Create a passkey

1. On the **Create a passkey** screen - "Use the security key of your device with fingerprint, passcode or face scan as a more secure sign-in method." - tap **Continue**.
2. Your phone prompts you to create the passkey with your **fingerprint, face scan, or device passcode**. This becomes your secure sign-in and the way you approve transactions.

{% hint style="info" %}
You can have one passkey per account. Make sure you save your recovery phrase; it will be needed to recover your passkey in case you replace your phone or lose access to it.
{% endhint %}

#### 4. Enable two-factor authentication (2FA)

1. On the **Enable 2FA** screen, open your authenticator app and **scan the QR code**. Prefer to type it in? Tap the setup code shown on screen to copy it, then paste it into your authenticator app.
2. Tap **Continue**.
3. On the **Enter verification code** screen, enter the current **6-digit code** from your authenticator app. When you see **Success**, setup is complete and you're taken to the dashboard.

### What to expect

* Once your passkey and 2FA are set up, your phone is ready to approve requests. When someone (including you) starts a payment or a workspace change that needs approval, you'll be able to review and sign it here.
* On future sign-ins, after your email code you'll also enter the 6-digit code from your authenticator app.
* Payments and withdrawals send you a **push notification** when your approval is needed; you can also find them on the **Home** screen under **Pending transactions**. Workspace/role changes don't push a notification - check **Home → Policy requests**.

### Troubleshooting

* **"My device doesn't support passkeys."** You'll see a message asking you to update your operating system or use a supported device. Update your phone's OS and try again.
* **"My 2FA code isn't accepted."** Authenticator codes refresh every 30 seconds - enter the current one. Make sure your phone's clock is set automatically, since a wrong time can cause codes to fail.
* **"I didn't receive the confirmation code."** Wait a moment, check your spam folder, then select **Resend**.
* **"I can't approve transactions."** Approving requires a passkey and biometrics/passcode set up on your phone. If prompted that authentication is required, follow the on-screen link to your device settings to enable Face ID, Touch ID, or a passcode.

### Related

* [Sign Up on Lisk](/guides/getting-started/sign-up-on-lisk)
* [Reset Two-Factor Authentication](/guides/user-settings/reset-two-factor-authentication)
* [Send Money](/guides/transactions-and-payments/send-money)


# Complete Business Verification (KYB)

How to verify your business (KYB)

{% hint style="info" %}
🛂 **KYB (Know Your Business)** verification is how we confirm your company is real and who stands behind it. Once you're verified, your workspace can add bank accounts, receive deposits and send money to a bank.

**What you'll do:** enter your company details, add your owners and directors, and upload a few official documents.

**How to get through it quickly:** have every document ready *before* you start. We may ask for extra documents partway through, and that's what usually adds days.
{% endhint %}

***

## Before you start

* You need permission to manage verification for your workspace. If you don't see the **Verification** option, ask a workspace admin.
* Gather the information and documents in [**What to prepare**](#what-to-prepare) below.

## What to prepare

Open each group below and gather what applies to you. Not every item is requested in every case, but having the full set ready is the best way to avoid back-and-forth later.

{% hint style="info" %}
🌍 **What we ask for can differ depending on where you're registered and what kind of entity you are.**

A Swiss foundation has no shareholder register, a UAE company owned through holding companies needs an ownership chart, a Cayman company's registered-agent address will usually be queried. The core questions are the same for everyone, but the documents that satisfy them are not.

We can't yet map out every entity type in every jurisdiction; we're building this up as we go. What we can share are concrete, real examples: [KYB by Entity Type and Jurisdiction](/guides/getting-started/kyb-by-entity-type-and-jurisdiction) covers UAE, Cayman, and Swiss entities (including foundations), with what each one was asked for, the follow-up questions (RFIs) that came up, and how long it took.

If your entity type isn't covered there, use the closest match as a guide and reach out to support if needed; we'll tell you what's needed for your case, and add it to the guide.

For a full preparation checklist by country, see the guides for the [United States](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-united-states-entities), the [Cayman Islands](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-cayman-islands-entities), and the [British Virgin Islands](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-british-virgin-islands-entities).
{% endhint %}

<details>

<summary>🏛️ Company identity and registration</summary>

* Legal business name, entity type, and incorporation date
* Country/region where the business is registered, and its registered address
* Certificate of incorporation (or equivalent formation document)
* Company registration extract, if available
* Business contact details

</details>

<details>

<summary>💼 Business details</summary>

* Industry, and a clear description of what your business does
* Expected account usage: transaction types and, if you have it, expected volume
* Primary source of funds

</details>

<details>

<summary>👥 Ownership and control</summary>

* List of ultimate beneficial owners (UBOs) and control persons
* Director / officer information and their roles
* Register of members / shareholders (and a cap table, if applicable)
* Signed organizational chart, and an ownership declaration if needed

</details>

<details>

<summary>🪪 Identity documents</summary>

* A valid photo ID (passport, national ID, or driver's license) for each owner and director
* Their tax ID, where applicable

</details>

<details>

<summary>🏢 Proof of address</summary>

* A lease agreement or utility bill in the business's name
* If your business is fully remote with no physical office, residential proof of address for an owner with 25% or more may be accepted, but only when the verification flow offers this option. See the [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide).
* A recent bank statement or invoice showing the address can also help

</details>

<details>

<summary>💰 Financial / source-of-funds evidence</summary>

* A recent company bank statement
* Any supporting document explaining where your funds come from (for example, a parent-company funding commitment)

</details>

<details>

<summary>📜 Good standing (if available)</summary>

* Certificate of good standing, a registry extract, or a recent official filing showing the company is active

</details>

{% hint style="info" %}
📎 **File requirements**

* PDF, JPG or PNG, each file **under \~5 MB;** anything larger will fail to upload
* ZIP archives aren't accepted. If a scan is too large, export or convert it to JPEG
* Documents in other languages are fine, but a bilingual or translated copy is reviewed faster
* Financial documents and proof of address must be dated **within the last 90 days**. A lease that is still in force can be older
  {% endhint %}

{% hint style="warning" %}
💡 **Use exactly the same legal company name everywhere:**

*Incorporation, ownership, bank and address documents.*

Mismatched names are the single most common cause of delays.
{% endhint %}

## KYB document templates

{% hint style="info" %}
You only need the templates relevant to your business or requested during review.
{% endhint %}

* **Business activity:** [Proof of Nature of Business](https://docs.google.com/document/d/1CK5i-fW4aklsGvfGyIIYYvxxtYgavgQSujayzPkSi2g/edit?usp=sharing), [Account Purpose and Expected Activity](https://docs.google.com/document/d/1W-qm1kJI8nmbaxscEVinHKKggeE-UO0KHyeQcKDkI8o/edit?usp=sharing), [Flow of Funds](https://docs.google.com/document/d/1lczJPb4hIqSksGV377QBV5X9P-z5Ti-IC9y8w6W06nY/edit?usp=sharing)
* **Ownership and authority:** [KYB Ownership pack](https://docs.google.com/document/d/1MwaiTNHlheZfo94d5ZW11CTBS2A0IydOwJrYhWFCzP4/edit?usp=sharing), [Declaration of No Shareholders’ Agreement](https://docs.google.com/document/d/16QTPOmVq2XZtBIOATBF49l3mBbyVNnKmwS9adgWOaTA/edit?usp=sharing), [Signed Ownership Attestation Letter](https://docs.google.com/document/d/1mk0pSCfQXrlb64XU7vDgbcwaNC166zho5VrNEIuj-zA/edit?usp=sharing), [Control Person Attestation Form](https://docs.google.com/document/d/1_filkvAQGqBULv2D3PcqHXGoH-g5YJdFe9wn0j0QlzY/edit?usp=sharing), [Directors, Officers, Trustees and Council Members Schedule](https://docs.google.com/document/d/17Afl3yDFe879l9TWPZKsCqSL5nBpLztdZ8wODA0xZGg/edit?usp=sharing), [Letter of Authority and Proof of Signatory Authority](https://docs.google.com/document/d/19IuTcp1Uybqoe_F9Y8RybXG2x40FLuGydffCwXo9o7U/edit?usp=sharing)
* **Source of funds and wealth:** [Source of Wealth Statement and Evidence Schedule](https://docs.google.com/document/d/13oQtBRlBKEYzzp-pNUbtphRBPDgYS_07kBs50kdGg2A/edit?usp=sharing), [Business Source of Funds Declaration](https://docs.google.com/document/d/1J54e4LaOkRERg4RJkv60ketTbkbyvpNt2iey0sFdgkE/edit?usp=sharing)
* **Additional requests:** [Proof of Relationship Explanation](https://docs.google.com/document/d/1pxbr2U6feAghd_a7rKti-NdtPnndHHkn4Nzcz4WkHgE/edit?usp=sharing), [High-Risk Activities and Compliance Controls Questionnaire](https://docs.google.com/document/d/1R4r8_nfgKoFN8kqrMXXVPVXn7P304o6wdC5ZhL6pW4Y/edit?usp=sharing)

## Steps

1. Open **Settings → Verification** in your workspace.
2. Answer a few questions about your business. You'll then see a checklist of the documents that apply to you.
3. Fill in the four sections in order: **Company details**, **Business activity**, **Associated persons** (owners, control persons and signers), and **Documents**.
4. Review everything and submit.

## Best practices for a smooth review

These are the things we most often have to come back to customers about. Two minutes here can save you a week:

* **One legal name everywhere.**
  * Identical on every document and in the form.
* **Matching incorporation date.**
  * What you enter should match your formation document.
* **The right formation document for your entity type.**
  * A certificate, articles, or a deed if you're a foundation.
* **Ownership evidence attached.**
  * A register, a registry extract, or a cap table.
* **An ownership structure chart if a company owns you.** Signed and dated.
* **A control person and a signer named**
  * Both need to be officers of your entity
* **Proof of address in your entity's own name**
  * Issued in the last 90 days (a lease that is still in force can be older), and not a registered-agent, PO box or virtual address.
* **Source-of-funds evidence ready**
  * Audited financials
  * a recent statement
  * or a tax return
* **Files in PDF, JPG or PNG, each under \~5 MB**

## What to expect

You can follow your status anytime in **Settings → Verification**.

* **We may come back with a request for more documents, called an RFI** — proof of address, a bank statement, or a clarification of your ownership structure, for example. This is completely normal.
* **Once you're approved**, fiat deposits and bank withdrawals become available in your workspace.

{% hint style="warning" %}
⚡ Reply to our requests the same day if you can.

**Slow replies are the number-one reason a review takes longer than it needs to.**
{% endhint %}

## Troubleshooting

* **"My country isn't eligible."**
  * Lisk can't verify businesses registered in that country yet. See [Supported Countries](/supported-countries), or contact support if you think this is a mistake.
* **"A document was rejected or wouldn't upload."**
  * Check it against **File requirements** above: PDF, JPG or PNG, under \~5 MB, no ZIP archives, and dated within the last 90 days for financial documents and proof of address (a lease that is still in force can be older).
* **"I was asked for more documents after submitting."**
  * This is normal. Upload what's requested as soon as you can to keep your review moving.
* **"My verification was declined."**
  * [Contact support](https://lisk.com/contact/) and we'll help you with the next steps.

## Related

* [KYB by Entity Type and Jurisdiction](/guides/getting-started/kyb-by-entity-type-and-jurisdiction) — document descriptions, jurisdiction-specific requirements, expected RFIs, and timelines
* [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide): address and identity evidence for the business and its people
* [Formation, Ownership and Company Records Evidence Guide](/guides/getting-started/complete-business-verification-kyb/formation-ownership-and-company-records-evidence-guide): formation, ownership and control records
* [Financial, Tax, Regulatory and Special Request for Information Evidence Guide](/guides/getting-started/complete-business-verification-kyb/financial-tax-regulatory-and-special-request-for-information-evidence-guide): source of funds, tax and other additional requests
* [Supported Countries](/supported-countries): where Lisk is available and which payment rails each country supports
* [Lisk App](/faq/lisk-app#how-long-does-it-take-to-get-set-up-on-lisk) — including how long it takes to get set up


# Proof of Address and Identity Evidence Guide

A practical guide for Lisk business customers preparing address and person-level identity evidence

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

{% hint style="warning" %}
**Important**: Follow the exact request shown in the current Lisk business verification flow or request for information. [Bridge reviews each application individually](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and may request additional or replacement evidence. A record that is generally accepted may still be rejected if it does not match the person, entity, address, period, or purpose in the request.
{% endhint %}

## **What this guide covers**

Use this guide when Lisk or Bridge asks for:

* Proof of a business operating address
* Proof of an individual's residential address, including an ultimate beneficial owner, meaning a person who directly or indirectly owns at least 25 percent in this flow, or a Control Person, meaning a director or senior executive with significant responsibility for the business
* Government photo identity document and tax-identifying information for a person
* The Lisk-specific option for a fully remote company that has no physical office, but only when that option is shown for the specific application in the onboarding flow

This is an evidence guide. It does not replace the exact in-product request and it does not turn official records into customer-created templates.

## **First rule: use genuine evidence**

Upload the original record issued by the relevant bank, utility provider, landlord, government, registry, or other authorized issuer. Do not recreate, rewrite, backdate, or imitate an [official or third-party document](https://apidocs.bridge.xyz/platform/customers/compliance/docs). A self-written declaration cannot replace a utility bill, bank statement, lease, government letter, passport, national identity document, or other requested official evidence.

If the requested document does not exist, tell Lisk Support and ask it to confirm with Bridge which alternative is acceptable. Do not create a substitute official record. Bridge, not Lisk Support, decides whether the alternative satisfies its verification requirement.

## **Business address evidence**

Official reference: [Bridge proof-of-address requirements](https://apidocs.bridge.xyz/platform/customers/compliance/poa)

### **When Bridge may request it**

Proof of business address is not required in every case. Bridge may request it when location signals conflict, such as when the stated operating address, registered jurisdiction, or Control Person location do not align, or when additional verification is needed. It is also likely to be requested when the operating address entered is a virtual address. In that case, provide documentation showing where the business actually operates, or correct the application to the actual physical operating address.

### **What the document must show**

* The applying entity's legal name
* Its current principal operating address
* A physical address, not a post office box or virtual address
* A recent issue date, except for a current office lease

### **Accepted business records**

* Bank statement issued within the last 90 days
* Utility bill issued within the last 90 days
* Government-issued letter issued within the last 90 days
* Current office lease agreement. It may be older than 90 days if it is still in force

The registered address and principal operating address can be the same when the entity genuinely operates from its registered address. If the entity uses a registered agent or corporate-services provider, that address may be correct for the registered address, but it does not by itself prove where the business actually operates.

## **Individual and ultimate beneficial owner residential address evidence**

Official reference: [Bridge proof-of-address requirements](https://apidocs.bridge.xyz/platform/customers/compliance/poa)

### **When Bridge may request it**

Bridge may ask an individual for residential proof when identity documents and claimed residence create conflicting location signals, or whenever additional verification is required.

### **What the document must show**

* The individual's full legal name
* The current residential address
* A physical address, not a post office box or virtual address
* A recent issue date, except for a current residential lease

### **Accepted residential records**

* Bank statement issued within the last 90 days
* Utility bill issued within the last 90 days
* Government-issued letter issued within the last 90 days
* Government-issued identity document issued within the last 90 days
* Current residential lease agreement. It may be older than 90 days if it is still in force

Upload the record for the exact person named in the request. A director's or founder's utility bill does not prove the company's address unless the Lisk flow explicitly offers the remote-company route below.

## **Person identity evidence**

Official reference: [Bridge identifying information overview](https://apidocs.bridge.xyz/platform/customers/customers/identifying-information-overview)

Bridge requires identifying information for verified individuals and people associated with the business. The exact tax identification number and government-issued photo identity document fields depend on the person's country and the current onboarding request.

### **Individuals outside the United States**

A valid government-issued photo identity document is required. Bridge lists these supported types:

* Driver's license
* Matriculate identity document
* Military identity document
* Permanent residency identity document
* State or provincial identity document
* Visa
* Passport
* National identity document

The front image is required for a government-issued photo identity document. The document number is optional for that photo identity document requirement. A passport or national identity document can also satisfy the tax identification requirement for an individual outside the United States when both its number and front image are provided, subject to the current country rules.

### **Individuals in the United States**

Only a Social Security Number or Individual Taxpayer Identification Number is valid for the United States individual tax identification requirement. [Bridge's general identifying-information guidance](https://apidocs.bridge.xyz/platform/customers/customers/identifying-information-overview) describes a photo identity document as optional for some United States individuals, but this is not a universal exemption. Bridge may require photo verification based on the applicable flow, verification outcome, or account activity. Provide the document whenever it is requested for an owner, Control Person, or signer.

### **Businesses**

The applying business must provide at least one valid tax identification number for its country. The exact accepted type varies by jurisdiction. Follow the field and evidence request shown in the Lisk flow.

## **Conditional Lisk remote-company route**

This is a conditional Lisk onboarding option, not a general rule for every remote company. [Bridge's public proof-of-address guidance](https://apidocs.bridge.xyz/platform/customers/compliance/poa) expressly describes a similar residential-address exception for decentralized autonomous organizations. For any other entity, use this route only when it is shown for the specific application in the Lisk onboarding flow or Lisk Support confirms that Bridge has enabled it. Bridge still makes the final verification decision.

When the route is offered for a company with no physical office:

* Keep the entity's legal registered-office address as its registered address
* Use the supported residential address where an eligible ultimate beneficial owner operates the company as the principal operating address, exactly as instructed in the flow
* The eligible ultimate beneficial owner must directly or indirectly own 25% or more of the applying entity
* Upload an accepted residential proof in that ultimate beneficial owner's name, following the recency and physical-address rules above
* A Control Person who does not own 25% or more is not eligible for this particular route. Use a different route only if Lisk confirms that Bridge has approved it for the application

Do not choose this route merely because the entity uses a registered agent, virtual office, or corporate-services provider. If the company has a separate physical office, use company-level evidence for that office.

## **Common preventable issues**

* The document is addressed to the wrong person or entity
* The legal name does not match the onboarding record
* The document shows a registered office, post office box, or virtual address instead of the requested physical operating or residential address
* The record is older than 90 days and is not a current lease
* The lease is no longer in force
* A person-level record is uploaded for a company-level request, or the reverse
* The front image of a requested government photo identity document is missing
* An official record has been recreated, rewritten, or replaced with a self-written declaration
* The remote-company route is used when Lisk did not offer it or the named ultimate beneficial owner does not own 25% or more

The safest preparation check is simple: the issuer, subject, address, date, and document purpose should all match the request.

## **Fictional Web3 company example**

Fictional example: NovaChain Labs Ltd is a Web3 infrastructure and software-as-a-service company. It sells blockchain analytics and application programming interface subscriptions to business customers. It does not hold, exchange, or transmit customer assets.

### **Scenario 1: NovaChain has a physical office**

NovaChain keeps its registered-agent address in the registered-address field and enters its actual Berlin office as the principal operating address. If Bridge asks for proof, NovaChain uploads a utility bill issued to NovaChain Labs Ltd 45 days ago that shows the Berlin office. The founder's home utility bill would not match this company-level request.

### **Scenario 2: NovaChain is fully remote**

NovaChain has no physical office. Its founder and chief executive officer, Maya, owns 60% and operates the company from her home in Lisbon. The Lisk flow offers the remote-company route. NovaChain keeps its legal registered-office address as the registered address, uses Maya's supported residential address as instructed, and uploads Maya's utility bill issued 30 days ago. Maya also provides the government photo identity document and tax-identifying information requested for her country.

If the remote-company option was not shown for NovaChain's application, NovaChain would contact Lisk Support instead of uploading Maya's utility bill under a company address request. It would not create a substitute declaration or alter an existing record.

## **Before you submit**

* Confirm whether the request is for the business or a specific person
* Confirm the full legal name matches the onboarding record
* Confirm the physical address matches the exact address entered in the flow
* Check the 90-day rule, or confirm that the lease is current
* Use the original, complete, readable record and the requested document side or image
* Use the remote-company route only when Lisk offers it and the ultimate beneficial owner threshold is met
* Ask Lisk Support to confirm Bridge's acceptance before substituting another document type


# Formation, Ownership and Company Records Evidence Guide

Customer-facing preparation guide for Bridge business verification

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

This guide helps you prepare formation, ownership, and company-record evidence that Bridge may request during business verification. The required documents depend on the entity type, jurisdiction, product, risk profile, and whether Bridge can verify the business through registry checks. Bridge, or an identity verification provider engaged by Bridge, may still send an additional request for information. This guide does not guarantee approval.

## **How to use this guide**

Prepare official records first. Use customer-created templates only where the guide explicitly says they are suitable.

* Use the exact legal entity name shown in the business verification application.
* Submit complete, legible documents. Include every page, schedule, amendment, seal, signature, and certification that forms part of the record.
* Make sure names, registration numbers, dates, addresses, and ownership percentages agree across all documents.
* Show every direct and indirect owner and account for 100% of the ownership chain.
* Identify every individual who owns 25% or more directly or indirectly. In this guide, each such individual is an [ultimate beneficial owner](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership). Also identify a [Control Person](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), meaning an individual with significant responsibility for directing the business, such as a director or senior executive. The same person may satisfy both roles.
* If a document is not in English, provide a clear translation when Bridge requests one.

## **1. Formation and legal existence**

### **Core formation evidence**

The examples below come from [Bridge's published business formation document requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation). The evidence should prove that the applicant legally exists in its jurisdiction and should match the legal name and registration details in the application.

* Corporation: articles or certificate of incorporation and all current amendments.
* Limited liability company: articles of organization, certificate of formation or incorporation, and current amendments.
* Partnership: the required record depends on the structure. For a general partnership, Bridge lists a partnership agreement, business license, or trade-name registration identifying the partners. For a limited partnership or limited liability partnership, use the applicable formation or registration certificate.
* Sole proprietorship: a business license, trade-name registration, or “doing business as” filing identifying the proprietor. A “doing business as” name is the public-facing business name when it differs from the proprietor's legal name.
* Trust: trust deed or agreement, certificate or abstract of trust, or a notarized trustee affidavit.
* Cooperative: articles of incorporation, bylaws, and membership agreement or register where applicable.

### **Good standing and current status**

Bridge may ask for evidence that the entity remains active, particularly when an automated registry check does not succeed. Use an official, current registry extract or certificate of good standing where available.

* The record should show the current legal name, registration number, jurisdiction, and active status.
* If the entity has changed its name, include the official certificate, registry filing, or other government record that connects the former name to the current name.
* Do not use a marketing page, internal certificate, or screenshot as a substitute for an official registry record.

## **2. Ownership and control**

### **Core ownership rules**

Bridge must identify the people who own or control the applicant. [Bridge's ownership requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership) allow a Control Person to confirm the ownership structure through an attestation in the hosted flow; without that attestation, ownership documents are required. An attestation is a formal confirmation that the disclosed owners are complete and accurate. It does not replace identity verification, and Bridge may request supporting records. Businesses incorporated in the European Economic Area must provide an ownership document even with an attestation, as explained in section 5. When documents are requested, use the checklist below.

* Provide evidence for all direct shareholders or members, including their ownership percentages.
* If a shareholder is another entity, provide ownership records for that intermediary so the chain can be traced. Provide its formation records as well if Bridge requests them.
* Continue through every layer until the ultimate individual owners are identified.
* Account for 100% at every ownership layer. Do not stop after identifying only the individuals above the business verification threshold.
* Identify every ultimate beneficial owner with 25% or more direct or indirect ownership and complete the identity verification requested in the applicable Bridge flow.
* If no individual meets the ownership threshold, identify the appropriate Control Person and provide governance records that support that role.

### **Acceptable ownership evidence**

Use the most authoritative current record that actually shows present ownership for the entity type. Prefer a government or statutory register when it records ownership. Otherwise, use the entity's maintained shareholder or member register, operating agreement, partnership agreement, or equivalent record. Use a customer-created chart or attestation only when [Bridge's business ownership document requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership) allow it, and make sure the full ownership chain is supported. Acceptable examples may include:

* Shareholder or member register showing names and ownership stakes.
* Shareholder ledger or capitalization table showing all holders and percentages.
* Shareholders’ agreement, operating agreement, partnership agreement, or membership agreement that records ownership.
* Stock, share, or membership certificates, supported by a complete register or ledger.
* Board or member minutes only when they clearly record current ownership or control.
* Relevant tax records, such as K-1 forms, when they clearly substantiate ownership and are appropriate for the entity type.
* Director, officer, trustee, or governing-body records for entities without individual shareholders.

### **Official evidence versus an ownership chart**

An ownership chart summarizes who owns the business. Bridge lists ownership charts and signed attestations among possible ownership documents, subject to its document and signature requirements. A self-generated document must be dated and signed by a verified Control Person, lawyer, or third-party certified public accountant where required. Do not assume an unsigned chart satisfies a request for a register or other specific record. The chart should show each legal entity and individual, jurisdiction, direct percentage, indirect percentage, and totals that account for 100% at every layer.

Use the [KYB Ownership Pack](https://docs.google.com/document/d/1MwaiTNHlheZfo94d5ZW11CTBS2A0IydOwJrYhWFCzP4/edit) to prepare a clear ownership chart and supporting ownership attestation.

In the absence of a standalone shareholders’ agreement, do not fabricate or generate one. Instead, use the [Declaration of No Shareholders’ Agreement - Guide and Template](https://docs.google.com/document/d/16QTPOmVq2XZtBIOATBF49l3mBbyVNnKmwS9adgWOaTA/edit) only when that statement is factually correct, and still provide the official register, ledger, articles, or other records that establish ownership.

## **3. Directors, officers and signatory authority**

Bridge may request a directors register, officer list, board minutes, power of attorney, letter of authority, or another record that proves who can act for the entity.

* Provide a current directors register or official filing when requested.
* Use board or member resolutions to show appointments, changes, and delegated authority where relevant.
* If the person signing or submitting is not already documented as an owner, director, or Control Person, provide clear written authority.

For a customer-created authority document, use the [Letter of Authority and Proof of Signatory Authority - Guide and Template](https://docs.google.com/document/d/19IuTcp1Uybqoe_F9Y8RybXG2x40FLuGydffCwXo9o7U/edit) and obtain the required signatures.

When Bridge requests confirmation of the individual who directs the business, use the [Control Person Attestation Form - Guide and Template](https://docs.google.com/document/d/1_filkvAQGqBULv2D3PcqHXGoH-g5YJdFe9wn0j0QlzY/edit) only after checking that the named person genuinely holds that responsibility.

## **4. Nonprofit, foundation and decentralized autonomous organization records**

### **Nonprofits and foundations**

These entities may have no shareholders. Prepare records that establish legal existence and the current people who govern or control the entity.

* Articles or certificate of incorporation or formation.
* Bylaws, foundation charter, trust deed, or equivalent governing instrument.
* Tax-exempt application, determination letter, registered-exemption record, or local equivalent where applicable.
* Current director, trustee, council, founder, or officer register.
* Board minutes or annual filings that confirm current controlling persons.

### **Decentralized autonomous organizations**

For a decentralized autonomous organization with a legal entity, provide the entity’s ordinary formation and ownership or control records. Bridge may also request decentralized autonomous organization-specific materials.

* White paper or protocol documentation that explains the organization and activities.
* Membership or token agreement.
* Governance framework, voting rules, and recent voting records.
* Legal wrapper records and a clear explanation of how onchain governance connects to the legal entity.
* Records identifying the individuals who exercise significant control when token ownership alone does not show control.

## **5. European Economic Area-specific checks**

For businesses incorporated in the European Economic Area, Bridge’s current European Economic Area requirements add specific evidence and associated-person obligations.

* Provide an ownership document at the business level; a Control Person's attestation alone does not replace it.
* If automated registry verification fails, provide both formation evidence and evidence of good standing.
* Provide a complete director list with the required identifying details.
* Complete the identity verification required by Bridge for every ultimate beneficial owner, at least one director, and every authorized signer.
* Provide a letter of authority for an authorized signer who is not documented as a director, owner, or Control Person.
* Check the live Bridge requirements before submission because product scope and European Economic Area evidence rules may change.

## **6. Common rejection reasons**

* The legal name or registration number does not match the business verification application.
* The document is cropped, blurred, password-protected, incomplete, or missing schedules or amendments.
* The record is outdated and does not show the current owners, directors, or legal status.
* Ownership percentages do not add to 100%, or an intermediary entity is left unexplained.
* A formation document is submitted as ownership evidence even though it does not list shareholders or members.
* A self-generated ownership record is undated, unsigned, does not name the entity, or is not signed by an appropriate Control Person, lawyer, or third-party accountant where required.
* A stock or share certificate is submitted without a complete register or ledger that shows all holders.
* A person is described as a Control Person or authorized signer without supporting governance or authority records.
* The current name cannot be connected to the name on historic formation or ownership records.
* The entity relies on a nominee, registered agent, virtual-office provider, or other intermediary without explaining the underlying owners and controllers.

## **7. Fictional example: NovaChain Labs Ltd**

NovaChain Labs Ltd is a fictional Web3 infrastructure company. It develops blockchain analytics software and earns revenue from software-as-a-service subscriptions and protocol-integration fees.

### **Ownership structure**

* Maya Chen owns 60% of NovaChain Labs Ltd directly.
* Orbit Holdings owns the remaining 40%.
* Luis Romero owns 75% of Orbit Holdings, giving him 30% indirect ownership of NovaChain Labs Ltd.
* Ava Singh owns 25% of Orbit Holdings, giving her 10% indirect ownership of NovaChain Labs Ltd.
* The ultimate ownership of NovaChain Labs Ltd is therefore Maya Chen 60%, Luis Romero 30%, and Ava Singh 10%. This accounts for 100%.
* Maya and Luis meet the 25% or more threshold. Ava is below the threshold, but she still appears in the chain so the ownership structure is complete.
* Maya is also the chief executive officer, a director, and the Control Person.

### **Example evidence pack**

* NovaChain Labs Ltd certificate and articles of incorporation, plus a current certificate of good standing if requested.
* NovaChain Labs Ltd shareholder register showing Maya Chen at 60% and Orbit Holdings at 40%.
* Orbit Holdings formation records and shareholder register showing Luis Romero at 75% and Ava Singh at 25%.
* A one-page ownership chart showing both layers and the 60%, 30%, and 10% ultimate ownership positions.
* Identity verification information for Maya Chen and Luis Romero as ultimate beneficial owners, plus Maya’s Control Person information.
* Current directors register and a board resolution or authority document if the person submitting is not already clearly authorized.
* The ownership chart helps the reviewer follow the chain, while the official registers and formation records substantiate it.

## **Related Lisk templates**

* [Signed Ownership Attestation Letter - Guide and Template](https://docs.google.com/document/d/1mk0pSCfQXrlb64XU7vDgbcwaNC166zho5VrNEIuj-zA/edit)
* [Directors, Officers, Trustees and Council Members Schedule - Guide and Template](https://docs.google.com/document/d/17Afl3yDFe879l9TWPZKsCqSL5nBpLztdZ8wODA0xZGg/edit)
* [Letter of Authority and Proof of Signatory Authority - Guide and Template](https://docs.google.com/document/d/19IuTcp1Uybqoe_F9Y8RybXG2x40FLuGydffCwXo9o7U/edit)
* [Proof of Relationship Explanation and Evidence Cover Sheet](https://docs.google.com/document/d/1pxbr2U6feAghd_a7rKti-NdtPnndHHkn4Nzcz4WkHgE/edit)

## **Official Bridge references**

[Bridge business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) · [Bridge business formation document requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation) · [Bridge business ownership document requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership) · [Bridge supported document purposes](https://apidocs.bridge.xyz/platform/customers/compliance/docs) · [Bridge current European Economic Area requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements)

Always check the live Bridge documentation and the request shown in the product flow before submitting. If Bridge or an identity verification provider engaged by Bridge asks for a different or additional record, follow that request and contact Lisk Support if the requirement is unclear.


# Financial, Tax, Regulatory and Special Request for Information Evidence Guide

Customer guidance for conditional and additional Bridge requests

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

## **Purpose**

Bridge may request these records during an additional compliance review, when assessing access to a product or payment network, to complete missing business verification information, or in a later request for information. They are conditional. Do not prepare or upload every item by default. Follow the exact request shown in the product or sent by Support.

### **Critical submission rules**

* Use genuine, current, and unaltered records issued by the proper institution or qualified professional. Never fabricate, backdate, or alter the substance of official evidence, or combine records in a way that misrepresents their issuer or contents. False, altered, or misleading evidence may cause rejection or account restrictions and may trigger consequences under Lisk's Terms of Service and the applicable provider terms.
* Match the exact customer, account, person, legal name, document type, time period and currency named in the request.
* Upload the complete, legible document, including all requested pages. Do not submit password-protected files or redact information unless the request permits it.
* If a name, address, amount or date does not match the application, explain the difference clearly and provide the supporting record Bridge asks for.
* Use the requested upload route. If the request is unclear, ask Support to confirm the required evidence before submitting.

### **How to distinguish the requests**

* Proof of funds shows that money or assets are currently available.
* Source of funds shows the immediate origin of a specific payment, balance or transfer.
* Source of wealth shows how a person or entity accumulated its broader wealth over time.
* Flow of funds explains how money moves through the business model and account.
* Account purpose explains why the account is needed and how it will be used.

These requests are not interchangeable. Answer the exact one that Bridge asks.

## **Financial evidence**

### **Financial statements**

Provide financial statements only when the request for information names them or asks for revenue, financial capacity or operating activity. Bridge does not publish one universal financial-statement format for every business verification case.

* Use the requested record, such as audited accounts, signed annual accounts, management accounts, profit and loss statement, balance sheet or cash-flow statement.
* Show the correct legal entity, accounting period, currency and preparation or audit status.
* If the statements cover a parent, group or different entity, explain the relationship and provide entity-level records if requested.
* Do not convert internal estimates into an official-looking statement. Label genuine management accounts accurately.

### **Bank or custody statements and proof of funds**

Bridge’s business onboarding guidance identifies bank statements as an example of proof of funds. A custody or exchange statement should be used only when Bridge accepts it for the exact request.

* Use an official statement or balance confirmation showing the holder’s legal name, institution, account identifier, statement date or period, and the relevant balance or transactions.
* For current availability, provide a recent statement or official balance confirmation covering the amount Bridge asks about.
* For digital assets, follow the exact request for a regulated custodian statement, exchange export or wallet evidence. Do not assume a screenshot or public wallet address is sufficient.
* Do not edit a screenshot, recreate a ledger or remove material account details unless Bridge explicitly permits redaction.

### **Proof of bank-account ownership**

Use a bank-issued statement, account confirmation letter or official portal export that identifies the legal account holder and the relevant account details. A document proving account ownership does not automatically prove operating or residential address.

### **Proof of source of funds**

Source of funds concerns the immediate origin of the specific money being reviewed. Common examples include software-as-a-service revenue, an equity investment, a loan, an asset sale or an internal treasury transfer.

* Pair a short factual explanation with records that reconcile, such as customer contracts and invoices plus matching bank credits, an investment agreement plus incoming transfer, or a loan agreement plus disbursement.
* Make amounts, dates, counterparties and transaction references easy to trace across the documents.
* If the funds came through several accounts, explain each step and provide the requested supporting statements.

For the operating narrative, use [Flow of Funds - Guide and Template](https://docs.google.com/document/d/1lczJPb4hIqSksGV377QBV5X9P-z5Ti-IC9y8w6W06nY/edit) and keep it consistent with the evidence submitted here.

### **Proof of source of wealth**

Source of wealth concerns how the named person or entity accumulated broader wealth over time. It is wider than the origin of one transfer.

* Evidence may include audited accounts, long-term salary or dividend records, tax returns, investment statements, company-sale records, inheritance records or other documents named in the request for information.
* If Bridge names an ultimate beneficial owner, respond for that person rather than substituting company-level evidence.
* Provide a concise narrative that connects the evidence to the total wealth being reviewed. Do not submit unrelated documents merely to increase volume.

## **Tax evidence**

### **Proof of tax identification number or Employer Identification Number**

* Use an official tax-authority confirmation, registration certificate, government registry extract or filed tax record that shows the exact number and legal name.
* Confirm that the identification type and issuing country match the information entered in the business verification application.
* Do not type the number into a self-created letter if Bridge asks for official proof.

### **Tax returns**

* Submit the filed return for the exact entity or person, jurisdiction and tax period named in the request. Include the filing confirmation or receipt when requested.
* Tax returns are sensitive and conditional. Do not upload them by default, and redact only when Bridge confirms that the redaction is acceptable.
* If the return is not in the applying entity’s name, explain the relationship and ask whether substitute evidence is acceptable.

## **Regulatory and anti-money laundering evidence**

### **Regulatory license or registration**

* Provide the current regulator-issued license, registration certificate or official register extract showing the legal name, license or registration number, permitted activity, jurisdiction and status.
* If you believe the business does not require a license, explain its actual activities and why you believe no license is required. This factual explanation is not a regulator-issued exemption. Ask Bridge whether it needs an official exemption record, a legal opinion, or other evidence; do not invent an exemption certificate.

### **Registered exemption**

Use a formal exemption certificate, regulator record, no-action letter, similar regulator letter, or another record explicitly accepted in the request for information. A legal opinion should be prepared only when Bridge permits it and by appropriately qualified counsel. Do not produce your own exemption certificate or similar official record. If no regulator-issued record exists, explain that fact and ask Bridge whether it will accept a legal opinion or another alternative.

### **Anti-money laundering policy, audit and comfort letter**

* Anti-money laundering policy: provide the approved, current policy that reflects the business’s actual products, customers, jurisdictions and controls.
* Anti-money laundering audit: provide the final independent report for the requested scope and period, including the issuer and report status.
* Anti-money laundering comfort letter: a written assurance about specified compliance matters, not a substitute for a policy or audit. Obtain it from the independent auditor, counsel, or compliance professional specified by Bridge, covering the exact matters Bridge requests.
* These items are conditional. Provide them to Bridge only through the secure method specified in the Platform or individual request. Lisk Support may coordinate the request, but it does not validate a policy, audit, comfort letter, license, or exemption on Bridge's behalf. Do not submit a generic policy or comfort letter that does not match the actual operating model.

## **Authority, relationship and legal-event evidence**

### **Electronic signature certificate**

Use the certificate or audit trail generated by the signature platform for the relevant agreement. It should identify the document, signer, signing events and integrity or completion information requested.

### **Power of attorney**

Provide the signed and effective power of attorney identifying the parties and powers granted. Include expiry, notarization, apostille or legalization only when required by the request or applicable document.

### **Proof of relationship, name change or court order**

* Proof of relationship may include the specific official certificate, contract, registry record or other evidence that establishes the legal or financial relationship Bridge asks about.
* For an entity or individual name change, provide the official registry filing, certificate or legal record connecting the old and new names.
* For a court order, provide the complete official order or certified copy requested. Do not create a summary as a substitute for the legal document.

## **Other and ad-hoc requests for information**

[Bridge's supported document list](https://apidocs.bridge.xyz/platform/customers/compliance/docs) includes an “other” category for evidence without a dedicated category. When Bridge uses this category, the individual request itself is the checklist. It should state the fact to be verified, the person or entity concerned, the relevant period, and any recency, format, language, translation, or certification requirements.

* Confirm the claim to be proven, the subject, period, recency, format, language and any certification or translation requirement.
* Possible requests include proof of operating activity, invoices, customer or vendor contracts, receipts, bills of lading, payroll records, product or service evidence, or request-specific custody and wallet evidence.
* Submit one concise cover note plus the genuine records that answer the request. More documents are not automatically better.
* If the requested record does not exist, state that fact and ask which alternative evidence Bridge will accept. Do not create or alter an official record.

## **Regional and product-specific conditions**

Access to a particular product or payment network, or a regional verification rule, may require additional evidence. For businesses incorporated in the European Economic Area, [Bridge's current European Economic Area requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements) include a business-level ownership document and, if automated registry verification fails, both formation evidence and evidence of good standing. The Lisk Platform is non-custodial: it does not hold or control client assets. Do not treat requirements for a separate Bridge custodial-wallet product as a universal Lisk checklist. Apply only the product-specific requirements that Bridge identifies for the application. Proof of address may also be required for a specific payment network or when location information conflicts. Treat these as conditional rules, not a universal checklist.

## **Fictional Web3 example**

NovaChain Labs Ltd. is a fictional Web3 software-as-a-service company that sells blockchain analytics subscriptions and application programming interface integrations to business customers. It does not hold, exchange, transmit or safeguard customer assets.

Bridge asks NovaChain for proof of funds, source of funds, tax identification number evidence and clarification of regulatory status. NovaChain prepares:

* A recent bank-issued statement in NovaChain’s legal name showing an operating balance of 180,000 United States dollars and the relevant account identifier.
* Five customer invoices totaling 68,000 United States dollars, the related software-as-a-service contracts and the matching credits on the bank statement to evidence the immediate source of funds.
* Its most recent signed management accounts, clearly labeled as management accounts, showing software-as-a-service revenue and cloud, security and contractor costs.
* The official tax-authority confirmation showing NovaChain’s Employer Identification Number or local equivalent and legal name.
* A short factual cover note explaining that NovaChain sells software, does not handle customer assets, and is not presenting itself as an exchange or money transmitter. It asks Bridge to confirm whether any license or exemption evidence is still required instead of fabricating one.

NovaChain uses [Account Purpose and Expected Activity - Guide and Template](https://docs.google.com/document/d/1W-qm1kJI8nmbaxscEVinHKKggeE-UO0KHyeQcKDkI8o/edit) to align the intended account use and [Flow of Funds - Guide and Template](https://docs.google.com/document/d/1lczJPb4hIqSksGV377QBV5X9P-z5Ti-IC9y8w6W06nY/edit) to align the movement of customer receipts and operating payments. This example is illustrative only and does not guarantee Bridge acceptance.

## **Final check before submission**

* The evidence answers the exact request from Bridge or an identity verification provider engaged by Bridge and covers the named person or entity.
* Every official record is genuine, complete, legible and unaltered.
* Names, addresses, amounts, dates and counterparties reconcile with the business verification application or are explained.
* The document period, recency, language, certification and translation requirements are satisfied.
* No password protection, accidental redaction, missing page, draft placeholder or unrelated sensitive record remains.
* The submission uses the secure upload flow provided for the case by the Platform, Bridge, or its identity verification provider, or the channel named in the request for information.

## **Related Lisk guides**

* [Flow of Funds - Guide and Template](https://docs.google.com/document/d/1lczJPb4hIqSksGV377QBV5X9P-z5Ti-IC9y8w6W06nY/edit)
* [Account Purpose and Expected Activity - Guide and Template](https://docs.google.com/document/d/1W-qm1kJI8nmbaxscEVinHKKggeE-UO0KHyeQcKDkI8o/edit)
* [Business Source of Funds Declaration and Evidence Schedule](https://docs.google.com/document/d/1J54e4LaOkRERg4RJkv60ketTbkbyvpNt2iey0sFdgkE/edit)
* [Source of Wealth Statement and Evidence Schedule](https://docs.google.com/document/d/13oQtBRlBKEYzzp-pNUbtphRBPDgYS_07kBs50kdGg2A/edit)
* [High-Risk Activities, Customer Funds and Compliance Controls Questionnaire](https://docs.google.com/document/d/1R4r8_nfgKoFN8kqrMXXVPVXn7P304o6wdC5ZhL6pW4Y/edit)

## **Official Bridge references**

* [Bridge supported documents](https://apidocs.bridge.xyz/platform/customers/compliance/docs)
* [Bridge business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview)
* [Bridge European Economic Area updated requirements](https://apidocs.bridge.xyz/platform/customers/customers/eea-updated-requirements)
* [Bridge missing requirements and issues](https://apidocs.bridge.xyz/platform/customers/customers/missing-requirements-and-issues)


# KYB by Entity Type and Jurisdiction

{% hint style="info" %}
🛂 Every business we verify answers the same core questions, but **the documents that satisfy them, and the follow-ups you'll get, depend on where you're registered and what kind of entity you are**.

This guide is the companion to [Complete Business Verification (KYB)](/guides/getting-started/complete-business-verification-kyb). That article walks you through the process everyone goes through. **This one is about what's different for you:** which version of each document fits your entity type, the follow-up questions that tend to come up, and how long verification has typically taken for businesses like yours.

**Verification has typically taken 8–11 calendar days** from submission to approval. How quickly you reply to our follow-up requests is the single biggest factor.
{% endhint %}

This guide covers four common entity types:

* UAE limited company
* Cayman company
* Swiss AG
* Swiss foundation.

If yours isn't listed, use the closest match as your guide and contact support about anything that doesn't fit.

For a full preparation checklist by country, see the guides for the [United States](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-united-states-entities), the [Cayman Islands](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-cayman-islands-entities), and the [British Virgin Islands](/guides/getting-started/kyb-by-entity-type-and-jurisdiction/business-verification-preparation-guide-for-british-virgin-islands-entities).

***

### How long it takes

{% hint style="info" %}
⏱️ **Verification has typically taken 8–11 calendar days from submission to approval.**

These are observed ranges from the businesses we've verified so far rather than a fixed commitment: the more layers there are between your company and the people who ultimately own it, the longer it tends to take.

What sets the pace is how quickly you reply to our follow-up requests. The businesses verified fastest answered each request the same day they received it.
{% endhint %}

Here's how it has gone for the entity types we've verified so far:

| Entity type                              | Jurisdiction        | Typical time to approval | What we asked for                                                                                                                  |
| ---------------------------------------- | ------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
| Limited company                          | 🇰🇾 Cayman Islands | \~11 days                | <p>• Operating address confirmation<br>• source of funds<br>• ownership chart<br>• licensed-partner clarification</p>              |
| Limited company (holding-company owners) | 🇦🇪 UAE            | \~9 days                 | <p>• Business description in place of a website<br>• ownership chain through holding companies<br>• proof of address</p>           |
| Corporation (AG)                         | 🇨🇭 Switzerland    | \~8 days                 | <p>• Ownership chart of the parent<br>• operating address confirmation<br>• source of funds</p>                                    |
| Foundation (Stiftung, nonprofit)         | 🇨🇭 Switzerland    | \~8 days                 | <p>• Written explanation in place of the shareholders question<br>• date of birth<br>• a proof of address dated within 90 days</p> |

A directly-owned company is typically approved in about a week. A company held through two holding companies, or one with no shareholders at all, usually takes a few days longer.

***

### Requests for Information (RFIs)

After you submit, we review everything you've sent. If something is missing or unclear, we come back with a **Request for Information (RFI)**: a request for one more document, or a quick clarification.

Getting one is completely normal. Every business we've verified so far received at least one.

**RFIs are sent by email**, to the address you signed up with. If you're expecting one, check your spam or junk folder as well, then reply on the same email thread with the document or clarification requested.

* These emails are sent from [**rfi@lisk.com**](mailto:rfi@lisk.com)

**Which RFIs you receive depends on your entity type and where you're registered.** A foundation gets asked about shareholders it doesn't have. A Cayman company gets asked about its registered-agent address. A company owned through holding companies gets asked to prove the chain.

These are the ones we see most often:

| Common RFI                                                                | Why it happens                                                         | What to include                                                                                                                                                                                               |
| ------------------------------------------------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "Your operating address looks like a registered agent or virtual address" | The address appears to be a registered agent or virtual office address | Send a lease or utility bill for your actual office. If you're fully remote, tell us up front. Residential proof for an owner with 25% or more may be accepted when the verification flow offers this option. |
| "Provide a signed ownership structure chart"                              | One of your owners is a company                                        | Attach the chart with your first submission                                                                                                                                                                   |
| "Provide documentation evidencing ownership of the holding entities"      | Your ownership runs through one or more holding companies              | Send each holding company's register or articles, plus a UBO declaration                                                                                                                                      |
| "Provide a document confirming shareholders and percentages"              | Your entity has no share capital (foundations, nonprofits)             | Send your commercial register extract with a short written explanation                                                                                                                                        |
| "Provide a recent proof of address"                                       | Your document is older than 90 days                                    | Get a fresh copy before you submit                                                                                                                                                                            |
| "Provide source-of-funds evidence"                                        | Your description alone wasn't enough                                   | Keep audited financials, a statement or a tax return on hand                                                                                                                                                  |
| "Confirm your website / business description"                             | You didn't give us a website                                           | Check "no website" and write a specific, plain-language description of what you do                                                                                                                            |
| "Confirm your licensed partners"                                          | Your terms mention regulated partners                                  | Be ready to name them and attach the agreement                                                                                                                                                                |

***

### The documents, explained

* 📄 Formation document → what proves your company legally exists

  This is the document filed with your company registry when your entity was created. It needs to show your **legal entity name** and **registration number**.

  Depending on where you're registered, yours may be called:

  * 🇦🇪 UAE
    * Certificate of incorporation (plus trade license, where issued)
  * 🇰🇾 Cayman
    * Certificate of incorporation
  * 🇨🇭 Switzerland (AG/GmbH)
    * Certificate/Articles of incorporation
  * 🇨🇭 Switzerland (Stiftung)
    * Deed of incorporation, notarized.
      * Foundations do not receive a "certificate", so submit the deed wherever a certificate is requested.
* 🧾 Ownership evidence → who owns the company

  A document from an official source, or signed by one of your officers, showing your shareholders and their percentages.

  * **Register of members / shareholder register** — if you're a limited company or an AG, this is the one we'll expect.
  * **Commercial register extract** — for Swiss entities. If you're a foundation, this replaces the shareholder register entirely, since you have no share capital or cap table.
  * **Cap table** — fine if you don't have a formal register.
  * **Memorandum / Articles of Association** — use this to show the sole shareholder of a holding company.
* 🗺️ Ownership structure chart → how ownership flows up to real people

  A signed, dated chart showing **every intermediary and ultimate owner with their percentages**, all the way up to the individuals at the top.

  If your company is owned by another company — a holding company, a parent, or any group structure — you will almost certainly be asked for this. Sending it with your first submission usually saves you an entire round of follow-ups.

  If a holding company sits in your chain, add a **UBO declaration** as well: a signed statement confirming that a named person is the ultimate beneficial owner of a named entity.
* 👤 UBOs, control persons and signers → the people behind the business

  * **UBO (ultimate beneficial owner)** — anyone who owns or controls **25% or more** of your business. You only need to list people at or above that threshold, and their percentages **don't have to add up to 100%**. Use whole numbers.
  * **Control person** — someone with significant responsibility to manage or direct your business: your CEO, a director, a managing officer. You need at least one.
  * **Signer** — someone authorized to approve transactions. You need at least one here too.

  For each of them, have ready: full legal name, title, date of birth, residential address, photo ID, and tax ID where applicable.

{% hint style="info" %}
💡 If your UBOs aren't officers of the entity — common if you're a subsidiary or owned by a foundation — you'll need to nominate a separate control person and signer who is.
{% endhint %}

* 🏢 Proof of address → where the business actually operates

  A **lease agreement or utility bill in your entity's name, dated within the last 90 days**.

  Common reasons we follow up:

  * You've given a **registered agent, PO box or virtual office** address — these addresses prompt a follow-up request.
  * The lease is in a **parent or sister company's name** — we can't accept it for the entity you're verifying.
  * The document is **older than 90 days** — we'll request a more recent copy.

  If your business is fully remote with no physical office, residential proof of address for an owner with 25% or more may be accepted, but only when the verification flow offers this option. See the [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide).
* 💰 Source of funds → where the money comes from

  You'll pick a primary source (for example, sales of goods and services, or investment income), describe it in a sentence, and give your estimated annual revenue plus the volume you expect to send and receive each month.

  If we ask for a supporting document, send one of these:

  * Audited financial statements
  * Recent bank or brokerage account statement
  * Tax return

  Make sure it's recent — the 90-day rule applies here too.
* ✅ Evidence of good standing

  Anything that shows your entity is active and authorized to operate: a certificate of good standing, a recent registry extract, a recent official filing, or, if you're a subsidiary, a signed parent funding commitment.
* 🇪🇺 EEA required information

  If this applies to you, we'll ask: *"Are you registered with any foreign tax authorities outside of your incorporation country?"* Answer yes or no, and have the registration details on hand if the answer is yes.

***

### What's different, by jurisdiction and entity type

Find the column that matches your entity and read down it. Everything else on this page is the explanation behind these cells.

| Requirement                   | 🇦🇪 UAE → limited company                                     | 🇰🇾 Cayman → limited company                                                                            | 🇨🇭 Switzerland → AG/GmbH                                                       | 🇨🇭 Switzerland → foundation (Stiftung)                                  |
| ----------------------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Formation document**        | Certificate of incorporation (+ trade license)                 | Certificate of incorporation                                                                             | Certificate/Articles of incorporation                                            | Deed of incorporation (notarized; often bilingual DE/EN)                  |
| **Ownership evidence**        | Register of members for each holding company + UBO declaration | Register of members                                                                                      | Shareholder register                                                             | Commercial register extract (no shareholder register or cap table exists) |
| **Ownership structure chart** | Required; ownership runs through holding companies             | Required; signed and dated                                                                               | Required whenever a parent entity owns the company                               | Not applicable; just be ready to tell us why in writing                   |
| **Beneficial owners**         | The individuals behind each holding company                    | Direct individual owners                                                                                 | UBOs of the parent; add a separate control person/signer if UBOs aren't officers | Foundation council members are treated as the UBO equivalent              |
| **Proof of address**          | Signed lease for the physical office                           | Lease or utility bill; if it's a registered-agent address we'll ask you to confirm the operating address | Lease in the entity's own name, or commercial register extract                   | Lease agreement for the operating address                                 |
| **Source** **of** **funds**   | Description + statement if requested                           | Account statement requested                                                                              | Audited financials, brokerage statement or tax return                            | Audit report                                                              |
| **EEA question**              | Not asked                                                      | Not asked                                                                                                | Not asked                                                                        | Asked                                                                     |
| **Typical time to approval**  | \~9 days                                                       | \~11 days                                                                                                | \~8 days                                                                         | \~8 days                                                                  |

***

### Example: an entity with no shareholders

{% hint style="info" %}
🧩 Foundations, associations, nonprofits and similar entities have no share capital and no owners, so the questions about shareholders and ownership percentages simply don't apply to you.

Here's what to submit instead:

1. **Send your registry extract instead of a shareholder register.**\
   Wherever ownership evidence is requested, upload your commercial or foundation register extract. It's the official record of who controls your entity.
2. **List your council, board or trustees as the controlling persons.** They take the place of beneficial owners. Give each one's full legal name, title, date of birth and residential address.
3. **Nominate at least one control person and one signer** from that group, someone who can act for the entity and approve transactions.
4. **Add one line of explanation.** Something like: *"Our entity is a foundation. It has no shareholders, share capital or ownership percentages. The foundation council listed above holds control."*
5. **Skip the ownership structure chart** unless another company sits above you. Just say so in writing rather than leaving the field blank.

That one line of explanation is normally all we need to close the question, no extra documents required.
{% endhint %}


# Business Verification Preparation Guide for Cayman Islands Entities

A practical pre-flight guide for Cayman companies onboarding to Lisk

{% hint style="warning" %}
**Important**: This guide covers typical Cayman exempted companies limited by shares and supplements Lisk's general business verification guide. Other structures need different evidence. Reviews are risk-based, so Bridge may request additional or replacement documents.
{% endhint %}

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

[Complete Business Verification](/guides/getting-started/complete-business-verification-kyb): the full Lisk verification walkthrough.

[Business Verification by Entity Type and Jurisdiction](/guides/getting-started/kyb-by-entity-type-and-jurisdiction): broader entity and jurisdiction guidance.

## **What is different for Cayman companies?**

* A Cayman exempted company's legal registered office is generally the address of its licensed corporate-services provider. A post office box or virtual office alone does not prove where the business operates.
* Remote companies should prepare separate evidence of their operating setup before starting.
* [For the Lisk/Bridge flow](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), disclose every individual who directly or indirectly owns 25% or more. Cayman law also identifies a beneficial owner through [ultimate effective control or control by other means](https://gov.ky/documents/35692/0/Beneficial%2BOwnership%2BTransparency%2BAct%2B%2B%282026%2BRevision%29%2C.pdf/451d0c7a-a64d-65da-974e-4fd7863af95f). At least one Control Person must also be identified.
* Layered ownership must be traceable through every intermediary entity to each qualifying ultimate beneficial owner. Prepare a current shareholder, member, partner, or equivalent ownership record for every intermediary entity, not only the applying company.
* Cayman applications may receive follow-up requests for business activity, source of funds, or regulatory evidence after submission.

## **Prepare before you start**

### **Company and business**

* Legal entity name, trade names, [Cayman Company Registration Number](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/identification), incorporation date, registered address, and principal operating address.
* [Certificate of Incorporation](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation) as the primary formation document. Keep the current Memorandum and Articles of Association ready if Bridge requests additional formation or governance evidence.
* A clear business description, website or product information, intended account use, and source of funds. If requested in the Lisk flow, also provide estimated annual revenue and expected monthly transaction volume.
* A current Register of Members. Also keep the current [Register of Directors and Officers](https://gov.ky/documents/35692/0/Companies%2BAct%2B%282026%2BRevision%29%2C.pdf/345cf168-32c9-8b07-c7f3-1e645b076320) available in case Bridge requests control or signatory evidence.

### **People and ownership**

* Personal information and government identity document for every individual the onboarding form asks you to verify, including every ultimate beneficial owner holding 25% or more and every required Control Person.
* Identify at least one Control Person, such as a director or executive with significant responsibility. The signer must be authorized to act for the company. One person may fill both roles, but a Control Person is not automatically an ultimate beneficial owner.
* For corporate shareholders or layered structures: a signed and dated ownership chart showing every intermediary entity, ownership percentage, and the natural persons behind the chain.
* Current ownership evidence for each intermediary entity. The complete pack should account for 100% of the ownership chain. If a shareholders' agreement is requested but none exists, use [Declaration of No Shareholders’ Agreement - Guide and Template](https://docs.google.com/document/d/16QTPOmVq2XZtBIOATBF49l3mBbyVNnKmwS9adgWOaTA/edit).

### **Conditional evidence to keep ready**

* [Operating-address evidence](https://apidocs.bridge.xyz/platform/customers/compliance/poa), if the principal operating address requires verification.
* Proof of nature of business when the website or public information is limited. A cover sheet must be accompanied by records such as contracts, invoices, receipts, product material, or partner agreements. Use [Proof of Nature of Business - Evidence Guide and Cover Sheet](https://docs.google.com/document/d/1CK5i-fW4aklsGvfGyIIYYvxxtYgavgQSujayzPkSi2g/edit) to organize the submission.
* If requested: source of funds evidence, such as recent bank statements, financial statements, tax records, or a signed parent-funding letter with supporting documents.
* If the company conducts regulated activity outside the Lisk Platform, prepare any applicable Cayman Islands Monetary Authority registration or license, anti-money laundering materials, a description of how funds move through the business, and regulated-partner agreements. [Cayman virtual-asset custody and trading-platform services require a virtual asset service provider license](https://www.cima.ky/vasp-faq); other in-scope virtual-asset services require registration or an applicable waiver. Clearly separate activities conducted outside Lisk from any activity intended to be enabled through Lisk or Bridge. A license does not make a use case eligible if it is prohibited by Bridge's terms or [high-risk activity rules](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/highrisk). Describe any handling of customer funds.

## **Address evidence for remote Cayman companies**

The registered address and principal operating address can be the same when the company genuinely operates there. If the company uses the corporate-services provider's office only for legal registration, use that address only as the registered address, enter the actual operating location as the principal operating address, and follow the route below.

| **Situation**                             | **What to enter**                                                                                                                                                                                                                                                                                       | **What to prepare**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Separate physical office or workspace** | Keep the corporate-services provider's registered-office address as the registered address. Enter the actual office as the principal operating address.                                                                                                                                                 | Evidence in the applying company's name: a bank statement, utility bill, or government letter issued within the last 90 days, or a current office lease. It must show a physical operating address, not a post office box or virtual office.                                                                                                                                                                                                                                                                                                                                                                     |
| **Fully remote company**                  | Keep the corporate-services provider's registered-office address as the registered address. When Lisk offers the remote-company route, enter the supported residential address where an eligible ultimate beneficial owner holding 25% or more operates the company as the principal operating address. | Upload accepted residential proof for that ultimate beneficial owner. A bank statement, utility bill, government-issued letter, or government-issued identity document must have been issued within the last 90 days; a residential lease may be older if it is current. Use this route only after the Lisk flow or Lisk Support confirms that Bridge has enabled it for your application. [Bridge's public proof-of-address requirements](https://apidocs.bridge.xyz/platform/customers/compliance/poa) do not provide a general exception for ordinary remote companies. Final acceptance remains with Bridge. |

If no individual owns 25% or more, identify anyone who exercises ultimate effective control or control by other means. If Cayman rules identify no registrable beneficial owner, a senior managing official is recorded as the contact person; this is not automatically the Lisk Control Person. The remote-company route remains limited to an eligible ultimate beneficial owner holding 25% or more unless Lisk confirms that Bridge has approved another route for the application.

## **Cayman ownership records and Lisk roles**

| **Role**                      | **Meaning**                                                                                                                                                                                         | **What to do**                                                                                                                                                                                    |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ultimate beneficial owner** | For this Lisk/Bridge flow, an individual who directly or indirectly owns 25% or more. Cayman law may also identify a beneficial owner through ultimate effective control or control by other means. | Disclose every qualifying ultimate beneficial owner, complete the requested identity checks, and use only an eligible ultimate beneficial owner holding 25% or more for the remote-company route. |
| **Control Person**            | A director or executive with significant responsibility for the company. This person may or may not be an ultimate beneficial owner.                                                                | Identify at least one. A non-owner Control Person is not eligible for the 25%-owner address option described here; a different route requires Bridge's approval.                                  |

Ownership attestation: A Control Person can confirm the disclosed ownership structure using the [checkbox in Bridge's hosted flow](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), when that option is available for the application. This may satisfy the ownership-evidence requirement; it does not replace disclosure or identity checks for the required people, and Bridge may request documents. If separate confirmation of the Control Person's role is requested, use [Control Person Attestation Form - Guide and Template](https://docs.google.com/document/d/1_filkvAQGqBULv2D3PcqHXGoH-g5YJdFe9wn0j0QlzY/edit).

## **Common Cayman follow-ups**

| **Follow-up**          | **Why it happens**                                                                               | **Prepare this**                                                                                                                                                                                                                                                                                                                                                                                     |
| ---------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Operating address**  | The registered-office address does not show where the company operates.                          | The correct company-level evidence or the conditional remote-company route described above.                                                                                                                                                                                                                                                                                                          |
| **Ownership chain**    | The Register of Members shows only a corporate shareholder or does not trace the full structure. | A signed ownership chart plus current evidence for each intermediary entity.                                                                                                                                                                                                                                                                                                                         |
| **Source of funds**    | The source, legal relationship, or movement of funds is unclear.                                 | Evidence matching the stated source of funds. For example, if a parent funds the company, evidence may include a signed funding letter and the relevant grant, equity, or loan documents.                                                                                                                                                                                                            |
| **Nature of business** | The website or public information does not prove the stated activity.                            | Contracts, invoices, receipts, product information, licenses, or partner agreements, organized with the cover sheet.                                                                                                                                                                                                                                                                                 |
| **Regulated activity** | It is unclear whether the company conducts regulated activity or handles money for customers.    | State the exact activity and submit any current Cayman Islands Monetary Authority registration, license, or waiver, anti-money laundering materials, funds-flow details, and regulated-partner agreements through the method Bridge specifies. For virtual assets, distinguish activity conducted outside Lisk from any custody, trading-platform, or other service intended through Lisk or Bridge. |

## **Fictional example**

NovaChain Labs Ltd is a fictional Cayman exempted company that provides Web3 infrastructure and business-to-business software-as-a-service integrations. Its preparation pack includes the Certificate of Incorporation, current Memorandum and Articles, Register of Members, Register of Directors and Officers, and a signed ownership chart. Maya Chen owns 60% directly. Orbit Holdings owns 40%; Orbit is owned 75% by Luis Romero and 25% by Ava Singh, producing ultimate ownership of 60%, 30% and 10%. Maya and Luis are the ultimate beneficial owners holding 25% or more. Maya is also chief executive officer, director and Control Person.

The corporate-services provider’s office remains the registered address. If NovaChain has a separate office, it prepares current company-level address evidence. If it is fully remote and Lisk offers the remote-company route, it may use recent residential proof for Maya, mapped to her as the eligible 60% ultimate beneficial owner. It also prepares the requested person identity document and address evidence, an executed software-as-a-service contract with a recent invoice and receipt, and a clear account-purpose and source-of-funds explanation. It receives its own business-to-business subscription and integration fees and pays cloud, security and contractor costs; it does not hold, exchange or transmit customer assets.

This example is illustrative only. Bridge may request additional evidence after its risk review.

Address and identity evidence: [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide)

Formation, ownership and company records: [Formation, Ownership and Company Records Evidence Guide](/guides/getting-started/complete-business-verification-kyb/formation-ownership-and-company-records-evidence-guide)

Financial, tax, regulatory and request for information evidence: [Financial, Tax, Regulatory and Special RFI Evidence Guide](/guides/getting-started/complete-business-verification-kyb/financial-tax-regulatory-and-special-request-for-information-evidence-guide)

Timing depends on document completeness and any follow-up requests. No review period is guaranteed.


# Business Verification Preparation Guide for British Virgin Islands Entities

A practical pre-flight guide for British Virgin Islands Business Companies onboarding to Lisk

{% hint style="warning" %}
**Important**: This guide covers a typical British Virgin Islands Business Company limited by shares and supplements Lisk's general business verification guide. Other structures need different evidence. Reviews are risk-based, so Bridge may request additional or replacement documents.
{% endhint %}

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

[Complete Business Verification](/guides/getting-started/complete-business-verification-kyb): the full Lisk verification walkthrough.

[Business Verification by Entity Type and Jurisdiction](/guides/getting-started/kyb-by-entity-type-and-jurisdiction): broader entity and jurisdiction guidance.

## **What is different for British Virgin Islands companies?**

* Every British Virgin Islands company has a physical registered office and licensed registered agent in the British Virgin Islands. The agent's office may be the correct registered address, but it does not prove where the business operates.
* Contact the registered agent early for current copies of the Register of Members and Register of Directors; request certification if available or required.
* [Under British Virgin Islands rules](https://www.bvifsc.vg/sites/default/files/revised_bo_guidelines_final_version_for_publication_02.01.26_0.pdf), a beneficial owner includes a natural person who directly or indirectly owns or controls 10% or more, can appoint or remove a majority of the board, or otherwise controls management. If none is identified after reasonable efforts, a senior managing official is recorded. [For the Lisk/Bridge flow](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), verify every ultimate beneficial owner holding 25% or more, submit the complete ownership structure, and follow the people requested in the form.
* Layered ownership must be traceable through every intermediary entity to the natural persons behind the structure; a Register of Members showing a corporate shareholder is not enough on its own.
* [Bridge currently classifies the British Virgin Islands as high risk](https://apidocs.bridge.xyz/platform/customers/compliance/supported-countries-list), so additional due diligence applies. Bridge may request more address, business-activity, source of funds, or regulatory evidence.

## **Prepare before you start**

### **Company and business**

* Legal entity name, trade names, British Virgin Islands Company Number shown on the [Certificate of Incorporation](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation), incorporation date, registered office and agent, and principal operating address.
* Certificate of Incorporation and the latest Memorandum and Articles of Association.
* A clear business description, website or product information, intended account use, expected volumes, annual revenue, and source of funds.
* [Current Register of Members and Register of Directors](https://www.bvifsc.vg/products-services/corporate-structures), certified by the registered agent if available or requested.

### **People and ownership**

* Personal information and government identity document for every individual the onboarding form asks you to verify, including every ultimate beneficial owner holding 25% or more.
* Identify at least one Control Person, such as a director or executive with significant responsibility. The signer must be authorized to act for the company. One person may fill both roles, but a Control Person is not automatically an ultimate beneficial owner.
* For corporate shareholders or layered structures: a signed and dated ownership chart showing every intermediary entity, ownership percentage, and the natural persons behind the chain.
* Current ownership evidence for each intermediary entity. The complete pack should account for 100% of the ownership chain. If a shareholders' agreement is requested but none exists, use [Declaration of No Shareholders’ Agreement - Guide and Template](https://docs.google.com/document/d/16QTPOmVq2XZtBIOATBF49l3mBbyVNnKmwS9adgWOaTA/edit).

### **Conditional evidence to keep ready**

* [Operating-address evidence](https://apidocs.bridge.xyz/platform/customers/compliance/poa), if the principal operating address requires verification.
* Proof of nature of business when the website or public information is limited. A cover sheet must be accompanied by records such as contracts, invoices, receipts, product material, or partner agreements. Use [Proof of Nature of Business - Evidence Guide and Cover Sheet](https://docs.google.com/document/d/1CK5i-fW4aklsGvfGyIIYYvxxtYgavgQSujayzPkSi2g/edit) to organize the submission.
* If requested: a Certificate of Good Standing, Certificate of Incumbency from the registered agent, an issued share certificate, or relevant nominee and trust records. These support, but do not replace, the Register of Members or Register of Directors.
* For regulated activity, prepare any current license or virtual asset service provider registration issued by the British Virgin Islands Financial Services Commission, anti-money laundering materials, and a description of how funds move through the business. For virtual-asset activity, explain whether the company exchanges, transfers, safeguards, administers, issues, or provides financial services involving virtual assets for customers or any other third party. This is what “provided for another person” means. Activity conducted only for the company's own treasury is different from a service performed on behalf of someone else. This distinction describes the activity; it does not establish a legal exemption or guarantee eligibility. Bridge will assess whether the intended use is eligible under its own onboarding criteria. See the [British Virgin Islands Financial Services Commission's explanation of the virtual asset service provider framework](https://www.bvifsc.vg/news/industry-updates/virtual-assets-service-providers-act-2022).

## **Address evidence for remote British Virgin Islands companies**

The registered address and principal operating address can be the same when the company genuinely operates from its registered address. If the company uses its British Virgin Islands registered agent's office only for legal registration, use that address only as the registered address, enter the actual operating location as the principal operating address, and follow the route below.

| **Situation**                             | **What to enter**                                                                                                                                                                                                                                                                                | **What to prepare**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Separate physical office or workspace** | Keep the British Virgin Islands registered agent's office as the registered address. Enter the actual office or workspace as the principal operating address.                                                                                                                                    | Evidence in the applying company's name: a bank statement, utility bill, or government letter issued within the last 90 days, or a current office lease. It must show a physical operating address, not a post office box or virtual office.                                                                                                                                                                                                                                                                                                                                                                     |
| **Fully remote company**                  | Keep the British Virgin Islands registered agent's office as the registered address. When Lisk offers the remote-company route, enter the supported residential address where an eligible ultimate beneficial owner holding 25% or more operates the company as the principal operating address. | Upload accepted residential proof for that ultimate beneficial owner. A bank statement, utility bill, government-issued letter, or government-issued identity document must have been issued within the last 90 days; a residential lease may be older if it is current. Use this route only after the Lisk flow or Lisk Support confirms that Bridge has enabled it for your application. [Bridge's public proof-of-address requirements](https://apidocs.bridge.xyz/platform/customers/compliance/poa) do not provide a general exception for ordinary remote companies. Final acceptance remains with Bridge. |

If no individual owns 25% or more: provide the standard ownership information. Do not use a non-owner Control Person's residential proof for the operating address unless Lisk confirms that Bridge has approved an exception for the application.

## **British Virgin Islands ownership records and Lisk roles**

| **Role**                      | **Meaning**                                                                                                                                                                                                                                                                                                                                                                                                         | **What to do**                                                                                                                                                                         |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ultimate beneficial owner** | Under British Virgin Islands rules, a beneficial owner includes a natural person who directly or indirectly owns or controls 10% or more, can appoint or remove a majority of the board, or otherwise controls management. If none is identified after reasonable efforts, a senior managing official is recorded. For this Lisk/Bridge flow, verify every individual who owns 25% or more, directly or indirectly. | Submit the complete ownership structure, follow the people requested in the form, and use only an eligible ultimate beneficial owner holding 25% or more for the remote-company route. |
| **Control Person**            | A director or executive with significant responsibility for the company. This person may or may not be an ultimate beneficial owner.                                                                                                                                                                                                                                                                                | Identify at least one. A non-owner Control Person is not eligible for the 25%-owner address option described here; a different route requires Bridge's approval.                       |

Ownership attestation: A Control Person can confirm the disclosed ownership structure using the [checkbox in Bridge's hosted flow](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), when that option is available for the application. This may satisfy the ownership-evidence requirement; it does not replace disclosure or identity checks for the required people, and Bridge may request documents. If separate confirmation of the Control Person's role is requested, use [Control Person Attestation Form - Guide and Template](https://docs.google.com/document/d/1_filkvAQGqBULv2D3PcqHXGoH-g5YJdFe9wn0j0QlzY/edit).

## **Common British Virgin Islands follow-ups**

| **Follow-up**                           | **Why it happens**                                                                                                                                                    | **Prepare this**                                                                                                                                                                                                                        |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Operating address**                   | The registered agent's office proves the legal registered address, not where the business operates.                                                                   | The correct company-level evidence or the conditional remote-company route described above.                                                                                                                                             |
| **Ownership and directors**             | The Register of Members shows a corporate shareholder, the full natural-person chain is unclear, or the records are not current.                                      | Current Register of Members and Register of Directors, a signed ownership chart, and supporting records for each intermediary entity.                                                                                                   |
| **Source of funds**                     | The source, legal relationship, or movement of funds is unclear.                                                                                                      | Evidence matching the stated source of funds. For example, if a parent funds the company, evidence may include a signed funding letter and the relevant grant, equity, or loan documents.                                               |
| **Nature of business**                  | The website or public information does not prove the stated activity.                                                                                                 | Contracts, invoices, receipts, product information, licenses, or partner agreements, organized with the cover sheet.                                                                                                                    |
| **Regulated or virtual-asset activity** | It is unclear whether the company provides a virtual-asset service for another person or otherwise conducts regulated activity in or from the British Virgin Islands. | State the exact activities and provide any applicable virtual asset service provider registration or other Financial Services Commission license, anti-money laundering material, funds-flow details, and regulated-partner agreements. |

## **Fictional example**

NovaChain Labs Ltd is a fictional British Virgin Islands Business Company that provides Web3 infrastructure and business-to-business software-as-a-service integrations. Its preparation pack includes the Certificate of Incorporation, current Memorandum and Articles, Register of Members, Register of Directors, and a signed ownership chart. Maya Chen owns 60% directly. Orbit Holdings owns 40%; Orbit is owned 75% by Luis Romero and 25% by Ava Singh, producing ultimate ownership of 60%, 30% and 10%. Maya and Luis are the ultimate beneficial owners holding 25% or more for the Lisk flow. Maya is also chief executive officer, director and Control Person.

The registered agent’s office remains the registered address. If NovaChain has a separate office, it prepares current company-level address evidence. If it is fully remote and Lisk offers the remote-company route, it may use recent residential proof for Maya, mapped to her as the eligible 60% ultimate beneficial owner. It also prepares the requested person identity document and address evidence, an executed software-as-a-service contract with a recent invoice and receipt, and a clear account-purpose and source-of-funds explanation. It receives its own business-to-business subscription and integration fees and pays cloud, security and contractor costs; it does not hold, exchange or transmit customer assets.

This example is illustrative only. Bridge may request additional evidence after its risk review.

Address and identity evidence: [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide)

Formation, ownership and company records: [Formation, Ownership and Company Records Evidence Guide](/guides/getting-started/complete-business-verification-kyb/formation-ownership-and-company-records-evidence-guide)

Financial, tax, regulatory and request for information evidence: [Financial, Tax, Regulatory and Special RFI Evidence Guide](/guides/getting-started/complete-business-verification-kyb/financial-tax-regulatory-and-special-request-for-information-evidence-guide)

Timing: British Virgin Islands reviews may require additional due diligence and follow-up requests. Actual timing varies and is not guaranteed.


# Business Verification Preparation Guide for United States Entities

A practical pre-flight guide for United States limited liability companies and corporations onboarding to Lisk

{% hint style="warning" %}
**Important**: This guide covers typical United States limited liability companies and corporations and supplements Lisk's general business verification guide. Other structures need different evidence. Reviews are risk-based, so Bridge may request additional or replacement documents.
{% endhint %}

{% hint style="info" %}
**Service-provider and data-handling notice**: Lisk provides the Platform interface and customer support. Bridge is the current regulated service provider. Bridge performs business and identity verification under its own compliance program, directly or through an identity verification provider it engages. Bridge makes the verification decision and may request additional evidence. Lisk collects information and documents submitted through the Platform, or sent in response to a request for information, for transmission to Bridge and may apply its own platform risk checks, but Lisk Support does not approve evidence on Bridge's behalf. Submit sensitive evidence only through the secure submission flow provided for your case in the Platform, by Bridge, or by the identity verification provider engaged by Bridge, or through the channel named in a request for information. If the route is missing or unclear, ask Lisk Support for instructions before sending documents. See [Bridge's business onboarding requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/overview) and [Lisk's Terms of Service](https://lisk.com/legal/terms/), [Privacy Policy](https://lisk.com/legal/privacy/), and [Partner Terms](https://lisk.com/legal/partner-terms/).
{% endhint %}

[Complete Business Verification](/guides/getting-started/complete-business-verification-kyb): the full Lisk verification walkthrough.

[Business Verification by Entity Type and Jurisdiction](/guides/getting-started/kyb-by-entity-type-and-jurisdiction): broader entity and jurisdiction guidance.

## **What is different for United States companies?**

* Use the legal name exactly as shown in state and Internal Revenue Service records and enter the [Employer Identification Number](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/identification). If Lisk or Bridge requests proof, prepare an official Internal Revenue Service confirmation document.
* [Formation records depend on entity type and state](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation). Corporations usually provide Articles or a Certificate of Incorporation; limited liability companies usually provide Articles of Organization or a Certificate of Formation.
* Formation records usually do not prove current ownership. Prepare a capitalization table or shareholder ledger for a corporation, or an operating agreement or membership ledger for a limited liability company.
* [The Lisk/Bridge flow identifies](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership) every individual ultimate beneficial owner holding 25% or more and at least one Control Person. Layered ownership must be traceable through every intermediary entity.
* Bridge currently does not support a [principal operating address in New York](https://apidocs.bridge.xyz/platform/customers/compliance/supported-countries-list). A company formed in New York may still qualify if it actually operates from a supported state and can prove that address.

## **Prepare before you start**

### **Company and business**

* Legal entity name; any trade name or “doing business as” name, meaning a public-facing name that differs from the exact legal entity name; Employer Identification Number; state of formation; entity type; formation date; registered address; and principal operating address. [Bridge's business formation document requirements](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/formation) use the same term.
* One state-filed formation record appropriate to the entity: Articles or a Certificate of Incorporation for a corporation, or Articles of Organization or a Certificate of Formation for a limited liability company.
* A clear business description, industry category, website or product information, intended account use, and source of funds. If requested in the Lisk flow, also provide estimated annual revenue and expected monthly transaction volume.
* Current ownership evidence appropriate to the entity: a capitalization table, shareholder ledger, or shareholders' agreement for a corporation; or an operating agreement, membership ledger, or member schedule for a limited liability company.

### **People and ownership**

* Personal information and government identity document for every individual the onboarding form asks you to verify, including every ultimate beneficial owner holding 25% or more.
* Identify at least one Control Person, such as a director or executive with significant responsibility. The signer must be authorized to act for the company. One person may fill both roles, but a Control Person is not automatically an ultimate beneficial owner.
* For entity shareholders or layered structures: a signed and dated ownership chart showing every intermediary entity, ownership percentage, and the natural persons behind the chain.
* Current ownership evidence for each intermediary entity. The complete pack should account for 100% of the ownership chain. If a shareholders' agreement is requested but none exists, use [Declaration of No Shareholders’ Agreement - Guide and Template](https://docs.google.com/document/d/16QTPOmVq2XZtBIOATBF49l3mBbyVNnKmwS9adgWOaTA/edit).

### **Conditional evidence to keep ready**

* [Operating-address evidence](https://apidocs.bridge.xyz/platform/customers/compliance/poa), if the principal operating address requires verification.
* Proof of nature of business when the website or public information is limited. A cover sheet must be accompanied by records such as contracts, invoices, receipts, product material, or partner agreements. Use [Proof of Nature of Business - Evidence Guide and Cover Sheet](https://docs.google.com/document/d/1CK5i-fW4aklsGvfGyIIYYvxxtYgavgQSujayzPkSi2g/edit) to organize the submission.
* If Lisk or Bridge requests Employer Identification Number proof, provide an [Internal Revenue Service Entity transcript](https://www.irs.gov/businesses/get-a-business-tax-transcript), digital CP575 notice, original CP575-series notice, or Letter 147C. [Form SS-4](https://www.irs.gov/forms-pubs/about-form-ss-4) is only the Employer Identification Number application and does not prove that an Employer Identification Number was assigned. If requested, also prepare a current Certificate of Good Standing, trade-name evidence, or foreign-qualification records.
* Disclose [high-risk activities](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/highrisk) and customer-money transmission in the Lisk flow. If requested, prepare applicable licensing or registration evidence, anti-money laundering or compliance-screening information, source-of-funds evidence, and a funds-flow explanation. [Licensing does not guarantee eligibility](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/highrisk). Bridge prohibits investment or credit services, digital-asset exchange services, money services, and money-transmission services when provided to third parties through Bridge.

## **Address evidence for United States companies**

The registered address and principal operating address can be the same when the company genuinely operates there. If the company uses a registered agent's address only for legal registration, enter that address only as the registered address and enter the actual operating location as the principal operating address. A post office box or virtual address, such as a virtual office used only for mail, does not show where the business actually operates. If you enter one as the principal operating address, expect a request for proof of address. Provide documentation showing where the company actually operates, or correct the application to the actual physical operating address.

| **Situation**                             | **What to enter**                                                                                                                                                                                                                                                                         | **What to prepare**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Separate physical office or workspace** | Enter the entity's actual registered address in the registered-address field. Enter the actual office or workspace as the principal operating address.                                                                                                                                    | Evidence in the applying company's name: a bank statement, utility bill, or government letter issued within the last 90 days, or a current office lease. It must show a physical operating address, not a post office box or virtual office.                                                                                                                                                                                                                                                                                                                                                                     |
| **Fully remote company**                  | Enter the entity's actual registered address in the registered-address field. When Lisk offers the remote-company route, enter the supported residential address where an eligible ultimate beneficial owner holding 25% or more operates the company as the principal operating address. | Upload accepted residential proof for that ultimate beneficial owner. A bank statement, utility bill, government-issued letter, or government-issued identity document must have been issued within the last 90 days; a residential lease may be older if it is current. Use this route only after the Lisk flow or Lisk Support confirms that Bridge has enabled it for your application. [Bridge's public proof-of-address requirements](https://apidocs.bridge.xyz/platform/customers/compliance/poa) do not provide a general exception for ordinary remote companies. Final acceptance remains with Bridge. |

If no individual owns 25% or more: provide the standard ownership information. Do not use a non-owner Control Person's residential proof for the operating address unless Lisk confirms that Bridge has approved an exception for the application.

## **United States ownership records and Lisk roles**

| **Role**                      | **Meaning**                                                                                                                                              | **What to do**                                                                                                                                                                                    |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ultimate beneficial owner** | An individual who owns 25% or more, directly or through other entities. Ownership and control are different roles, but the same person may satisfy both. | Disclose every qualifying ultimate beneficial owner, complete the requested identity checks, and use only an eligible ultimate beneficial owner holding 25% or more for the remote-company route. |
| **Control Person**            | A director or executive with significant responsibility for the company. This person may or may not be an ultimate beneficial owner.                     | Identify at least one. A non-owner Control Person is not eligible for the 25%-owner address option described here; a different route requires Bridge's approval.                                  |

Ownership attestation: A Control Person can confirm the disclosed ownership structure using the [checkbox in Bridge's hosted flow](https://apidocs.bridge.xyz/platform/customers/compliance/businesses/ownership), when that option is available for the application. This may satisfy the ownership-evidence requirement; it does not replace disclosure or identity checks for the required people, and Bridge may request documents. If separate confirmation of the Control Person's role is requested, use [Control Person Attestation Form - Guide and Template](https://docs.google.com/document/d/1_filkvAQGqBULv2D3PcqHXGoH-g5YJdFe9wn0j0QlzY/edit).

## **Common United States follow-ups**

| **Follow-up**                                     | **Why it happens**                                                                                                                                                                                                       | **Prepare this**                                                                                                                                                                                                                             |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Operating address**                             | A registered agent, virtual office, or post office box address does not prove where the business operates.                                                                                                               | The correct company-level evidence or the conditional remote-company route described above.                                                                                                                                                  |
| **Employer Identification Number and legal name** | The Employer Identification Number cannot be verified automatically or the legal name differs across Internal Revenue Service and state records.                                                                         | An Internal Revenue Service Entity transcript, digital CP575 notice, original CP575-series notice, or Letter 147C, plus any requested legal name-change or state formation evidence.                                                         |
| **Ownership structure**                           | Formation records do not show current owners, or an entity shareholder hides the natural-person chain.                                                                                                                   | A current capitalization table, ledger, operating agreement, or membership record, plus a signed ownership chart and intermediary records.                                                                                                   |
| **Nature of business**                            | The website or public information does not prove the stated activity.                                                                                                                                                    | Contracts, invoices, receipts, product information, licenses, or partner agreements, organized with the cover sheet.                                                                                                                         |
| **High-risk or customer-money activity**          | The company reports money services, lending or banking, foreign exchange or virtual-currency brokerage, over-the-counter activity, holding client funds, third-party payment processing, or customer-money transmission. | Explain the use case and compliance screening. If requested, provide licenses or registrations, anti-money laundering materials, funds-flow details, and partner agreements. Confirm eligibility against Bridge's prohibited-activity rules. |

## **Fictional example**

NovaChain Labs Inc. is a fictional Delaware corporation that provides Web3 infrastructure and business-to-business software-as-a-service integrations. Its preparation pack includes the Certificate of Incorporation, bylaws, Employer Identification Number, current shareholder ledger, current director and officer records, and a signed ownership chart. Maya Chen owns 60% directly. Orbit Holdings owns 40%; Orbit is owned 75% by Luis Romero and 25% by Ava Singh, producing ultimate ownership of 60%, 30% and 10%. Maya and Luis are the ultimate beneficial owners holding 25% or more. Maya is also chief executive officer, director and Control Person.

The registered agent’s address remains separate from the principal operating address. If NovaChain has a separate office, it prepares current company-level address evidence. If it is fully remote and Lisk offers the remote-company route, it may use recent residential proof for Maya, mapped to her as the eligible 60% ultimate beneficial owner. It also prepares the requested person identity document and address evidence, an executed software-as-a-service contract with a recent invoice and receipt, and a clear account-purpose and source-of-funds explanation. It receives its own business-to-business subscription and integration fees and pays cloud, security and contractor costs; it does not hold, exchange or transmit customer assets.

This example is illustrative only. Bridge may request additional evidence after its risk review.

Address and identity evidence: [Proof of Address and Identity Evidence Guide](/guides/getting-started/complete-business-verification-kyb/proof-of-address-and-identity-evidence-guide)

Formation, ownership and company records: [Formation, Ownership and Company Records Evidence Guide](/guides/getting-started/complete-business-verification-kyb/formation-ownership-and-company-records-evidence-guide)

Financial, tax, regulatory and request for information evidence: [Financial, Tax, Regulatory and Special RFI Evidence Guide](/guides/getting-started/complete-business-verification-kyb/financial-tax-regulatory-and-special-request-for-information-evidence-guide)

Timing varies by case and may include follow-up requests.


# Workspace Management

Guides for managing your workspace, accounts, contacts, and members.


# Create an Account

How to add a new account to your workspace.

An **account** in Lisk is a shared financial account inside your workspace - it holds a balance and is where money moves in and out. A workspace can have several accounts (for example, one for team budget and one for taxes), each with its own name, icon, and set of approvers.

When you create an account, you choose who can use it and how many people must approve each transaction before it goes through.

### Before you start

* You need permission to create accounts. This is available to workspace **Admins** and the **Owner**. If you don't see an **Add account** button, ask an admin to create the account for you.
* The people you want to add as approvers should already be members of the workspace. To add someone new first, see Invite members to a workspace.
* Anyone you want to set as an **Approver/Viewer** must have finished setting up the **Lisk mobile app** - approvers sign transactions on their phone.

### Steps

1. Go to the **Accounts** page in your workspace.
2. Click **Add account**.
3. On the **Create account** step, enter a **Name** for the account (for example, "Team Budget"). You can also click the icon next to the name field to pick an emoji and color, and optionally choose a **Department**.\
   In the Lisk app, a department is an organizational subdivision within a workspace — a way to group your workspace by team or business unit (e.g. Finance, Marketing, Operations) so accounts and people are easier to organize and report on.
4. Click **Next** to go to the **Members & approvals** step.
5. Use the **Add member** search box to find a workspace member by name or email, and select them to add them to the account.
6. For each person you added, open the role dropdown and choose:
   * **Approver** - can initiate and approve transactions from this account.
   * **Viewer** - can see the account but can't approve transactions.
7. Set **Approvals required** - the number of approvers who must approve before a transaction is executed (for example, 2 out of 3 approvers).
8. Click **Create account**.

### What to expect

The new account appears in your workspace's **Accounts** list. You'll need to add funds before you can send from it - see [Deposit Funds](/guides/transactions-and-payments/deposit-funds).

The **Approvals required** number you set applies to every transaction from this account: whenever someone sends, transfers, or withdraws, that many approvers must approve it (in the Lisk mobile app) before it goes through. Choose a number that fits how your team works - a higher number is more secure but needs more people to sign off.

### Troubleshooting

* **I don't see the Add account button** → Creating accounts is limited to admins and the owner. Ask an admin to create it.
* **A member is greyed out when I try to add them as an approver** → That person hasn't set up the Lisk mobile app yet, so they can't sign transactions. Ask them to download and log in to the mobile app, then add them.
* **I can't finish the Members & approvals step** → You need at least one **Approver** on the account, and the approvals-required number must be at least 1. Make sure everyone you added has a role assigned.

### Related

* [Invite Members](/guides/workspace-management/invite-members)
* [Add a Contact](/guides/workspace-management/add-a-contact)
* [Transfer Funds between Accounts](/guides/transactions-and-payments/transfer-funds-between-accounts)


# Invite Members

How to invite members to your workspace.

Inviting members lets your coworkers join your workspace so they can view accounts, be added as approvers, and help manage transactions. You invite people by email, and they get access once they accept and finish setting up their account.

### Before you start

* You need permission to invite members. This is available to workspace **Admins** and the **Owner**. If you don't see an **Invite** button, ask an admin to send the invitations.
* Have the email addresses of the people you want to invite ready.

### Steps

1. Click the workspace on the top left (, or your **avatar** in the top right corner), then select **Settings**.
2. In the Settings sidebar, under **Workspace**, select **Members**.
3. Click **Invite**.
4. In the **Invite new members** dialog, type an **Email address** and click **Add**.
5. Repeat step 4 to add as many people as you need - each added email appears in a list below, and you can remove any before sending.
6. Click the invite button (it shows how many people you're inviting, for example **Invite 3 people**).

### What to expect

Each person receives an email invitation to join the workspace. You can track who hasn't accepted yet on the **Invited** tab of the Members page.

New members join with the standard member level of access. To give someone more access or assign them to specific accounts, manage their role and account assignments from the Members list after they've joined.

### Troubleshooting

* **I don't see the Invite button or the Members page** → Inviting members is limited to admins and the owner. Ask an admin to send the invitation.
* **"This email has already been added"** → That address is already in the list of people you're about to invite. Check the list below the field.
* **The invite won't send / the email looks wrong** → Make sure each address is a valid email. You need at least one valid address added to the list before you can send.
* **Someone hasn't received their invite** → Check the **Invited** tab to confirm the invitation was sent, and ask them to check their spam folder. Alternatively, you can press the three dots on the invite and hit “Resend invite” to resend it.

### Related

* [Create an Account](/guides/workspace-management/create-an-account)
* [Add a Contact](/guides/workspace-management/add-a-contact)


# Add a Contact

How to add a contact to your workspace.

A **contact** is a saved recipient you pay from your workspace - a vendor, a supplier, or anyone you send money to. Saving a contact stores their name and payment details (a bank account, a crypto wallet, or both) so you don't have to re-enter them every time you send a payment.

Contacts are shared across your whole workspace: once you add one, other members can pay them too.

### Before you start

* Any workspace member can add a contact. Editing or deleting a contact is limited to admins.
* Have the recipient's payment details ready - their bank account details (SEPA or ACH/wire) or their crypto wallet address.

### Steps

1. Go to the **Contacts** page in your workspace.
2. Click **Add contact**.
3. On the first step, enter the contact's **Full name**. You can also add an optional **Nickname** and a **Photo**. Click **Next**.
4. Choose a payment method under **Select method**:

   * **SEPA bank account** - European bank details (IBAN and BIC).
   * **ACH/wire bank account** - US bank details.
   * **Crypto wallet** - a wallet address.

   Fill in the details for the method you picked. Click **Next**.
5. (Optional) To save a second payment method for the same contact, click **Add another method** and fill in its details.
6. On the final step, add any optional details such as **email**, **phone**, and **address**, then click **Add contact**. (If you saved a bank account, an address is required.)

### What to expect

The contact appears on your **Contacts** page and is available to everyone in the workspace. The next time you send a payment, you can pick this contact and one of their saved payment methods instead of typing the details again - see [Send Money](/guides/transactions-and-payments/send-money).

You can also add a new contact on the fly while sending a payment, without leaving the send flow.

### Troubleshooting

* **I can't finish adding the contact** → A contact needs at least one payment method. Make sure you've completed the payment-method step. If you added a bank account, you'll also need to fill in an address on the final step.
* **My bank details are rejected** → Double-check the IBAN (for SEPA) or the account and routing numbers (for ACH/wire). The form checks these for the correct format.
* **I can't edit or remove a contact** → Adding contacts is open to all members, but changing or deleting them is limited to admins. Ask an admin if you need a contact updated.

### Related

* [Send Money](/guides/transactions-and-payments/send-money)
* [Create an Account](/guides/workspace-management/create-an-account)
* [Invite Members](/guides/workspace-management/invite-members)


# Transactions and Payments

Guides for moving money - sending, transferring, depositing, and withdrawing.


# Deposit Funds

How to add money to your workspace.

You add funds to your workspace with a **deposit**. Deposits happen at the workspace level, and the funds land in your workspace's **Main Account**. Lisk gives you the details you need to send money in from an outside source - either a **bank transfer** or a **crypto transfer**. You then make that transfer from your bank or wallet, and the funds arrive in your workspace.

### Before you start

* Depositing is limited to the workspace **Owner and Admins**. If you don't see a **Deposit** button, ask an admin.
* Deposits need your workspace to have completed **business verification (KYB)** first.
* For a bank transfer, have access to the bank account you'll be sending from. For a crypto transfer, have your wallet ready.

### Steps

1. Click **Deposit** (available from your dashboard and the Transactions page).
2. In the **Deposit** dialog, choose a method:
   * **ACH/wire bank transfer** - for US bank transfers.
   * **SEPA bank transfer** - for European bank transfers.
   * **Crypto transfer** - to send crypto to your workspace wallet.
3. Lisk shows the details you need:
   * For a **bank transfer**, you'll see the receiving bank details to use for your transfer.
   * For a **crypto transfer**, you'll see the **wallet address** to send to. Choose the **asset** first, then use the copy button to copy the address.
4. Make the transfer from your own bank or wallet using those details.
5. Click **Done** to close the dialog.

### What to expect

When you send crypto, only send the **asset shown, on the network shown** (the deposit screen states this, for example "Only send USDC on the Base network"). Sending a different asset or using a different network can result in lost funds.

Bank transfers take as long as your bank normally needs to process a transfer; crypto transfers usually arrive after the network confirms them, usually nearly instantly. Your workspace balance updates once the funds are received - you can check the **Transactions** page for incoming deposits.

### Troubleshooting

* **The deposit screen asks me to complete verification** → Deposits require your workspace's **business verification (KYB)** to be approved. Follow the prompt to start or finish verification, or ask an admin to complete it.
* **I don't see the Deposit button** → Depositing is limited to the workspace Owner and Admins. If you're a member, ask an admin.
* **I sent the wrong asset or used the wrong network** → Only send the exact asset and network shown on the deposit screen. If you're unsure, contact support before sending.
* **"This deposit method isn't available for this account yet"** → That method hasn't been set up for your workspace. Try another method or ask an admin.

### Related

* [Withdraw Funds](/guides/transactions-and-payments/withdraw-funds)
* [Send Money](/guides/transactions-and-payments/send-money)
* [Create an Account](/guides/workspace-management/create-an-account)


# Send Money

How to send money in Lisk.

Sending a payment moves funds from one of your workspace accounts to a recipient (a **contact**) - for example, paying a vendor or supplier. You start the payment on the web, and it's approved and signed in the **Lisk mobile app**.

### Before you start

* You must be an **approver** on the account you're paying from.
* The account you're sending from needs enough balance to cover the amount plus the network fee.
* The recipient should be saved as a **contact** with a payment method. You can also add a new contact during the send flow. See [Add a Contact](/guides/workspace-management/add-a-contact).
* Have the **Lisk mobile app** ready - payments are approved there.&#x20;

### Steps

1. Click **Send** (available from your dashboard, the account page, and the Transactions page).
2. On the **Send transaction** form:
   * **From** - choose the account to pay from.
   * **Recipient** - choose a contact (or add a new one).
   * **Method** - choose which of the contact's saved payment methods to pay to (bank account or crypto wallet).
   * **Send as** - if you're paying to a crypto wallet, choose which token to send.
   * **Amount** - enter the amount. You can tap **Max** to use the full balance. The account's balance is shown for reference.
   * **Notes** - optionally add a short note.
3. Click **Next**.
4. On **Confirm transaction**, review the details. A badge shows how many approvals are required for this account. Click **Confirm**.
5. A screen titled **Waiting for approval via mobile app** appears with a **QR code**. Scan it with your phone to open the request directly in the Lisk mobile app.

Confirming on the web is only the first step - the payment isn't actually sent until you approve it on your phone.

### Approve the payment on your phone

1. After you confirm on the web, you'll see the **Waiting for approval via mobile app** screen with a **QR code**. Scan it with your phone to open the request directly.
2. On your phone you'll get a **push notification** that an approval was requested. You can also find it on the **Home** screen under **Pending transactions** (tap **View all**), or in your **Notifications**.
3. Tap the request to open the payment details. Review **From**, **To**, **Amount**, the estimated fee, and any **Notes**.
4. At the bottom, tap **✓ Approve**. (If you'd rather not approve it right now without blocking it for others, tap **Skip** instead.)
5. In the **Approve transaction** sheet, review the details and tap **Confirm**.
6. Confirm with your **passkey** - your phone prompts for **Face ID, Touch ID, or your device passcode**.
7. You'll see **Transaction approved**. If the account needs more than one approval, it stays pending until enough approvers have signed. Once the required number is reached, you'll see **Transaction submitted** and the payment is sent.

### What to expect

Starting the payment on the web counts as the first approval, but the money isn't sent yet - it moves only once the payment is fully approved in the Lisk mobile app.

If the account requires more than one approver, each other approver repeats the approval steps above in their own Lisk mobile app. The screen shows how many approvals are still needed. Once enough approvals are collected, the transaction is sent and you'll see **Transaction submitted**. You can follow its status on the **Transactions** page at any time - you don't need to keep the send window open.

A pending request **expires after 72 hours** if it isn't fully approved by then. If that happens, just start the payment again.

### Troubleshooting

* **I don't see the Send button** → You may not have permission to create transactions, or you're not an approver on any account. Ask an admin.
* **My amount won't go through / balance warning** → The amount plus the network fee is more than the account's balance. Lower the amount or add funds first - see [Deposit Funds](/guides/transactions-and-payments/deposit-funds).
* **"Contact has an invalid wallet address"** → The crypto wallet saved for that contact isn't a valid address. Update the contact's payment method and try again.
* **The transaction is still waiting** → It needs more approvals in the Lisk mobile app. It completes automatically once the required approvers have approved it.

### Related

* [Transfer Funds between Accounts](/guides/transactions-and-payments/transfer-funds-between-accounts)
* [Withdraw Funds](/guides/transactions-and-payments/withdraw-funds)
* [Add a Contact](/guides/workspace-management/add-a-contact)


# Transfer Funds between Accounts

How to internally transfer funds between two accounts of your workspace.

A **transfer** moves funds from one account in your workspace to another - for example, moving money from your main account into a taxes account. Unlike a payment, both the source and destination are your own workspace accounts. Like other transactions, a transfer is approved and signed in the **Lisk mobile app**.

### Before you start

* You need permission to create transactions, and you must be an **approver** on the account you're transferring from.
* Your workspace needs at least two accounts. To create one, see Create an account.
* The source account needs enough balance to cover the amount plus the network fee.
* Have the **Lisk mobile app** ready - transfers are approved there.&#x20;

### Steps

1. Click **Transfer** (available from your dashboard, the Accounts page, and the account page).
2. On the **Transfer** form:
   * **From** - choose the account to move money out of.
   * **To** - choose the account to move money into. (You can't pick the same account for both.)
   * **Amount** - enter the amount. You can tap **Max** to use the full balance. The source balance is shown for reference.
3. Click **Next**.
4. On **Confirm transaction**, review the details. A badge shows how many approvals are required. Click **Confirm**.
5. A screen titled **Waiting for approval via mobile app** appears with a **QR code**. Scan it with your phone to open the request directly in the Lisk mobile app.

Confirming on the web is only the first step - the transfer isn't actually sent until you approve it on your phone.

### Approve the transfer on your phone

1. After you confirm on the web, you'll see the **Waiting for approval via mobile app** screen with a **QR code**. Scan it with your phone to open the request directly.
2. On your phone you'll get a **push notification** that an approval was requested. You can also find it on the **Home** screen under **Pending transactions** (tap **View all**), or in your **Notifications**.
3. Tap the request to open the transfer details. Review **From**, **To**, **Amount**, the estimated fee, and any **Notes**.
4. At the bottom, tap **✓ Approve**. (If you'd rather not approve it right now without blocking it for others, tap **Skip** instead.)
5. In the **Approve transaction** sheet, review the details and tap **Confirm**.
6. Confirm with your **passkey** - your phone prompts for **Face ID, Touch ID, or your device passcode**.
7. You'll see **Transaction approved**. If the account needs more than one approval, it stays pending until enough approvers have signed. Once the required number is reached, you'll see **Transaction submitted** and the transfer is sent.

### What to expect

Starting the transfer on the web alone doesn't move the money - the funds move only once the transfer is fully approved in the Lisk mobile app.

If the source account requires more than one approver, each other approver repeats the approval steps above in their own Lisk mobile app. Once enough approvals are collected, the funds move and you'll see **Transaction submitted**. You can check its status on the **Transactions** page.

A pending request **expires after 72 hours** if it isn't fully approved by then. If that happens, just start the transfer again.

### Troubleshooting

* **I don't see the Transfer button** → You may not have permission to create transactions, or you're not an approver on any account. Ask an admin.
* **The To field is empty or won't let me pick an account** → You need at least two accounts to transfer between, and you can't send to the same account you're sending from. Create another account first.
* **My amount won't go through / balance warning** → The amount plus the network fee is more than the source account's balance. Lower the amount or add funds first - see [Deposit Funds](/guides/transactions-and-payments/deposit-funds).
* **The transfer is still waiting** → It needs more approvals in the Lisk mobile app. It completes automatically once the required approvers have approved it.

### Related

* [Send Money](/guides/transactions-and-payments/send-money)
* [Withdraw Funds](/guides/transactions-and-payments/withdraw-funds)
* [Create an Account](/guides/workspace-management/create-an-account)


# Withdraw Funds

How to withdraw funds from your workspace.

Withdrawing moves funds out of a workspace account to a **saved withdrawal method** - an external bank account or a crypto wallet you've saved. You start the withdrawal on the web, and it's approved and signed in the **Lisk mobile app**.

### Before you start

* You need permission to withdraw. If you don't see a **Withdraw** button, ask an admin.
* The account needs enough balance to cover the amount plus the network fee.
* You need at least one saved **withdrawal method**. You can add one during the withdrawal, or manage them in **Settings → Withdrawal methods**.
* Withdrawing to a bank account requires your workspace's **business verification** to be approved.
* Have the **Lisk mobile app** ready - withdrawals are approved there. You'll need it set up with a **passkey** and biometrics or a device passcode (Face ID, Touch ID, or your passcode) enabled, so you can confirm the approval.

### Steps

1. Open the account you want to withdraw from and click **Withdraw**.
2. On the **Withdraw** form:
   * **From** - choose the source account.
   * **To** - choose a saved withdrawal method. To add one now, choose **Add new withdrawal method** and fill in its details.
   * **Rail** - if you picked an ACH/wire bank method, choose how the payout is sent.
   * **Amount** - enter the amount. You can tap **Max** to use the full balance. The account balance is shown for reference.
   * **Note** - optionally add a short note.
3. Click **Next**.
4. On **Confirm withdrawal**, review the details. A badge shows how many approvals are required. Click **Confirm**.
5. A screen titled **Waiting for approval via mobile app** appears with a **QR code**. Scan it with your phone to open the request directly in the Lisk mobile app.

Confirming on the web is only the first step - the withdrawal isn't actually sent until you approve it on your phone.

### Approve the withdrawal on your phone

1. After you confirm on the web, you'll see the **Waiting for approval via mobile app** screen with a **QR code**. Scan it with your phone to open the request directly.
2. On your phone you'll get a **push notification** that an approval was requested. You can also find it on the **Home** screen under **Pending transactions** (tap **View all**), or in your **Notifications**.
3. Tap the request to open the withdrawal details. Review **From**, **To**, **Amount**, the estimated fee, and any **Notes**.
4. At the bottom, tap **✓ Approve**. (If you'd rather not approve it right now without blocking it for others, tap **Skip** instead.)
5. In the **Approve transaction** sheet, review the details and tap **Confirm**.
6. Confirm with your **passkey** - your phone prompts for **Face ID, Touch ID, or your device passcode**.
7. You'll see **Transaction approved**. If the account needs more than one approval, it stays pending until enough approvers have signed. Once the required number is reached, you'll see **Transaction submitted** and the withdrawal is sent.

### What to expect

Starting the withdrawal on the web alone doesn't complete the withdrawal - the withdrawal is sent only once it's fully approved in the Lisk mobile app.

If the account requires more than one approver, each other approver repeats the approval steps above in their own Lisk mobile app. Once enough approvals are collected, you'll see **Transaction submitted** and the withdrawal is sent.

Bank payouts take as long as the banking network needs to process them; crypto payouts usually arrive after the network confirms them. You can follow the status on the **Transactions** page.

A pending request **expires after 72 hours** if it isn't fully approved by then. If that happens, just start the withdrawal again.

### Troubleshooting

* **I don't see the Withdraw button** → You may not have permission to withdraw. Ask an admin.
* **"This withdrawal method is inactive"** → The method you selected can't be used right now. Choose an active method or add a new one.
* **My amount won't go through / balance warning** → The amount plus the network fee is more than the account's balance. Lower the amount.
* **I can't withdraw to a bank account** → Bank withdrawals require your workspace's business verification to be approved. Ask an admin to check the workspace's verification status.
* **The withdrawal is still waiting** → It needs more approvals in the Lisk mobile app. It completes automatically once the required approvers have approved it.

### Related

* [Deposit Funds](/guides/transactions-and-payments/deposit-funds)
* [Send Money](/guides/transactions-and-payments/send-money)
* [Transfer Funds between Accounts](/guides/transactions-and-payments/transfer-funds-between-accounts)


# User Settings

Guides for managing your personal user settings.


# Change Your Email Address

How to change your email address.

You can update the email address on your Lisk profile from your settings. To keep your account secure, you'll confirm the change with a code sent to your new email before it takes effect.

### Before you start

* Make sure you can access the inbox for the **new** email address, since you'll need to enter a code sent there.

### Steps

1. Select your profile picture in the top corner and choose **Settings**.
2. In the **Personal** section, open **My Profile**.
3. Next to **Email address**, select the edit button.
4. In the **Edit email address** dialog, type your new email and select **Update**.
5. On the **Enter confirmation code** screen, check your new inbox for a message with a code and enter the 6-digit code.
   * Didn't get it? Select **Resend**. The button becomes available again after a short countdown.

### What to expect

* Once you enter the correct code, the change is confirmed and the dialog closes on its own.
* Your new email address then shows on your **My Profile** page.
* Your email doesn't change until you've entered the verification code, so if you don't finish this step, your old email stays in place.

### Troubleshooting

* **"My code doesn't work."** Codes expire and can be used only once. Select **Resend** to get a new one and enter the most recent code.
* **"I didn't receive the code."** Check the spam folder for your new email address, wait a moment, then select **Resend**.
* **"The Update button is greyed out."** Make sure you've entered an email address that's different from your current one.

### Related

* [Reset Two-Factor Authentication](/guides/user-settings/reset-two-factor-authentication)


# Reset Two-Factor Authentication

How to reset the two-factor authentication (2FA) of a workspace member.

Two-factor authentication (2FA) adds a second step to signing in: a 6-digit code from an authenticator app on your phone. If you've lost access to that app, or got a new phone, you'll need your 2FA reset so you can set it up again.

You can't reset your own 2FA from your personal settings. Only the **owner** of your workspace can reset a member's 2FA. Admins can view a member's 2FA method but can't reset it. Once the owner resets it, you set up 2FA fresh the next time you log in.

### Before you start

* Know who the **owner** of your workspace is. If you're not sure, ask a workspace admin.
* Have your phone ready with an authenticator app (for example, Google Authenticator, 1Password, or Authy) so you can set up 2FA again after the reset.

### Steps

**If you need your 2FA reset**, ask your workspace owner to reset it for you.

**If you're the workspace owner** resetting 2FA for a member:

1. Select your profile picture in the top corner and choose **Settings**.
2. In the **Workspace** section, open **Members**.
3. Find the member in the list and open the actions menu (the **⋮** button) on their row.
4. Select **Reset 2FA**.
5. In the confirmation dialog, select **Reset**.

### What to expect

* After the reset, the member will be asked to set up 2FA again the next time they log in. This reset can't be undone.
* To set up 2FA again, open the Lisk app on your phone and, on the **Enable 2FA** screen, scan the QR code with your authenticator app (or enter the code shown), then continue and enter a 6-digit code to confirm.
* Once 2FA is set up again, you'll use a fresh code from your authenticator app each time you sign in.

### Troubleshooting

* **"I don't see a Reset 2FA option."** Only the workspace owner can reset another member's 2FA. Admins can view a member's 2FA method but can't reset it. If you're a member or an admin, ask the owner to do it.
* **"I'm locked out and can't reach anyone."** Contact your workspace owner or admin so they can reset your 2FA. You can review your current 2FA method under **Settings → Security**, but resets are handled by the owner.

### Related

* [Change Your Email Address](/guides/user-settings/change-your-email-address)
* [Sign Up on Lisk](/guides/getting-started/sign-up-on-lisk)


# Roles and Permissions

Guides for managing member roles and workspace ownership.


# Remove a Member from a Workspace

How to deactivate a member from your workspace.

To take away someone's access to a workspace, you **deactivate** them. A deactivated member loses access to the workspace. Use this when a person leaves the team or should no longer be able to see or act in the workspace.

### Before you start

* You must have permission to manage members (admins and the workspace Owner can).
* To deactivate someone who is an **Admin**, you must be the workspace **Owner**. Admins can deactivate members but not other admins.
* You can't deactivate yourself, and the workspace **Owner** can't be deactivated. If the owner needs to leave, transfer ownership first - see Transfer ownership of a workspace.

### Steps

1. Click the workspace on the top left(, or your **avatar** in the top right corner) to open the menu, then select **Settings**.
2. In the Settings sidebar, under **Workspace**, select **Members**.
3. Find the person in the list and click the **⋮** (more) button at the end of their row.
4. Select **Deactivate**.
5. In the confirmation dialog ("Deactivate member"), read the warning that they will lose access to the workspace, then click **Deactivate** to confirm.

### What to expect

The person is deactivated right away and loses access to the workspace. Their entry stays visible in the Members list, shown in a dimmed (deactivated) state, rather than disappearing entirely.

### Troubleshooting

* **There's no Deactivate option in the ⋮ menu** → You may not have permission, you're looking at your own row, or the person is the workspace Owner (owners can't be deactivated). To deactivate an admin, you need to be the owner.
* **You only want to reduce their access, not remove it** → Lower their role instead.
* **The owner is leaving the team** → Deactivating the owner isn't possible. Transfer ownership to someone else first, then the former owner (now an admin) can be deactivated. See [Transfer Workspace Ownership](/guides/roles-and-permissions/transfer-workspace-ownership).

### Related

* [Transfer Workspace Ownership](/guides/roles-and-permissions/transfer-workspace-ownership)


# Transfer Workspace Ownership

How to transfer ownership of your workspace to another member.

Every workspace has exactly one **Owner** - usually the person who created it. The owner has full control, including deleting the workspace, transferring ownership, and resetting another member's two-factor authentication (2FA). If you're the owner and someone else should take over, you can transfer ownership to them.

**Transferring ownership can't be undone.** Once you transfer it, you become an **Admin** and the other person becomes the Owner.

### Before you start

* You must be the current workspace **Owner**. Only the owner can transfer ownership.
* Choose an existing, active member to become the new owner.
* Be sure - this action is permanent and can't be reversed from the app.

### Steps

1. Click the workspace on the top left(, or your **avatar** in the top right corner) to open the menu, then select **Settings**.
2. In the Settings sidebar, under **Workspace**, select **Members**.
3. Find the member you want to make owner and click the **⋮** (more) button at the end of their row.
4. Select **Update role**.
5. In the **Update role** dialog, open the role dropdown and choose **Owner**.
6. Click **Confirm**.
7. A confirmation dialog appears: "Are you sure you want to transfer ownership?" It explains that the action can't be undone and that you'll lose your ownership and be downgraded to admin. To go ahead, click **Transfer**.

### What to expect

Once confirmed, the other member becomes the workspace **Owner** and you become an **Admin**. As an admin you keep full operational control, but a few owner-only abilities move to the new owner - such as deleting the workspace, transferring ownership again, and resetting another member's 2FA.

### Troubleshooting

* **Owner isn't an option in the role dropdown** → Only the current owner can transfer ownership. If you don't see **Owner** as a choice, you're not the owner of this workspace.
* **You changed your mind** → As long as you haven't clicked **Transfer** in the final confirmation dialog, nothing has changed - click **Cancel** or close the dialog. After you confirm, the transfer is permanent; the new owner would have to transfer it back to you.

### Related

* [Remove a Member from a Workspace](/guides/roles-and-permissions/remove-a-member-from-a-workspace)


# Lisk Chain

Guides related to the Lisk Chain.


# Celo Migration

### Exploring a Path to Celo

This guide explains how projects currently building or deployed on Lisk can explore a potential migration or redeployment path to Celo following our recent announcement.

Migration is open to every project and remains entirely optional. Each team should decide what makes the most sense based on its product, users, technical setup, and future plans.

The Celo team is committed to supporting projects that choose to make the move and has prepared resources to help teams get established in the Celo ecosystem.

If you think Celo is the right path for your team, here’s how to get started:

#### 1. Review your current deployment

Prepare a short overview of your project, including:

* Project name and description
* Website and socials
* Main contact
* Current deployment status on Lisk
* Smart contract addresses
* Active users, liquidity, or assets, if relevant
* Key infrastructure dependencies, such as RPCs, indexers, bridges, or oracles

#### 2. Share your interest

If your team is interested in exploring a migration or redeployment to Celo, [fill out this short interest form](https://docs.google.com/forms/d/e/1FAIpQLSe_hWNMi7A_6l6k8VQEprVvQ0cMc0UzvGQF6G0FWgx24Vh_Mw/viewform).

#### 3. Connect with Celo

After receiving your submission, the Celo team will get in touch to share relevant resources and discuss what a potential move could look like for your project.

Considerations may cover:

* Product fit
* Technical requirements
* User or liquidity considerations
* Ecosystem relevance
* Potential next steps

#### 4. Define the migration approach

Together with the Celo team, you can determine the most appropriate migration or redeployment approach based on your product, technical requirements, and users.

There is no single migration path for every project. The goal is to help each team understand its options and work through an approach that makes sense for its specific setup.

#### Important Notes

* Migration is optional.
* Celo will review projects individually.
* No funding, technical support, or ecosystem support should be assumed unless confirmed.
* Projects with users, liquidity, or assets should prepare a more detailed migration plan.
* Public communication should only happen once the migration path is clear and aligned.


