Subscription-Based Web Service Development

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.
Development and maintenance of all types of websites:
Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:
Development stages
Latest works
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1161
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1041
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    822
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    847
  • image_website-sbh_0.png
    Website development for SBH Partners
    999
  • image_website-_0.png
    Website development for Red Pear
    451

Web service subscription development

A subscription web service is any product where users pay regularly (monthly, yearly) for access to features, content, or data. Technically: managing subscription lifecycle (trial → active → past_due → cancelled), handling failed payments, anti-churn mechanics, and correct feature access based on status.

Subscription lifecycle

trialing (14 days)
    ↓ automatic payment
active
    ↓ payment failure
past_due → retry 3–4 times → cancelled
    ↓ manual cancellation
cancelled → grace period (until period end)
    ↓
expired

Each transition generates webhook from payment provider. App listens for events and updates subscription status.

Stripe webhook events:

  • invoice.payment_succeeded → activate/renew
  • invoice.payment_failed → set past_due, send email
  • customer.subscription.deleted → deactivate access

Dunning management

Dunning is handling failed payments. Stripe Billing has Smart Retries (ML algorithm selects optimal retry time). Configure in billing settings: 3–4 attempts over 7–14 days.

In parallel, send email notifications with card update link. Stripe Billing provides hosted customer portal — page where client updates payment method.

Free trial period

Two approaches:

  • Trial without card — user doesn't enter card, must add after trial ends. Less friction, lower conversion.
  • Trial with card — card added at signup, charged automatically after trial. Higher conversion, fewer signups.

B2B-SaaS recommends trial with card. B2C and viral products — without card.

Upgrade / Downgrade

Plan change should be instant and account for already-paid period. Stripe handles via proration:

await stripe.subscriptions.update(subscriptionId, {
  items: [{ id: itemId, price: 'price_premium_monthly' }],
  proration_behavior: 'create_prorations',
});

On upgrade — difference for remaining days charged. On downgrade — difference credited.

Anti-churn: retention mechanics

  • Cancellation flow: instead of "Cancel" button — dialog with questions ("Why?"), offer to pause (1–3 months) or discount
  • Email campaigns: series of emails on past_due, on failed trial conversion, at 30/60/90 days after cancellation
  • Win-back offers: special offer for cancelled users

Feature access

Access check should be centralized:

// Gate in Laravel
Gate::define('use-advanced-feature', function (User $user) {
    return $user->subscription?->active()
        && $user->subscription->plan->hasFeature('advanced');
});

// Usage
$this->authorize('use-advanced-feature');

Timeline

Web service with subscription via Stripe (signup, trial, upgrade/downgrade, portal, basic webhooks): 2–3 months. With advanced pricing, teams, dunning, analytics: 3–5 months.