Request flow

Overview

Use request when your user wants to ask someone else for money. The requester opens the magic link, composes the ask (route, amount, payout), and shares a payer-facing link. The payer completes payment on a fund-request flow.

Create example

curl -X POST https://raas-widgets-backend-sandbox.up.railway.app/partner/links \
  -H "X-API-Key: raas_sandbox_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "referenceId": "requester_user_123",
    "flow": "request",
    "language": "es",
    "config": {
      "userData": {
        "name": {
          "firstName": "Lucia",
          "lastName": "Mendez"
        }
      },
      "destinationCountry": "MX",
      "destinationCurrency": "MXN"
    }
  }'

config is optional. Prefilling userData (and destination hints) reduces friction for the requester — see User data.

The payer experience is a separate link with flow: "fund-request". Partners sometimes mint that link themselves when the request payload is already known — see Fund request.

Lifecycle and webhooks

After the requester finishes, the platform mints a fund-request link for the sender. When the sender pays, you receive operation.created (with requestId when applicable) and later a terminal operation.completed / failed / cancelled. Full journey (including legacy Request API): Request money lifecycle.

Next steps

Fund request

Payer fulfills the ask.

Request money lifecycle

Ask → fund-request → operation.

Create links

Shared envelope and discriminators.

Send flow Fund request flow

Getting Started

Request API

Concepts

Integration

Flows

Webhooks

Operations

Overview

Create example

Lifecycle and webhooks

Next steps

Fund request

Request money lifecycle

Create links

​Overview

​Create example

​Lifecycle and webhooks

​Next steps

Fund request

Request money lifecycle

Create links

Overview

Create example

Lifecycle and webhooks

Next steps