Cowrie Research

daimo-primary-sources-2026-04-27

5 min read

Daimo primary-source snapshot

Fetched: 2026-04-27 UTC

1) Official homepage

Source: https://daimo.com/

Selected excerpts from the official site:

The ramp for ambitious stablecoin apps

Integrate once, accept deposits from anywhere.

Funds are routed and settled non-custodially to your configured destination automatically.

Additional signals from the homepage:

  • The homepage framing is unusually clear that Daimo is building infrastructure for apps, not a consumer wallet
  • The non-custodial settlement claim is central to how Daimo wants integrators to understand the trust model
  • The rail list on the homepage already signals a hybrid fiat-plus-crypto deposit product rather than a single-chain onchain widget

2) Docs introduction

Source: https://docs.daimo.com/introduction

Selected excerpts from the official docs:

Daimo is the ramp for stablecoin apps. Integrate once, accept deposits from any wallet, any chain, any token. Funds arrive as the stablecoin you want, on the chain you want.

Create a session: specify destination chain, token, and amount

Both paths use the same session-based API. The modal SDK is a thin React wrapper around the API.

Additional signals from the source:

  • The destination-first wording is a strong clue that Daimo is better understood as routing/orchestration infrastructure than as a simple checkout page
  • The same source explicitly presents both SDK and raw API paths, which reinforces that the core product is a reusable control plane

3) Docs index (llms.txt)

Source: https://docs.daimo.com/llms.txt

Selected excerpts from the docs index:

Sessions: Core concept: session lifecycle, statuses, and credential model

Fiat: Accept deposits from local bank accounts and payment rails via a Daimo-hosted flow

Deposit to Hyperliquid: Accept payments from any chain and deposit directly to a Hyperliquid account.

Additional signals from the source:

  • Even the AI-facing index is high-signal because it shows the product surface at a glance: sessions, fiat, webhooks, custom integration, supported chains, and destination-specific advanced flows
  • The Hyperliquid page in the official docs is especially useful because it reveals Daimo is not only thinking about generic wallet top-ups but about embedded application settlement destinations

4) Sessions guide

Source: https://docs.daimo.com/guides/sessions

Selected excerpts from the official docs:

A session represents a single deposit attempt. It tracks the full lifecycle from creation through delivery.

Daimo uses two types of credentials

The client secret is safe to expose in browser code.

Hosted fiat deposit … Daimo delivers the stablecoin to your destination — same session lifecycle as any other payment method.

Additional signals from the source:

  • The explicit session lifecycle and credential split are strong trust-model clues worth preserving
  • The docs show Daimo normalizing EVM, Tron, Solana, and fiat into one lifecycle, which is a stronger infrastructure signal than the homepage alone
  • The inclusion of themeCssUrl, status transitions, refund behavior, and chain-specific payment-method details suggests a fairly mature integrator product

5) API overview

Source: https://docs.daimo.com/api-reference/overview

Selected excerpts from the official docs:

https://api.daimo.com

API key … Server-side. Create sessions, retrieve full details.

Client secret … Client-side, per-session. Set payment method, check status.

Additional signals from the source:

  • The API docs confirm Daimo is exposing a real programmable surface rather than only a hosted UI
  • The typed session object, payment-method variants, and error model suggest production-ready developer infrastructure

6) Supported chains

Source: https://docs.daimo.com/supported-chains

Selected excerpts from the official docs:

Deposits can be delivered to any of these EVM chains

Users can deposit from: All EVM chains above … Solana … Tron

Source chain and token availability is automatic.

Additional signals from the source:

  • The official docs explicitly frame Daimo as multichain routing infrastructure, not just an EVM-only deposit widget
  • The destination/source split is especially important for categorization because it centers delivery outcomes rather than asset custody

7) Fiat guide

Source: https://docs.daimo.com/guides/fiat

Selected excerpts from the official docs:

Fiat lets your users deposit in local currency (CAD, USD) using familiar rails like Interac, ACH, and Apple Pay.

Daimo hosts identity verification and the deposit UI, settles the fiat transfer, and delivers the stablecoin to your destination.

The user pays in their local currency and never touches crypto.

Additional signals from the source:

  • This guide makes Daimo look more like a stablecoin deposit operating layer than a crypto-only onramp
  • Hosted KYC plus stablecoin delivery to a specified onchain destination is a distinctive categorization clue
  • The guide also shows Daimo can be embedded via modal, WebView, iframe, or fully custom integration

8) Hyperliquid advanced guide

Source: https://docs.daimo.com/advanced/hyperliquid

Selected excerpts from the official docs:

Daimo Pay can bridge funds from any chain to a Hyperliquid (Hypercore) account in one session.

It uses a final-call adapter on HyperEVM that forwards USDC into Hypercore via Hyperliquid’s CoreDepositWallet.

Always set refundAddress when using calldata.

Additional signals from the source:

  • This is one of the strongest current clues that Daimo is app-facing settlement infrastructure, not merely a branded deposit form
  • Contract-call delivery plus refund-path guidance suggests Daimo is willing to expose fairly composable execution patterns to integrators

9) GitHub organization

Source: https://github.com/daimo-eth

Selected excerpts/signals from the public org page:

sdk

machine-payments

real-world-payment — Agent skill for sending real-world payments via Venmo, CashApp, Zelle, PayPal, Wise, Revolut. Powered by Daimo + Peer Protocol.

This is our old, archived payments app. For our current product, see our website.

Additional signals from the source:

  • The public org suggests Daimo has evolved from an earlier payments app into a more infrastructure-centric product surface
  • The presence of SDK, machine-payments, and agent-payment experiments is notable because it hints at broader ambitions around programmable and agentic money movement

Notes

  • Daimo appears best cataloged as stablecoin deposit ramp / onchain settlement infrastructure / fiat-and-crypto deposit orchestration.
  • No canonical whitepaper or litepaper surfaced in this pass.
  • The strongest categorization clue is the session-based destination-routing model spanning crypto deposits, hosted fiat rails, and downstream app-specific settlement targets like Hyperliquid.

Graph View