# Risk management ### Underwriting We underwrite the user based on:\ \- **Onchain data**: wallet assets, transaction history, DeFi activity; \ \- **Offchain data**: bank account balance, assets & liabilities, cashflow;\ \- **Exotic data sources** like criminal history, tax reports, and employment status, that we get with **zkTLS** or **Open Banking**;\ \ Using this mix allows us to get more **accurate results** than most web2 companies, as well as **serve a global audience**. We design **tailored algorithms** (decision tree, weights, and thresholds) **for each underwriting case**, based on the specifics of our partner integration: location, userbase, and payment target. ### Servicing & default management We currently allow user to **repay their debt manually** or **inside our partner app** (through API). For EVM networks, we leverage our partner's infrastructure to enable **automatic recurring payments** (see [Otim Docs](https://docs.otim.com/docs/use-cases#recurring-transfers)). We plan to use more onchain protocols to optimize repayment UX in the future. We employ several **offline debt collection agencies** to service our debt if needed. Special agreements with our partners allow us to **restrict app or asset access** in case of delinquency. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.yumi.finance/summary/risk-management.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.