M2M flow

When to use m2m

m2m is a flow slug for partners who already hold KYC and/or payout data and want to prefill the widget. It is one productized flow in the RaaS Widgets catalog — not the name of the platform.

More prefills → less user friction. Incomplete CIP data can trigger data requests. Read the trade-off in User data.

Prefill 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": "user_12345",
    "flow": "m2m",
    "expiresInMinutes": 120,
    "config": {
      "userData": {
        "name": {
          "firstName": "Ana",
          "secondName": "Maria",
          "lastName": "Garcia",
          "secondLastName": "Lopez"
        },
        "idNumber": "GALO900515HDFRPN09",
        "idType": "CURP",
        "dob": "1990-05-15",
        "paymentMethod": {
          "type": "bank_account",
          "bankAccount": {
            "country": "MX",
            "accountNumber": "012345678901234567"
          }
        }
      }
    }
  }'

You can send partial userData (for example name only) and fulfill the rest via webhooks. Prefer legal names and YYYY-MM-DD dates so CIP matches government records.

Friction tip

Prefill level	Typical UX
Full CIP + payout	Confirm and send
Name only	Short form / data request for ID & DOB
`referenceId` only	Full CIP in widget

For new send products without prefills, prefer smart.

Next steps

User data

Friction vs integration effort.

Data requests

Fulfill missing CIP fields.

Smart flow Send flow

Getting Started

Request API

Concepts

Integration

Flows

Webhooks

Operations

When to use m2m

Prefill example

Friction tip

Next steps

User data

Data requests

​When to use m2m

​Prefill example

​Friction tip

​Next steps

User data

Data requests

When to use m2m

Prefill example

Friction tip

Next steps