Ramp Network

• Name: Ramp Network
• URL: https://rampnetwork.com/
• Tags: ethereum-ecosystem
• Category: fiat-crypto on/off-ramp infrastructure / embedded checkout SDK / payments orchestration platform
• Summary: Ramp Network at the project layer is the embedded widget, SDK, and REST API surface inside a broader company-run compliance and payout shell. The useful product cut is the hosted checkout and sale flow partners actually integrate — widget initialization, SDK events, REST asset and method discovery, and signed lifecycle webhooks. The broader operator boundary now lives in ramp-network, which is the cleaner place to reason about partner onboarding, API-key issuance, feature enablement, jurisdiction policy, payment and payout coverage, and regulated-entity posture.
• What it does:
  • Lets partners embed on-ramp and off-ramp flows so users can buy or sell supported cryptoassets directly from a wallet, dapp, or web app
  • Exposes a hosted widget plus SDKs and APIs for web, iOS, Android, React Native, and Flutter integrations
  • Publishes REST APIs for asset availability, pricing, limits, payment methods, payout methods, and related integration data, with rate limits and geolocation-aware responses
  • Uses signed webhook and event surfaces so integrators can track purchase and sale lifecycle changes without relying only on frontend callbacks
  • Supports multiple payment and payout rails including open banking, cards, Apple Pay, Google Pay, SEPA transfers, US bank transfers, direct card payouts, and PIX in supported regions
• Key claims:
  • Ramp’s docs describe the product as a way to let users buy or sell crypto directly from a partner dapp while Ramp aggregates liquidity, payment methods, and payout methods behind the scenes
  • The getting-started docs present open banking, cards, Apple Pay / Google Pay, SEPA transfers, US bank transfers, and direct Visa / Mastercard payouts as core parts of the integration surface
  • The REST API docs show Ramp operating a structured JSON API for asset discovery, pricing, country-filtered availability, payment methods, and payout methods rather than a widget-only integration model
  • The same API docs show hostApiKey and enabledFeatures as first-class parts of the product surface, which is a useful reminder that even the project layer is not a static public widget
  • The webhook docs show Ramp exposing purchase and sale state transitions as signed backend integration primitives, including ECDSA signature verification and explicit retry behavior
  • Ramp’s verified GitHub org and SDK repos corroborate the multi-platform developer-infrastructure posture beyond the consumer-facing buy/sell UI
• Whitepaper: No canonical Ramp Network whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs, REST API and webhook references, and Ramp’s verified GitHub organization collected in ../whitepapers/ramp-network-primary-sources-2026-04-27.md.
• Sources:
  • https://rampnetwork.com/
  • https://docs.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
  • https://raw.githubusercontent.com/RampNetwork/ramp-instant-sdk/master/README.md

Internal linkages

• Company boundary for the broader operator shell: ramp-network.
• Closest peer in the same embedded-ramp tier: transak.
• Best contrast for the routing layer above any single provider: onramper.

Protocol / company boundary

• Keep this note on the product shell: widget initialization, SDK and mobile integration shape, REST discovery APIs, webhook and event handling, and the purchase / sale lifecycle objects partner apps directly consume.
• Use ramp-network for the named-operator layer around partner onboarding, API-key issuance, feature enablement, jurisdiction and payment-method policy, payout coverage, regulated-entity posture, and the broader commercial/compliance shell.
• That split matters because what does a Ramp integration expose? and which company controls production access, coverage, policy, and transaction-state authority? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in widget initialization, SDK configuration, hostApiKey-enabled feature exposure, geolocation-aware asset and method discovery, webhook delivery, and the purchase or sale lifecycle objects the integration consumes.

• The broader operator dependency sits one layer up in ramp-network: partner admission, API-key issuance, payment and payout coverage, compliance policy, regulated-entity perimeter, and company-run truth surfaces when transaction state is disputed.

• The useful project-layer question is which checkout, SDK, REST, and webhook primitives downstream apps inherit when they integrate Ramp, not who regulates or commercially packages the whole stack.

• Last reviewed: 2026-08-10 UTC