SimplifyLabs fires webhooks for every subscription state change. When a renewal payment confirms, a subscription.renewed webhook fires to your configured endpoint—your SaaS listens for this event and extends the subscriber's access period. When a renewal is overdue and the grace period expires, a subscription.suspended webhook fires and your SaaS downgrades or suspends the account. This webhook-driven model means your subscription state in-product always reflects the actual payment state without your SaaS polling SimplifyLabs for subscription status. The integration pattern is identical to how you'd integrate Stripe webhooks for subscription management—the concept is the same, the payment method is different.

Dunning for crypto subscriptions works differently from card billing because there's no stored payment method to charge automatically—subscribers need to actively send a new payment. SimplifyLabs dunning handles this by: sending a renewal invoice to the subscriber's registered email or webhook delivery channel at the billing date, firing reminder webhooks at configurable intervals (1 day, 3 days, 7 days overdue—whatever your policy specifies), maintaining access through a grace period you define, and ultimately firing a final suspension webhook when the grace period ends without payment. Your SaaS uses these webhook events to trigger in-app notifications, emails, or feature restrictions that communicate urgency to the subscriber. Dunning effectiveness is tracked in the SimplifyLabs dashboard so you can optimize timing and messaging over time.

SimplifyLabs runs alongside your existing card billing system, so subscribers can be migrated individually or offered crypto as an upgrade option. The simplest migration flow: at renewal time, offer the subscriber the option to pay their next invoice in crypto. Generate a SimplifyLabs invoice for their renewal amount, email or present the payment link, and on confirmation, cancel their card billing subscription and activate the SimplifyLabs subscription. If they prefer to stay on card, nothing changes. Many SaaS companies incentivize migration to crypto billing with a discount or bonus—the lower processing fees often make a 5% crypto discount economically neutral or positive for the SaaS.

Yes. SimplifyLabs Subscriptions API supports multiple plan definitions with different pricing, feature sets, and billing intervals. Each plan is a discrete configuration with its own subscription terms. Add-on charges are handled as supplemental invoices generated via the Payments API alongside the base subscription. Plan-level webhooks fire with the plan identifier so your SaaS knows which feature set to activate for each subscriber. Mid-cycle plan upgrades trigger prorated invoices calculated by SimplifyLabs based on the configured plan prices and the remaining days in the current period. If your pricing structure involves complex configurability beyond standard tiers, contact our integration team—we've built custom billing logic for enterprise SaaS pricing models.

SimplifyLabs provides subscription-level revenue reporting with MRR calculations, new MRR from new subscriptions, churned MRR from cancellations, expansion MRR from upgrades, and contraction MRR from downgrades. All figures are available in fiat-equivalent values (using confirmed conversion rates) so your MRR reporting is in consistent fiat terms regardless of which cryptocurrency subscribers used. Reports are available via dashboard, API, or scheduled CSV export. The export format maps directly to standard MRR analytics tools like ChartMogul and ProfitWell—most SaaS finance teams are importing SimplifyLabs data into their MRR dashboard within hours of going live.

Crypto subscription refunds are processed as new outgoing transactions from your SimplifyLabs account to the subscriber's wallet address. You initiate the refund from the dashboard or via API, specify the amount (full or partial), and SimplifyLabs processes the outgoing transaction. The refund is logged against the original subscription invoice for audit purposes. For refund policy implementation—such as pro-rated refunds for annual subscriptions cancelled mid-year—SimplifyLabs calculates the pro-rated amount based on your configured refund policy and generates the refund transaction accordingly. All refund activity is visible in your subscription reporting with the original payment and refund linked for clear revenue recognition.

Stripe and SimplifyLabs serve complementary use cases for SaaS billing. Stripe excels for card-billing subscribers with stored payment methods, automatic retries, and a mature ecosystem of SaaS billing tooling built around it. SimplifyLabs excels for international subscribers in high-card-decline markets, crypto-native customers who prefer not to provide card details, and markets where card subscription renewals fail at rates that cause significant involuntary churn. Most SaaS companies run both in parallel: Stripe for the majority of subscribers, SimplifyLabs for markets and customer segments where Stripe doesn't perform reliably. The integration patterns are similar—API-driven plan management, webhook-driven access control—which makes running both relatively straightforward for engineering teams already familiar with Stripe.