Ramp Network

• Name: Ramp Network
• URL: https://rampnetwork.com/
• Category: payments and ramp operator / embedded checkout and payout company / compliance-and-coverage middleware company
• Tags: ethereum-ecosystem
• Summary: Ramp Network belongs in companies/, not only projects/, because the durable dependency is a named company that onboards partners, issues API-key-backed custom integrations, decides which payment and payout methods are exposed in which countries, enforces eligibility and compliance policy, and acts as the source of webhook and dashboard truth for purchase and sale state. The useful question is not just can users buy or sell crypto here? but which company controls the coverage, payout, and lifecycle surfaces the host app inherits by default?
• What it does:
  • Operates embedded on-ramp and off-ramp flows for wallets, dapps, and apps through hosted widget, SDK, and API integrations
  • Packages payment and payout coverage across open banking, cards, Apple Pay, Google Pay, SEPA transfers, US bank transfers, direct card payouts, PIX, and other country-specific method combinations exposed through its APIs
  • Issues custom integrations and feature-gated API access, including partner-managed host API keys and enabled-feature responses in the REST API surface
  • Runs signed webhook delivery for purchase and sale state changes, with company-published public keys and retry policy that partners are expected to treat as operational truth
  • Sells a broader company shell that now includes a consumer app, self-custodial wallet and swap positioning, and regulated operating entities in the US, EU, and UK alongside the embedded developer surface
• Key claims:
  • The homepage says Ramp is regulated in the US, EU, and UK through named entities including Ramp Swaps LLC, Ramp Swaps (Ireland) Ltd, and Ramp Swaps Ltd, which is analytically useful because the entity perimeter matters more than a generic buy crypto label
  • The same homepage markets 10M+ customers, 150+ countries and territories, 40+ fiat currencies, 110+ cryptoassets, and a combined buy / sell / swap / wallet shell, reinforcing that several operator surfaces sit under one company boundary
  • The getting-started docs say partners must fill out a form to receive an API key and then work with Ramp on the next steps, which is a clean sign that production use is company-gated rather than a neutral public rail
  • Those docs also present open banking, cards, Apple Pay / Google Pay, SEPA transfers, US bank transfers, and direct Visa / Mastercard payouts as configurable parts of one company-run stack rather than separate providers the integrator controls directly
  • The REST API docs say hostApiKey unlocks partner-enabled features, userIp geolocation filters which assets are returned, and separate endpoints enumerate available payment methods and payout methods by country and currency, making Ramp’s policy surface operationally explicit
  • The webhook docs say Ramp signs webhook payloads with ECDSA, publishes production and demo public keys, retries failed deliveries four times with a three-minute delay, and expects integrators to verify signatures before trusting purchase or sale events
• Whitepaper: No classic standalone company whitepaper is the important artifact here. The clearest primary materials are the homepage, getting-started docs, REST API reference, and webhook docs; the broader source bundle remains ../whitepapers/ramp-network-primary-sources-2026-04-27.md.
• Sources:
  • https://rampnetwork.com/
  • https://docs.rampnetwork.com/getting-started
  • https://docs.rampnetwork.com/rest-api-v3-reference
  • https://docs.rampnetwork.com/webhooks
  • https://github.com/rampnetwork

Internal linkages

• Product-layer note: ramp-network.
• Useful adjacent company reads: moonpay, transak, and bvnk.
• Best routing-layer contrast where the question shifts toward provider aggregation rather than one company shell: onramper.

Protocol / company boundary

• ramp-network is the product-layer note for the hosted widget, SDK, and REST API surface that partners integrate.
• This company note is the operator boundary: partner onboarding, API-key issuance, custom feature enablement, jurisdiction and payment-method coverage, payout-method exposure, webhook signing, and regulated-entity posture all sit with Ramp as a named company.
• That split matters because the dependency most integrators inherit is not a neutral fiat bridge. It is a company-managed workflow graph spanning checkout, KYC and eligibility enforcement, payout routing, geolocation policy, and lifecycle-state truth.

Control surface

• Practical leverage sits in partner admission, API-key issuance, enabled-feature flags, geolocation filtering, supported payment and payout methods, compliance and eligibility enforcement, signed webhook delivery, retry semantics, and the dashboard or support surfaces partners trust when purchase or sale state becomes disputed.

• The sticky dependency is operational memory: once a wallet or app hardens around Ramp-managed pricing, country filtering, checkout state, webhook signatures, and payout coverage, the real lock-in is to the company-run compliance-and-settlement shell rather than only to an SDK embed.

• Read Ramp Network as a company-operated money-movement and onboarding control plane first, and as an embedded on/off-ramp product second.

• Last reviewed: 2026-08-06 UTC