Deferred payout

Overview

Deferred payout splits the journey:

Sender funds now on deferred-payout-origination
Recipient claims later on payout-claim

Use this when the beneficiary should receive funds after the sender has already committed, without both parties completing the same session.

Originate (sender)

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": "sender_user_123",
    "flow": "deferred-payout-origination",
    "expiresInMinutes": 120,
    "language": "es"
  }'

Optional config can prefill user data and corridor pins (same general shape as send). See OpenAPI for the current schema.

Claim (recipient)

payout-claim is the recipient/claim side. Platforms often mint claim links automatically after origination. You can also create flow: "payout-claim" via POST /partner/links when your integration owns claim distribution — see OpenAPI (CreatePayoutClaimLinkDto) for required fields such as origination or send-commitment inputs.

Listen for standard Partner webhooks (operation.created, operation.cancelled, …) as the claim binds into an operation.

Resource	Purpose
`POST /partner/links`	Mint origination (and optionally claim) links
Partner portal deferred payouts	Ops list / cancel (Clerk session)
Compat APIs	Brief note under Pre-quote lite

Next steps

Flows catalog

How flows fit in the platform.

Operations

Query operations after claim.

Cash deposit flow Webhooks overview

Getting Started

Request API

Concepts

Integration

Flows

Webhooks

Operations

Overview

Originate (sender)

Claim (recipient)

Next steps

Flows catalog

Operations

​Overview

​Originate (sender)

​Claim (recipient)

​Related Partner resources

​Next steps

Flows catalog

Operations

Overview

Originate (sender)

Claim (recipient)

Related Partner resources

Next steps