Cowrie Research

depay

4 min read

DePay

  • Name: DePay
  • URL: https://depay.com/
  • Category: wallet-to-wallet checkout middleware / multichain payment routing / merchant plugin platform
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: DePay is wallet-to-wallet checkout middleware. Keep this note on route selection, accepted-asset policy, fee extraction, and callback truth around direct-wallet settlement. The broader operator boundary now lives in depay, which is the cleaner place to reason about DePay AG’s managed integration shell, centralized-service licensing, callback-signing keys, domain restrictions, and the legal/privacy perimeter around those hosted surfaces.
  • What it does:
    • Lets applications and merchants accept wallet-to-wallet crypto payments directly into their own addresses without custodial settlement by DePay
    • Supports payment links, embeddable buttons, and fully controlled in-app widgets with managed and unmanaged configuration modes
    • Allows merchants to denominate prices in fiat currency or in tokens, while using real-time conversion so payers can use different assets than the receiver ultimately wants
    • Provides callback and event-webhook flows so merchants can automate post-payment fulfillment, redirect users, and observe payment lifecycle states
    • Offers checkout integrations for Shopify, WooCommerce, and World App MiniApps in addition to general-purpose developer integrations
    • Exposes the DePay payment protocol / payment router as a protocol layer developers can integrate directly into smart contracts, protocols, or other payment products
  • Key claims:
    • The homepage says DePay offers software, infrastructure, and APIs to manage payments on blockchains and highlights direct wallet payments, auto-conversion, and embeddable payment experiences
    • The benefits page says DePay payments are peer-to-peer and non-custodial, that transactions flow directly into the merchant wallet, and that DePay uses DeFi protocols for automatic token conversion
    • The payments docs say DePay offers links, buttons, widgets, plugins, payment APIs, and an underlying payment protocol, which is a broader product surface than a single widget SDK
    • The widget docs say developers can create managed integrations in app.depay.com, denominate payments in currencies or tokens, choose accepted token/blockchain combinations, and configure HTTPS callbacks and events
    • The widget docs show callback payloads with blockchain, transaction hash, sender, receiver, token, amount, confirmations, timestamps, and optional redirect control via forward_to
    • The support docs say DePay currently supports 10 blockchains, hundreds of wallets, and thousands of tokens, with explicit support pages for wallet standards such as WalletConnect, Ethereum extension wallets, Solana extension wallets, Solana Mobile Wallet Adapter, and Solana Pay
    • The protocol docs say the DePay payment protocol enables on-the-fly token conversion during a payment, delivers funds to the receiver, and can optionally extract a fee on execution
    • The GitHub READMEs show DePay maintaining open-source widget and button packages that support both EVM and Solana environments and expose configuration for multichain payments, fixed-currency pricing, and fee extraction
  • Whitepaper: No canonical standalone DePay whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, documentation portal, protocol and integration docs, and the public widget/button repositories; see ../whitepapers/depay-primary-sources-2026-05-02.md and ../whitepapers/depay-company-primary-sources-2026-08-13.md for the newer company-boundary split.
  • Sources:

Internal linkages

  • Company boundary for the managed integration and legal/operator shell: depay.
  • Best upward reads: walletconnect-pay and solana-pay.
  • Useful adjacent company comparisons when the sharper question is webhook truth or managed checkout workflow: coinflow and onramper.

Protocol / company boundary

  • Keep this note on the product shell: wallet-to-wallet checkout, token-conversion routing, accepted-asset policy, plugin and widget behavior, redirect mechanics, and the protocol/router surface developers can wire into apps or contracts.
  • Use depay when the sharper question is who controls the managed integrations in app.depay.com, callback-signing keys, retry semantics, domain restrictions, centralized-service licensing, and the broader legal/privacy shell around those hosted surfaces.
  • That split matters because how does DePay route and present a payment? and which company controls the managed integration and callback-truth shell around that payment? are related but not identical questions.

Control surface

  • The leverage at the product layer sits in accepted chain-and-token policy, route selection for conversion, fee extraction, checkout-widget defaults, and whether merchants trust DePay callbacks and events as the real payment state.

  • The broader operator dependency now sits one layer up in depay: managed integrations, callback-signing keys, retry semantics, domain restrictions, centralized-service licensing, and the legal/privacy shell merchants inherit when they rely on the hosted path.

  • Treat DePay as wallet-to-wallet checkout middleware at this layer, not as a neutral payment primitive and not as the whole company shell around it.

  • Last reviewed: 2026-08-13 UTC

Graph View

Backlinks