Concepts

Non-Custodial Wallets

Tesser provides both non-custody and third-party custodial options for financial institutions to hold and manage stablecoins. We generally recommend a non-custodial model (also called self-custodial) to eliminate dependency on third-party custodians and maintain full operational control — in this model, you (the customer) are the custodian. This section covers non-custodial wallets.

Wallets and Accounts

Wallets are a type of Account. In Tesser, an Account represents any value-holding instrument, including:

• Non-custodial wallets (covered in this section)
• Custodial wallets (held with a licensed custodian)
• Bank accounts
• Mobile money accounts
• Other account types that store value and can send/receive funds

Payments reference Account identifiers as sources and destinations, enabling orchestration across wallet and fiat rails with one model.

Wallet Security

Tesser provides enterprise-grade security with a non-custodial architecture, meaning:

Non-Custodial Key Management

• You maintain control: Tesser cannot move your funds without your authorization
• Private key isolation: Raw private keys are never exposed to Tesser, your software, or your team
• Secure enclaves: End-to-end private key generation and access control within hardware-isolated secure enclaves
• No single point of failure: Keys are generated and managed in secure hardware with strong isolation guarantees

Verifiable Security

• Cryptographic attestation: Cryptographic proof that only authorized code is running
• Reproducible deployments: Auditable system configurations with minimal attack surface
• End-to-end audit trail: Complete cryptographic verification of all operations

Key Features

• Automated backup management: We handle secure backup and disaster recovery for your keys
• Multi-factor access controls: Hardware-backed authentication and authorization
• Quorum-based operations: Distributed security architecture preventing single points of compromise
• Enclave secure channels: Direct encrypted communication between secure enclaves and authorized users

Wallet Provisioning

Wallets can be created for your team before KYB to support integration and testing. Certain payment operations are gated until KYB is complete. Retrieve wallets:

Code
 
curl -X GET https://api.tesser.xyz/wallets \
  -H "Authorization: Bearer your-access-token"

Each wallet includes id, name, address, currency, network, availableBalance, and pendingBalance.

Wallet Properties

Code
 
{
  "id": "wallet-123",
  "name": "Main USDC Wallet",
  "address": "0x742d35Cc6634C0532925a3b8D4C9db96590c6C87",
  "type": "custody",
  "currency": "USDC",
  "network": "ethereum",
  "availableBalance": "1000000000", // 1,000 USDC (6 decimals)
  "pendingBalance": "50000000",     // 50 USDC reserved
  "createdAt": "2024-01-01T00:00:00Z",
  "updatedAt": "2024-01-15T10:30:00Z"
}

Deposits and Balances

1. Send USDC/USDT to the address on the specified network.
2. After confirmation, availableBalance updates; pendingBalance is used to reserve funds for in-flight payments.

Tip: Maintain a safety buffer for fees and batch payouts.

Supported Networks

Currently supported:

• Polygon: Primary network for USDC and USDT transactions

Coming soon:

• Ethereum: Mainnet support for USDC and USDT
• Solana: High-performance blockchain for stablecoin payments

Note: Need support for other EVM-compatible networks? Contact us and we can quickly add support for additional chains.