Subscriptions on any PSP.
Recover what fails.
Plans, trials, retries, lifecycle and usage-based billing, executed on the payment stack you already run with Yuno. Configure it from the Dashboard or the API.
Orchestration under every cycle
Every renewal is routed like a first purchase: routing rules, PSP fallback, vaulted credentials and local rails. A retry can go through a different PSP than the one that declined.
Recovery you can see and steer
Approval per billing cycle is a number in your Dashboard. Three retry strategies per plan, an A/B split, hard-decline stop and a retry cap, set by your billing team, not your developers.
Merchant-facing, always
Yuno bills. Your systems read the webhook and decide what the customer can use. No end-customer portal to adopt, no checkout to replace.
— Plans, trials, meters and retry rules, defined once in the Dashboard or the API. Yuno charges every cycle across the PSPs it already routes for you.
Launch anywhere.
Multi-phase plans: a trial, an intro price, then the regular price, each with its own length and frequency. Free trials or a verification charge. A price per country on every phase, so euros in Europe and reais in Brazil never drift with FX.
Billing: monthly · Retry strategy: SMART
Recover with Smart Retries.
Smart Retries learns from the approvals and declines Yuno processes across issuers, payment methods and countries, and picks the moment each retry is most likely to clear. Hard declines stop on the spot, a cap protects your scheme standing, and the retry can go through a different PSP. Run it A/B against your own schedule from the Dashboard and see the difference on your traffic.
Bill by usage.
Attach a meter to the plan: tokens, deliveries, GB, seats. Included credits, then per-unit, package or tiered pricing. Send usage events with an idempotent ID; the overage is added to the next cycle charge, same subscription, same webhook, same retries.
Usage events
POST /usage event_id: evt_8f21a0… +120
POST /usage event_id: evt_8f21a1… +75
POST /usage event_id: evt_8f21a2… +240
idempotent by event_id
Charge how they pay.
Cards, Apple Pay, Google Pay, PayPal and Pix Automático in the same subscription object, with each rail's recurring rules handled inside the engine. Create the subscription and take the first payment in one call from your own checkout, or start it from a Yuno payment link with zero integration.
Charged
Charged
Charged
Charged
ChargedKeep Stripe Billing.
Not migrating your billing? Keep Stripe Billing as the engine and let Yuno run every charge with multi-PSP routing and local rails. Or keep your Stripe integration as it is and point it at Yuno's Stripe-compatible endpoint.
Stripe Billingyour billing engineKeep vaulted cards current so a renewal never fails on an expired or replaced card.
Recurring charges on credentials you own, portable to any PSP you route to.
Route every renewal, and every retry, to the PSP most likely to approve it.
Runsubscriptionsonthestackyoualreadyhave.
Runsubscriptionsonthestackyoualreadyhave.
Talk to our team about plans, retries and a pilot on your traffic.