Wallets

Private-Label Model

Partners white-label at the product layer: your brand, your signup, your balance and deposit screens. Provision and reads run on your server with a business API key. Onchain execution always requires user consent in your shell because Torque holds custody and your API key must never sign user transactions.

Manage keys and setup in the developer portal.

Provision

Call on signup. externalUserId is your stable user id; email is their step-up identity for execute in your flow (not a Torque app signup). Idempotent on externalUserId.

server.ts

import { createTorqueFromEnv } from 'torque-node'
const torque = createTorqueFromEnv()
const wallet = await torque.wallets.ensure({
  externalUserId: 'user_48291',
  email: 'user@example.com',
})

HTTP equivalent:

provision.sh

curl -sS -X POST "https://app.torque.fi/api/v1/accounts/end-users" \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "externalUserId": "user_48291",
    "email": "user@example.com"
  }'

Response includes addresses, portfolioSummary, and capabilities. Full accounts reference: below.

Deposits

Return addresses in your deposit UI. Encode each address in a client-side QR: QR value is the raw address string from addresses.evm, addresses.solana, or addresses.btcDeposit. No server QR endpoint.

Poll GET /accounts/end-users/{id}/deposits or set an optional deposit webhook in portal Settings (end_user.deposit.detected). Preview QR in the developer portal wallet row.

Execute in Your App

Trades, transfers, and withdrawals are confirmed in your UI. Your API key provisions wallets and reads balances; it never signs user transactions. After the user confirms in your product, your server calls POST /execute/** with a delegated JWT.

Not supported: Mint wallet JWTs with sk_live_… alone; Unattended server sweeps without user or attested partner consent; Export seed phrases or owner keys to partners.

Portal → Settings → Execute callbacks → enter your app URL (e.g. https://yourapp.com). Torque registers callback https://yourapp.com/torque/connect/callback. Add that route on your backend. Consent completion returns to your app with ?code=….

v1 shipping note: Shipping today: consent completion returns to your app via a Connect callback and delegated JWT. Embedded confirm UI in your shell is on the roadmap.

Test execute callback (portal): try before your app is live. Callback: https://developers.torque.fi/connect/callback.

Connect details: Connect OAuth, Actions: cash-out, Authentication.

Identity & Recovery

The email you pass at provision is the step-up identity when the user confirms execute in your flow. Use a stable address your users will keep. externalUserId is how you look up the wallet in your systems. Wrong email at provision means a separate wallet; balances are not merged between emails.

Support copy for lost devices: same email → same wallet (email code, passkey, or linked OAuth). Lost email access: contact hello@torque.fi for verified help, not self-serve. Details: Account Recovery for integrators.

Accounts API

Caller identity: business (sk_live_…) or wallet (Smart Wallet JWT). Metadata only; no fund movement.

GET /accounts/business

business-me.sh

export TORQUE_KEY="sk_live_…"

curl -sS "https://app.torque.fi/api/v1/accounts/business" \
  -H "Authorization: Bearer $TORQUE_KEY" \
  | jq '.'

GET /accounts/wallet

User + EVM/Solana addresses for the JWT; confirm before POST /execute/**. There is no partner API to mint wallet JWTs; see Authentication.

wallet-me.sh

export WALLET_JWT="<smart_wallet_jwt>"

curl -sS "https://app.torque.fi/api/v1/accounts/wallet" \
  -H "Authorization: Bearer $WALLET_JWT" \
  | jq '.'

FAQ