What you keep, and what the lender decides
You keep the client relationship, the interface and the onboarding. Your clients sign every deposit, loan and repayment from their own wallets, and your instance builds each transaction for them. The lender of record decides the rest: the rates, the loan-to-value limits, who may borrow and how seized collateral is sold. A market you deploy takes no loans until a bank adopts it, and once adopted, only the bank’s roles change its parameters. Roles and signatures draws the line step by step.Track 1: bring an asset to lending
For tokenization platforms and issuers whose clients hold a token they would rather borrow against than sell.- Import the token. Detect Token, then Import Token. A market can only be deployed against a token your instance imported.
- Describe it. Publish the profile with Update Profile and the instrument record lenders read with Save Instrument. A token without a published profile is refused at deployment with
TOKEN_PROFILE_REQUIRED. - Deploy the market. Deploy Market picks the collateral mode, the price source and the opening rate and term offering, and nominates the banks that may take it.
- Authorize it on the token. The token’s agent or identity registry operator signs the steps Get Setup Steps lists. That is often your platform.
- Hand it to a bank. A nominated bank takes the market with Accept Lender Role. Get Nominations shows who may.
- Keep the register in step. Whoever keeps the token’s register records each pledge from List Pledges. Name that party on the market with Set Market Register, and it receives each change as a pledge webhook. The register entry is the operative act, and it stays with the register provider.
Track 2: add earn and borrow to your app
For apps, brokers, neobanks and wealth platforms.- Onboard clients. Get each client’s wallet through the gate the bank chose. Use an onboarding to run the identity check inside your own app, a hosted ID link to send the client to verify.trusset.org, direct verification if you ran KYC yourself, or KYC-STARKs for proof-backed claims. Onboarding and access shows which path fills which gate.
- Send the KYC file when the bank asks. A bank that gates on a whitelist can name you as its KYC source. Seal each client’s file with KYC Courier, and the bank lists the wallet once it approves the file. See the verifier walkthrough.
- Offer earn. List Vaults returns every published vault on your network. Show the operating bank from
operatedBywherever you show the vault. Deposit builds the client’s approval and deposit and names your instance as distributor. - Collect your share. Once the vault’s bank approves your instance as a distributor, it earns the distributor share of the interest its depositors’ capital produces. Before that, deposits still go through and the share goes to the vault operator. Get Earnings shows it, and Collect Distributor Fees with Pay Distributor pays it out.
- Offer borrow. Quote with Get Max Borrow, then build the loan with Open Loan. On a
FREEZEmarket the collateral stays in the client’s wallet. Borrowing runs on markets your instance holds, such as one you deployed in track 1. - Show positions. Get Lending Positions lists one client’s loans and debt. Get Position Statement returns a PDF with the verified transaction trail.
