Skip to main content

Overview

Yuno Subscriptions enable you to set up recurring billing that automatically collects payments from your customers on a defined schedule. Whether you are running a SaaS platform, streaming service, or membership program, subscriptions handle the complexity of recurring payments, including lifecycle management, payment retries, and dunning.

Key Capabilities

CapabilityDescription
Flexible billing cyclesDaily, weekly, monthly, quarterly, or annual intervals
Automatic collectionPayments are charged automatically on schedule
Smart retriesFailed payments are retried with configurable schedules
Lifecycle managementCreate, pause, resume, cancel, and upgrade subscriptions
WebhooksReal-time notifications for payment and subscription events
Multi-currencyBill in the customer’s local currency

How Subscriptions Work

1

Enroll Payment Method

The customer provides a payment method (card, wallet, etc.) which is securely tokenized and stored for recurring use.
2

Create Subscription

You create a subscription via the API, specifying the billing amount, interval, and start date.
3

Automatic Billing

Yuno automatically charges the enrolled payment method on each billing cycle.
4

Handle Outcomes

Successful payments advance the subscription. Failed payments trigger smart retries and dunning flows.

Subscription Lifecycle

StatusDescription
CREATEDSubscription created but first payment not yet collected
ACTIVESubscription is billing normally
PAST_DUEPayment failed, retries in progress
PAUSEDBilling suspended, can be resumed
CANCELLEDSubscription terminated (by merchant, customer, or dunning)
EXPIREDSubscription reached its end date
A subscription enters PAST_DUE status after a payment failure. Smart retries will attempt to collect the payment according to your retry schedule. If all retries are exhausted, the subscription moves to CANCELLED unless you intervene.

Webhook Events

Subscribe to these events for real-time subscription updates:
EventTrigger
subscription.createdNew subscription created
subscription.activatedFirst payment collected successfully
subscription.payment.successRecurring payment succeeded
subscription.payment.failedRecurring payment failed
subscription.past_dueSubscription entered past due status
subscription.cancelledSubscription cancelled
subscription.pausedSubscription paused
subscription.resumedSubscription resumed from pause
Always implement webhook handlers for subscription.payment.failed and subscription.past_due to manage customer communication and access control.

Next Steps

Create a Subscription

Set up your first recurring billing flow with API examples.

Smart Retries

Configure automatic retry schedules and dunning for failed payments.