Skip to main content
POST
Create Standalone Transfer
Create a transfer independently of a payment. The direction field determines which account sends the funds.
Recipient-to-platform transfers are not generally available. Use this direction only after Yuno confirms account enablement and provider support.
Direction is saved at creation and returned in the response, GET, and transfer notifications. It cannot be changed after creation. Reusing the same account and idempotency key with a different direction is rejected; omitted and explicit PLATFORM_TO_RECIPIENT represent the same direction. Invalid strings (including empty or incorrectly cased values), objects, arrays, numbers, and booleans return 400 INVALID_PARAMETERS. A recipient-to-platform request with a provider other than STRIPE returns 400 INVALID_PARAMETERS before the enablement check. A valid recipient-to-platform request for an account without access returns 400 DIRECTION_NOT_ENABLED, before the idempotency direction check. A recipient-to-platform transfer cannot be reversed. To return a separately collected fee, create a new platform-to-recipient transfer.

Authorizations

PUBLIC-API-KEY
string
header
required
PRIVATE-SECRET-KEY
string
header
required

Headers

X-Idempotency-Key
string
required

Unique key for request idempotency.

Body

application/json
account_id
string
required

The unique identifier of the account.

recipient_id
string<uuid>
required

The target recipient identifier.

provider_id
string
required

The payment provider code to use (e.g., adyen, stripe).

amount
object
required
description
string

A human-readable description for the transfer (3-255 chars). This is sent to the provider.

merchant_reference
string

Merchant's unique identifier for idempotency and tracking.

metadata
object[]
direction
enum<string> | null
default:PLATFORM_TO_RECIPIENT

Direction of the transfer. Omitted or null defaults to PLATFORM_TO_RECIPIENT. RECIPIENT_TO_PLATFORM is supported only for eligible STRIPE accounts. RECIPIENT_TO_PLATFORM is not generally available. Use it only after Yuno confirms account enablement and provider support.

Available options:
PLATFORM_TO_RECIPIENT,
RECIPIENT_TO_PLATFORM,
null

Response

Created

id
string
Example:

"TRF_7kB2mQ9xPnL4vR"

direction
enum<string>

The immutable direction saved when the transfer was created. Existing transfers return PLATFORM_TO_RECIPIENT. It cannot be changed after creation.

Available options:
PLATFORM_TO_RECIPIENT,
RECIPIENT_TO_PLATFORM
Example:

"PLATFORM_TO_RECIPIENT"

recipient_id
string<uuid>
Example:

"550e8400-e29b-41d4-a716-446655440000"

amount
object
status
string
Example:

"SUCCEEDED"

reason
string
Example:

"ORDER_CANCELLED"

description
string
Example:

"Weekly marketplace earnings"

merchant_reference
string
Example:

"TRANSFER-2026-02-15-001"

metadata
object[]
provider_data
object
created_at
string<date-time>
Example:

"2026-02-16T10:30:00Z"

updated_at
string<date-time>
Example:

"2026-02-16T10:30:15Z"

completed_at
string<date-time>
Example:

"2026-02-16T10:30:15Z"

provider
string | null
Example:

null

transactions
object[]