Subscription Service
The Subscription Service is the authority for subscription billing within the FloatMe platform. It owns the full subscription lifecycle — activation and plan management, scheduled and event-driven collections, ACH outcome processing, membership event handling, and pre-subscription notifications.
What This Service Owns
| Domain | Responsibility |
|---|---|
Subscriptions |
Subscription records and lifecycle — activation, status transitions, upgrade/downgrade, reactivation, and ban |
Collections |
Scheduled, retry, pause, and webhook-driven collection engine with ML-based decisions and distributed locking |
Memberships |
Kinesis-driven membership lifecycle event processing from the User Service |
Notifications |
Three-day pre-subscription notifier delivered via Iterable |
ACH Callbacks |
ACH payment outcomes from the payments stream mapped to billing status transitions |
Administration |
User bans, QA subscription creation, and admin notes via the Admin Service |
Events |
Billing activity changes published to the |
Documentation
-
Architecture — system context, component inventory, external dependencies
-
Infrastructure — Lambda config, queues, streams, schedules, secrets
-
API Specification — OpenAPI spec (Swagger UI)
-
DynamoDB Tables — schemas, access patterns, enums, locks
-
Subscription Lifecycle — status machine and lifecycle flows
-
Collections Engine — scheduled, retry, pause, and webhook collection flows
-
Memberships — membership event consumer
-
ACH Processing — ACH callback handling
-
Notifications — pre-subscription notifier
-
Events — published and consumed event contracts
-
Feature Flags — GrowthBook flag index