Cowrie Research

swapped-com

3 min read

Swapped.com

  • Name: Swapped.com
  • URL: https://swapped.com/
  • Category: embedded ramp widget stack / deposit-and-top-up orchestration product / signed callback and dashboard integration surface
  • Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
  • Summary: Swapped.com is still worth keeping as a product note because Ramp and Connect expose a concrete integration surface: embeddable buy/sell widgets, signed iframe parameters, callback and sandbox workflow, and deposit/top-up flows that connect wallets or exchanges without manual address copying. The named operator boundary around partner onboarding, legal-entity routing, merchant-dashboard control, review and refund workflow, and callback / transaction-state truth now lives in swapped-com.
  • What it does:
    • Lets partners embed hosted buy and sell flows for supported crypto assets inside their own app or website through Swapped Ramp
    • Exposes signed iframe and callback mechanics, sandbox support, and a merchant dashboard so teams can integrate and monitor widget-driven money movement
    • Provides Swapped Connect for deposit and top-up flows that prefill transfer details and reduce wallet-address and network-selection mistakes
    • Supports multiple Connect linkage models — direct wallet/exchange integration, API-key connection, and proxy connection — that make the product surface more than a simple fiat widget
    • Publishes docs for pricing, payment and payout methods, supported assets, payment status, transaction endpoints, and related integration workflow
  • Key claims:
    • The current source set still shows a real integration product rather than just a retail buy/sell site: the public docs cover widget behavior, signed integration parameters, callbacks, transaction monitoring, and sandbox setup
    • Swapped Connect is the strongest reason to keep the product note: it turns Swapped into deposit and top-up middleware that can sit between a user’s wallet or exchange account and the destination platform without making the user manually copy addresses and networks
    • The merchant dashboard matters at the product layer because it is where teams monitor orders and configure integration parameters, even though the sharper operator question about who controls that shell belongs in swapped-com
    • The legacy kado.money brand history is still useful context because it explains why older discovery paths may point to stale or broken docs, while the live product surface now sits at swapped.com and docs.swapped.com
    • This is better read as embedded payments and deposit-orchestration middleware than as a generic consumer ramp brand
  • Whitepaper: No canonical Swapped.com or Kado whitepaper/litepaper surfaced in this pass. The clearest current source of truth remains the official site, docs portal, and the earlier product-layer snapshot in ../whitepapers/swapped-com-primary-sources-2026-04-27.md, now complemented by the company-side source capture in ../whitepapers/swapped-com-company-primary-sources-2026-08-11.md.
  • Sources:

Internal linkages

  • Company / operator boundary for partner onboarding, legal-entity routing, merchant-dashboard control, review and refund workflow, and callback truth: swapped-com.
  • Best adjacent product reads: moonpay-commerce and walletconnect-pay.

Protocol / company boundary

  • Keep this note on the product and integration surface: Ramp widget behavior, signed iframe parameters, callbacks, transaction and sandbox workflow, Connect deposit flows, and the connection modes partners or users actually touch.
  • Use swapped-com for the named-operator layer around partner admission, jurisdiction routing, merchant-dashboard access, documentation review, refund handling, and the callback / transaction-state truth integrators ultimately depend on.
  • That split matters because how do I integrate Swapped Ramp or Connect? and which company decides who gets access, under what entity, with which review and lifecycle-publication rules? are related but not identical questions.

Control surface

  • At the product layer, authority sits in the embed model, signed integration parameters, supported assets and payment methods, wallet/exchange connection modes, transaction-status objects, sandbox behavior, and callback consumption.

  • The thicker legal, review, and operational shell now points upward to swapped-com.

  • Read Swapped.com as hosted ramp and deposit-orchestration middleware, not as a neutral payments baseline.

  • Last reviewed: 2026-08-11 UTC

Graph View

Backlinks