Smart Retries. When a subscription payment fails, Yuno automatically retries based on the
max_retries configuration. The retry schedule uses intelligent spacing to maximize approval rates. See Smart Retries for details.Object Fields
The unique identifier of the subscription (UUID).Example:
sub_7a1b2c3d-4e5f-6789-abcd-ef0123456789Current subscription status. Transitions are managed automatically based on payment outcomes and merchant actions.Values:
ACTIVE, PAUSED, CANCELLED, EXPIRED, PAST_DUEACTIVE. Subscription is live and payments are being collected on schedule.PAUSED. Temporarily halted by the merchant; no charges until resumed.CANCELLED. Permanently terminated; cannot be reactivated.EXPIRED. Reached theend_datenaturally.PAST_DUE. Most recent payment failed; retries are in progress.
ACTIVEThe recurring charge amount.
The billing frequency unit. Combined with
interval_count to define the billing cycle (e.g., MONTHLY with interval_count: 1 charges once per month).Values: DAILY, WEEKLY, MONTHLY, YEARLYExample: MONTHLYThe number of interval units between each billing cycle. For example,
interval: WEEKLY with interval_count: 2 charges every two weeks.Example: 1ID of the associated customer. Links to the Customer Object.Example:
c9d0e1f2-3a4b-5c6d-7e8f-9a0b1c2d3e4fID of the vaulted payment method used for recurring charges. Must be a tokenized card or payment method enrolled via the Enrollment flow.Example:
pm_d4e5f6a7-b8c9-0123-4567-89abcdef0123ISO 8601 date of the next scheduled charge.
null when status is CANCELLED, EXPIRED, or PAUSED.Example: 2026-04-10T00:00:00.000ZISO 8601 timestamp of when the subscription began (first charge date).Example:
2026-03-10T00:00:00.000ZISO 8601 timestamp of when the subscription is set to expire.
null for open-ended subscriptions.Example: 2027-03-10T00:00:00.000ZNumber of retry attempts already made for the current billing cycle. Resets to
0 after a successful payment.Example: 0Maximum number of retry attempts before the subscription transitions to
CANCELLED. Configurable at creation time.Example: 3Custom key-value pairs set by the merchant. Up to 50 keys, each key max 40 characters, each value max 500 characters.
ISO 8601 timestamp of when the subscription was created.Example:
2026-03-10T14:00:00.000ZISO 8601 timestamp of the last subscription update.Example:
2026-03-10T14:00:01.000ZExample
Related Endpoints
- Create Subscription.
POST /v1/subscriptions - Get Subscription.
GET /v1/subscriptions/{subscription_id} - Update Subscription.
PATCH /v1/subscriptions/{subscription_id} - Pause Subscription.
POST /v1/subscriptions/{subscription_id}/pause - Resume Subscription.
POST /v1/subscriptions/{subscription_id}/resume - Cancel Subscription.
POST /v1/subscriptions/{subscription_id}/cancel - Retry Subscription.
POST /v1/subscriptions/{subscription_id}/retry
Related Concepts
- Subscriptions Overview. How recurring payments work in Yuno
- Smart Retries. Automated retry logic and configuration