Skip to main content
POST
/
v1
/
banking
/
transfers
Webhook Notifications
curl --request POST \
  --url https://{merchant_base_URL}/v1/banking/transfers \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": "xfer_cc0e8400-e29b-41d4-a716-446655440000",
  "destination_account_id": "acct_aa0e8400-e29b-41d4-a716-446655440000",
  "account_id": "550e8400-e29b-41d4-a716-446655440000",
  "provider": {
    "account_id": "col_bank_account_789",
    "transfer_id": "col_incoming_xyz456"
  },
  "status": "COMPLETED",
  "direction": "INCOMING",
  "sender": {
    "account_number_last_4": "5678",
    "routing_number": "987654321",
    "account_name": "External Company LLC",
    "bank_name": "Bank of America"
  },
  "amount": {
    "value": 2500,
    "currency": "USD"
  },
  "payment_rail": "ACH_STANDARD",
  "description": "Payment for services",
  "created_at": "2026-02-01T14:30:00Z",
  "updated_at": "2026-02-01T14:30:00Z"
}
'
{
  "received": true
}
Yuno sends incoming transfer notifications to your endpoint at {merchant_base_URL}/v1/banking/transfers. Your endpoint must return a 200 OK response with {"received": true}. Notifications include sender details, transfer amount, payment rail, and status. Yuno retries on 5xx responses and timeouts with exponential backoff. See Webhook events for the complete list of Banking Connectivity webhook event types.

Body

application/json
​
id
string

The unique identifier of the transfer (prefixed xfer_).

Example:

"xfer_cc0e8400-e29b-41d4-a716-446655440000"

​
destination_account_id
string

The id of the destination Banking Connectivity account that received the incoming transfer.

Example:

"acct_aa0e8400-e29b-41d4-a716-446655440000"

​
account_id
string

The merchant's Yuno account identifier.

Example:

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

​
provider
object

Provider-side identifiers.

​
status
enum<string>

The transfer status.

Available options:
PENDING,
COMPLETED
Example:

"COMPLETED"

​
direction
enum<string>

The transfer direction. Incoming transfer webhooks always have INCOMING.

Available options:
INCOMING
Example:

"INCOMING"

​
sender
object

Information about the external sender.

​
amount
object

The transfer amount.

​
payment_rail
enum<string>

The payment rail used for the transfer.

Available options:
ACH_STANDARD,
ACH_SAME_DAY,
WIRE,
RTP,
FPS,
CHAPS,
BACS,
NPP,
PAYTO,
BPAY
Example:

"ACH_STANDARD"

​
description
string

The transfer description.

Example:

"Payment for services"

​
created_at
string

The timestamp when the transfer was created (ISO 8601).

Example:

"2026-02-01T14:30:00Z"

​
updated_at
string

The timestamp when the transfer was last updated (ISO 8601).

Example:

"2026-02-01T14:30:00Z"

Response

200 - application/json