Skip to content
Rampay

For businesses

A structured integration with
clear operational boundaries

Rampay is designed to enable eligible digital platforms to provide their users with access to a structured fiat-to-digital-asset journey, with defined stages, visible transaction states and clearly allocated operational responsibilities. Business onboarding, eligibility review and technical requirements apply before production integration.

Start an Onboarding ConversationSee the Onboarding Journey

Who it is designed for

Platform profiles

Suitability is assessed during onboarding and depends on the business model, target markets and applicable requirements.

Digital platforms

Platforms that want to offer their users a structured route from fiat payment to digital assets within an existing product experience.

Fintech products

Products that already operate payment or account journeys and need a defined digital asset access layer alongside them.

Wallet & app providers

Applications with an existing user base and asset destinations that require a coordinated funding journey.

Marketplaces & networks

Platforms where digital asset access complements an existing digital customer experience.

Integration model

An illustrative session-based request

The example below illustrates the shape of a session-based integration model. It is illustrative only and does not represent a live API contract, endpoint, credential model or guaranteed field set.

illustrative-request.http

Illustrative integration model
POST /v1/sessions
Authorization: Bearer <api_key>
Content-Type: application/json

{
  "reference": "ord_8f21c0",
  "amount": { "value": "250.00", "currency": "EUR" },
  "asset": "SUPPORTED_ASSET",
  "destination": { "type": "customer_wallet_address", "value": "<end_user_wallet>" },
  "customer": { "id": "usr_44120", "email": "customer@example.com" },
  "return_url": "https://platform.example/callback"
}

// Illustrative response
{
  "session_id": "ses_2b91e7",
  "status": "created",
  "next_action": "redirect",
  "redirect_url": "https://<rampay-session-url>",
  "reference": "ord_8f21c0"
}

Field names, supported assets, payment methods and available parameters are confirmed during onboarding and implementation. No live endpoint, credential or capability is implied.

Transaction states

Illustrative transaction states

A structured integration is only as good as its handling of non-success states.

  • created — session established for the request
  • verification_required — additional customer information or verification may be required
  • payment_pending — the fiat payment stage has not yet completed
  • in_review — additional assessment may be required before the journey proceeds
  • processing — applicable stages are being completed
  • completed — the journey has completed and the asset has been transferred to the end user’s designated wallet
  • declined — the journey cannot proceed following applicable checks or requirements
  • unavailable — the requested journey is not available for the given configuration or jurisdiction

Responsibilities

Clear operational boundaries

Responsibilities are defined during onboarding and reflected in the contractual documentation applicable to the relationship.

Platform responsibilities

The integrating business is responsible for its own product experience, its user communications, its own legal and regulatory obligations, and the accuracy of the data it submits.

Journey coordination

Rampay coordinates the structured transaction journey and the states communicated back to the platform.

Applicable requirements

Verification, screening and transaction control requirements may apply and can affect whether a journey can proceed.

Operational handling

The platform should be able to handle every documented state, including pending review, decline and unavailability outcomes.

Onboarding path

What to expect

Onboarding is a structured review. The steps below are illustrative and may vary.

  1. 01

    Introduction

    Discussion of the business model, markets and intended customer journey.

  2. 02

    Business review

    KYB, ownership and control, and business model assessment as applicable.

  3. 03

    Integration definition

    Definition of the transaction structure, states and operational responsibilities.

  4. 04

    Implementation

    Technical implementation against the agreed integration model.

  5. 05

    Production eligibility

    Production access is subject to successful completion of applicable requirements.

Transaction participant

The end user remains the transaction participant

Businesses integrate Rampay to enable an end-user on-ramp journey, not to purchase digital assets themselves.

The fiat-to-digital-asset transaction is completed by the individual end user. Following successful completion of the applicable transaction stages, the selected digital asset is delivered to the user’s designated wallet.

The integrating business does not receive the end user’s digital asset as part of the standard on-ramp journey described on this website.

Certain payment, verification, conversion and digital asset services may be provided through appropriately authorized third-party service providers, depending on jurisdiction and service configuration.

Nothing on this page constitutes an offer, a commitment to provide services, or a representation that any service, payment method, digital asset or capability is available in a particular jurisdiction.