> For the complete documentation index, see [llms.txt](https://support.lisk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.lisk.com/guides/getting-started/complete-business-verification-kyb/financial-tax-regulatory-and-special-request-for-information-evidence-guide.md).

# 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)