Webhook Notifications
Receive incoming transfer notifications with sender, amount, rail, and status details
{merchant_base_URL}/v1/banking/transfers. Your endpoint must return a 200 OK response with {"received": true}. Yuno sets the merchant base URL for banking webhooks on request, so ask your Yuno contact to register or change it.
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.Authorizations
Public API key from Dashboard > Settings > API Keys
Private secret key (server-side only)
Body
The unique identifier of the transfer (UUID, 36 characters).
"cc0e8400-e29b-41d4-a716-446655440000"
The id of the destination Banking Connectivity account that received the incoming transfer.
"aa0e8400-e29b-41d4-a716-446655440000"
The merchant's Yuno account identifier.
"550e8400-e29b-41d4-a716-446655440000"
Provider-side identifiers.
The transfer status.
PENDING, COMPLETED "COMPLETED"
The transfer type. Incoming transfer webhooks always have INCOMING.
INCOMING "INCOMING"
Information about the external sender.
The transfer amount.
The payment rail used for the transfer.
ACH_STANDARD, ACH_SAME_DAY, WIRE, RTP, FPS, CHAPS, BACS, NPP, PAYTO, BPAY "ACH_STANDARD"
The transfer description.
"Payment for services"
The timestamp when the transfer was created (ISO 8601).
"2026-02-01T14:30:00Z"
The timestamp when the transfer was last updated (ISO 8601).
"2026-02-01T14:30:00Z"