Wallets, neobanks, and fintech platforms
Build a distribution experience around Torq resources, wallet sessions, wrappers, and canonical events.
Use Torq to embed governed tokenized credit in a wallet, neobank, exchange, fintech, or partner distribution product. The platform owns customer experience and signing; Torq supplies the canonical API, typed workflows, governed contracts, and completion evidence. Access remains Developer Preview.
Institutional Earn distribution use cases
Use the complete implementation playbook for your exact delivery model:
All audiences first implement the complete credit lifecycle: product discovery, deposit and share-class selection, position/yield/liquidity monitoring, redemption, impairment detection, optional Distressed Recovery Fund review, claims, and canonical reconciliation. A recovery-fund subscription is a separate customer-approved allocation; it is not automatic compensation for an affected vault position.
| Audience | End-to-end implementation |
|---|---|
| Wallet providers | Build a wallet-native Earn program |
| Neobanks | Build a ledger-reconciled Earn account |
| Exchanges and custodians | Build custodial Earn |
| Asset managers | Launch and operate governed Earn vaults |
| Financial service providers | Build a tenant-isolated white-label platform |
| Yield aggregators | Build a comparable Earn marketplace |
| Crypto lending protocols | List Torq vaults natively with the existing connected wallet |
Neobanks, wallets, and exchanges
Add an Earn program inside an existing customer experience without rebuilding vault discovery, eligibility, transaction preparation, position state, and reconciliation from raw chain data. Approved distributors can route deposits through a partner wrapper and participate in the approved reseller split for the activity they distribute. The customer remains inside the integrator's product, while signing and custody remain inside the customer's or integrator's declared custody boundary.
Asset managers and financial service providers
Package institutional-grade Earn access around selected Torq vaults, mandate controls, reporting, and customer servicing. Use canonical resources and events to support portfolio views, operational reconciliation, and lifecycle communication. A public integration never grants protocol-governance authority: it distributes supported Earn products through documented roles and workflows.
Yield aggregators and integrators
List Torq vaults beside other Earn opportunities, then use approved wrapper deposit and redemption flows instead of sending customers to a separate Torq experience. An approved reseller split can create distribution economics for qualifying wrapper-attributed activity. Where the commercial agreement and disclosures permit it, an integrator can use that margin to offer a lower-fee distribution route than the direct Torq channel and compete on customer price. The same model can apply to other approved integrators, not only aggregators.
Crypto lending protocols
Add Torq vaults to an existing protocol catalog without replacing its application shell or wallet connection. Use the host's already-connected wallet for identity, review, simulation, and signing; use Torq canonical resources for every Torq vault, market, allocation, liquidity, eligibility, and position field. Deposit and redemption stay explicit Torq typed workflows, so the host must not assume that a Torq wrapper has identical synchronous behavior to its native vault contracts.
Torq does not guarantee revenue, margin, vault performance, approval, or a particular fee advantage. Program approval, reseller terms, customer pricing, taxes, disclosures, and regulatory treatment remain specific to each integrator and jurisdiction. External access remains Private Preview.
Choose an architecture
| Integration | Browser boundary | Server boundary | Signer |
|---|---|---|---|
| Self-custody wallet | Origin-bound publishable key and wallet session | Optional secret-key backend | User wallet |
| Neobank or fintech | Customer session in app | Secret-key service and durable event inbox | Customer-owned HSM or MPC |
| Exchange or custodian | No server authority in browser | Tenant-scoped API, audit, reconciliation | Exchange custody boundary |
| Partner channel | Wallet session where required | Partner application, wrapper, fee, and event services | Authorized partner wallet |
Distribution capabilities
- Discover assets, markets, vaults, tranches, eligibility, positions, fees, and partner programs.
- Use wrappers for approved
partnerWrapperDepositandpartnerWrapperRedeemworkflows. - Submit partner applications and operate approved channels through explicit role workflows.
- Track wrapper flows, program snapshots, fee shares, and borrower-fee claims through canonical resources and events.
- Keep every organization, application, environment, key, origin, scope, quota, and webhook endpoint isolated in the Developer Console.
Security boundary
Torq never asks a platform to upload custody secrets and never turns a publishable key into server authority. A wallet session authenticates the current wallet for the scoped application; it does not grant protocol-governance, emergency, or unrelated tenant access.
Reconcile before crediting a customer
Webhook delivery is at least once. Verify the raw-body signature, durably store the event, deduplicate
both eventId and deliveryId, acknowledge it, then read the referenced canonical resource. Never
credit a customer solely from a receipt or event payload.
Continue with Embed Torq Earn, Code samples, and Webhooks and events.