Cowrie Research

depay-primary-sources-2026-05-02

4 min read

DePay primary sources — 2026-05-02

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is DePay’s official homepage, docs portal, payment integration pages, support matrix pages, protocol page, and public GitHub READMEs for widgets and buttons.
  • The current materials consistently frame DePay as non-custodial wallet-to-wallet payments infrastructure with both merchant-facing integrations and a protocol layer.

Primary-source snapshots

1) Official homepage

  • URL: https://depay.com/
  • Key excerpt:
    • The homepage presents DePay as a “Crypto Payments Platform” and says teams can use DePay’s software, infrastructure, and APIs to manage payments on blockchains.
    • It highlights embeddable payments, support across multiple blockchains and wallets, and built-in auto-conversion so customers can pay with many assets while the merchant receives the desired token.
    • The homepage repeatedly stresses direct wallet settlement rather than custodial processing.

2) Payments docs index

  • URL: https://depay.com/docs/payments/
  • Key excerpt:
    • The payments docs describe DePay as offering links, buttons, widgets, plugins, payment APIs, and a separate payment protocol.
    • This page is the clearest single source showing that DePay is broader than a one-off widget or plugin.
    • It also points to example repos for Express and Next.js integrations.

3) Benefits page

  • URL: https://depay.com/docs/payments/benefits/
  • Key excerpt:
    • The page says DePay payments are “peer-to-peer and non-custodial” and that every transaction flows directly into the merchant wallet without intermediaries.
    • It says DePay uses DeFi protocols for auto-conversion so merchants can accept thousands of cryptocurrencies while still receiving desired assets.
    • It also frames the UX as a “one-click” experience that scans customer wallet balances across multiple chains.

4) Widget integration docs

  • URL: https://depay.com/docs/payments/integrate/widget/
  • Key excerpt:
    • The widget docs show DePay as a self-hosted payment flow embedded directly into an app via package install or CDN.
    • Merchants can create managed integrations, denominate payments in currencies or tokens, choose accepted token/blockchain combinations, and place the integration code into the app with DePayWidgets.Payment({ integration: 'YOUR-INTEGRATION-ID' }).
    • The docs also define HTTPS callbacks and event endpoints, including example payloads carrying blockchain, transaction hash, sender, receiver, token, amount, confirmations, timestamps, and redirect control via forward_to.
    • Retry semantics are explicitly documented, with exponential backoff and up to 25 retries over roughly 21 days.

5) Supported blockchains page

  • URL: https://depay.com/docs/payments/supported/blockchains/
  • Key excerpt:
    • The page lists current support for Solana, World Chain, Base, Optimism, Arbitrum, Gnosis, Polygon, Avalanche, BNB Smart Chain, and Ethereum.
    • It also gives DePay’s own rough timing and transaction-cost expectations for each network, which is a useful operational clue that the product is optimized around live multichain payment routing rather than only static checkout embeds.

6) Supported wallets page

  • URL: https://depay.com/docs/payments/supported/wallets/
  • Key excerpt:
    • The page lists support for MetaMask, Coinbase Wallet, Phantom, World App, Backpack, Solflare, Ledger Live, WalletConnect, Ethereum extension wallets, Solana extension wallets, Solana Mobile Wallet Adapter, and Solana Pay.
    • The combination of EVM and Solana wallet-transport support is a strong clue that DePay is building a broad wallet-connectivity layer around payments.

7) Protocol page

  • URL: https://depay.com/docs/payments/protocol/
  • Key excerpt:
    • The docs say the DePay payment protocol can be integrated into smart contracts and protocols.
    • They define the protocol’s core function as enabling on-the-fly token conversion during a payment while delivering funds to the receiver and optionally extracting a fee.
    • This is the cleanest evidence that DePay has a protocol layer beneath the checkout and widget surface.

8) Checkouts docs

  • URL: https://depay.com/docs/checkouts/
  • Key excerpt:
    • The checkout docs show DePay packaging store-facing flows for Shopify, WooCommerce, and World App MiniApps.
    • This suggests DePay is not only a developer SDK but also a merchant plugin/distribution layer.

9) Widgets README

  • URL: https://raw.githubusercontent.com/DePayFi/widgets/main/README.md
  • Key excerpt:
    • The README describes DePay Widgets as enabling wallet-to-wallet crypto payments, with both managed integrations and unmanaged local configuration.
    • It shows support for both EVM and SVM packaging, multichain accept lists, fixed-currency pricing, and fee / protocol-fee configuration.
    • The README is also a good primary source for the distinction between simple execution-only flows and managed integrations that include callbacks.

10) Buttons README

  • URL: https://raw.githubusercontent.com/DePayFi/buttons/main/README.md
  • Key excerpt:
    • The buttons package exposes a low-friction HTML and React surface for merchant payments and donation flows.
    • This reinforces that DePay’s product surface includes lightweight merchant-facing embeds in addition to the more configurable widget.

Working conclusion

DePay is best cataloged as non-custodial multichain payment infrastructure centered on direct wallet settlement, auto-conversion, and reusable integration surfaces. The most important differentiator in this pass was the combination of merchant plugins and embeds with a deeper payment-router/protocol layer, which makes DePay materially broader than a generic web3 checkout widget.

Graph View