Skip to main content

Webhook attributes

The JSON attributes for Yuno webhooks are listed below:
account_id
string
The unique identifier of the account in Yuno (MAX 64; MIN 36).
type
string
Specifies the notification type.
type_event
string
Specifies the event notification type.
version
string
Specifies the version of the webhook sent. Currently 2.
retry
string
Specifies the number of retries for that notification.
data
string
Specifies the payment (for payment type) or payment method object (for enrollment and other objects).
x-hmac-signature
string
Optional. The HMAC-SHA256 signature sent in the HTTP header for webhook verification when HMAC authentication is enabled.

Examples

Yuno provides several webhooks related to enrollment and payment notifications. Here you will find some examples of data structures related to each event.

Payment Webhook V2

Payment Webhook V1

Chargeback Webhook V2

Chargeback Webhook V1

Enrollment

Payouts

Subscriptions

Onboardings

Refunds

Marketplace Split Transfers

HMAC - Authorization

Payment

Payment Webhook V2

The next JSON object presents an example of a data structure related to a payment event from Webhook V2.
Webhook payloads for events corresponding to a bank transfer payment method include payment.payment_method.payment_method_detail.bank_transfer.bank_id. The field mirrors the bank_id sent in the original payment request and is omitted when no bank was selected.

Payment Webhook V1

The next JSON object presents an example of a data structure related to a payment event from Webhook V1.
JSON

Chargeback Webhook V2

The next JSON object presents an example of a data structure related to a payment event from Webhook V2.

Chargeback Webhook V1

The next JSON object presents an example of a data structure related to a payment event from Webhook V1.
JSON

Enrollment

Payouts

JSON

Subscriptions

JSON

subscription.active

Sent when a subscription transitions from any other valid status into ACTIVE. Use this event to trigger post-activation processes without polling.
JSON

subscription.pause

Sent when a subscription is paused. Use this event to update the status in your system and pause related services.
JSON

subscription.resume

Sent when a paused subscription is resumed and transitions back to the ACTIVE status.
JSON

subscription.cancel

Sent when a subscription is canceled. Once canceled, the subscription is terminated and cannot be reactivated.
JSON

subscription.complete

Sent when a subscription reaches its end date or total billing cycles and transitions to the COMPLETED status.
JSON

subscription.close_to_renewal

Sent ahead of an upcoming renewal. Timing is controlled by renewal_notification_days on the subscription.
JSON

Renewal charges and failures (no subscription.error)

There is no subscription.error webhook. Yuno does not emit a subscription event when a renewal charge fails. Renewal-charge outcomes — successful rebills and failed/declined attempts — are delivered as payment.purchase webhooks tied to the subscription, with the result carried in the status/sub_status fields. Subscribe to payment.purchase to track renewal results. $0/trial cycles emit no payment webhook.
The renewal charge itself is always signaled by a payment.purchase webhook, never by a subscription webhook. The payments array inside the subscription object is currently always empty in webhook payloads. subscription.active is sent once (at billing_cycles.current = 2), not on every renewal.

Onboardings

Example

Marketplace Split Transfers

split_transfer.succeeded

split_transfer_reverse.succeeded

Refunds

Example

HMAC - Authorization