User Service
The User Service is the central authority for user identity, membership, and account lifecycle within the FloatMe platform. It owns user profile data, membership tiers, phone numbers, tags, KYC, and MLA compliance records.
What This Service Owns
| Domain | Responsibility |
|---|---|
Users |
User profiles, status lifecycle (PROCESSING → ACTIVE → PAUSED/BANNED/INVESTIGATE) |
Memberships |
Membership tier records, upgrades, downgrades, pause/unpause, cancellation, reactivation |
Phone Numbers |
Phone number storage and deduplication |
Tags |
Arbitrary key/value attributes attached to a user account |
KYC |
Know Your Customer session storage and management via Transactions service |
MLA |
Military Lending Act covered borrower lookups via Experian |
Consent |
User consent agreement records |
Lambda Functions
| Function | Trigger | Purpose |
|---|---|---|
|
API Gateway (IAM auth) |
Primary REST API — CRUD for users, memberships, phone numbers, tags, KYC, MLA, consent |
|
Kinesis ( |
Reacts to payment events — bans users on chargeback |
|
Kinesis ( |
Reacts to subscription events — handles pause and resume flows |
|
DynamoDB Streams |
Publishes user and membership change events to the outbound Kinesis stream |
|
SQS ( |
Cleans up cancelled accounts — removes Plaid items, blocks Auth0, schedules Array cleanup |
External Dependencies
| Service | Role |
|---|---|
Auth0 |
User authentication, MFA enforcement, account blocking |
Subscription Service |
Manages recurring billing subscriptions; source of pause/resume events |
Payment Service |
Processes one-time charges (e.g. upgrade proration); source of chargeback events |
Growthbook |
Membership tier configuration and pricing |
Experian |
MLA covered borrower lookups |
Transactions Service |
Plaid item management, KYC session storage; queried during user activation and cleanup |
Float Service |
Outstanding float balances checked during cancellation and reactivation |
Underwriting Service |
Recalculates underwriting on reactivation |
Documentation
See Architecture for the system context diagram and a full breakdown of components. See API Specification for the full OpenAPI spec.