Cowrie Research

swapped-com

4 min read

Swapped.com

  • Name: Swapped.com
  • URL: https://swapped.com/business
  • Category: embedded ramp and deposit-orchestration company / jurisdiction-routed money-movement operator / callback-and-review workflow shell
  • Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
  • Summary: Swapped.com clears the bar for a company note because the practical dependency is not only there is an embeddable ramp widget or there is a deposit/top-up flow. A named operator packages partner onboarding, merchant-dashboard access, signed integration credentials, transaction review and documentation requests, callback and transaction-state publication, refund handling, and even jurisdiction routing across multiple affiliated entities. The product note still matters for Ramp and Connect mechanics; this note is for the company boundary where Swapped ApS, Swappedcom Inc., and the Northstake ApS merchant-of-record path turn those mechanics into a live regulated service shell.
  • What it does:
    • Operates Swapped Ramp as an embeddable buy/sell widget and business integration surface for partners that want hosted fiat↔crypto conversion inside their own app or site
    • Operates Swapped Connect as a deposit and top-up orchestration layer for wallet and exchange transfers, including direct, API-key, and proxy connection modes
    • Runs the merchant dashboard and broader partner workflow for monitoring orders, viewing volume, and configuring integration parameters
    • Packages review, documentation, refund, and transaction-status handling into the same operating shell that controls product access and signed callback truth
    • Routes users and partners through different legal entities depending on geography, with explicit references to Swapped ApS, Swappedcom Inc., and Northstake ApS in current first-party materials
  • Key claims:
    • The business page now sells Ramp and Connect together as the product family and explicitly names the underlying entity shell: Swapped ApS, Swappedcom Inc., and the EU/EEA merchant-of-record path through Northstake ApS
    • The funds-handling page is unusually concrete for a public legal/marketing source: instant-payment authorizations can be canceled after review, bank-transfer client funds are kept separate from company funds, sell-side transfers are time-limited, and refunds are explicitly part of the operational path
    • The ramp terms say different Swapped entities serve different jurisdictions, that Swapped acts as principal in buy/sell transactions, and that access can be suspended for compliance reasons, which makes the legal entity boundary part of the real control surface rather than boilerplate
    • The Ramp docs show a company-run merchant dashboard where partners monitor orders and configure integration parameters, which is a stronger operator signal than a thin affiliate widget model
    • The Connect docs matter because they show Swapped brokering direct wallet/exchange links, API-key-based connections, and proxy connections; that is a live workflow and trust boundary, not just a consumer checkout page
    • The older kado.money identity now looks best read as legacy brand history beneath the current Swapped operator shell rather than as a separate still-canonical system
  • Whitepaper: No classic standalone company whitepaper is the point here. The strongest primary materials for this pass were the current business page, legal and funds-handling pages, Ramp and Connect docs, and the focused source snapshot in ../whitepapers/swapped-com-company-primary-sources-2026-08-11.md, complemented by the earlier product-layer snapshot in ../whitepapers/swapped-com-primary-sources-2026-04-27.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep swapped-com focused on the product and integration surface: embeddable ramp widgets, signed iframe parameters, callbacks, sandboxing, Connect deposit flows, and wallet/exchange connection modes.
  • Keep this note focused on the named operator boundary above that surface: partner admission, merchant-dashboard and credential control, jurisdiction routing, review and documentation workflow, refund handling, callback and transaction-state truth, and the legal entities that actually provide the service.
  • That split matters because how do Ramp and Connect work? and which company decides who can use them, under which entity, with which review path and lifecycle truth? are related but not identical questions.

Control surface

  • Practical leverage sits in partner onboarding, merchant-dashboard access, API and integration credential issuance, jurisdiction and entity routing, payment-method and geography coverage, documentation-review workflow, refund handling, transaction-status publication, and callback truth.

  • Non-custodial language does not remove operator authority here. It mostly relocates it into legal routing, transaction review, money-movement sequencing, and the publication of what counts as the authoritative order lifecycle.

  • Read Swapped.com as a company-run money-movement and deposit-orchestration shell, not as a neutral access rail.

  • Last reviewed: 2026-08-11 UTC

Graph View

Backlinks