Billing & Subscription Quotas Flow
Understand the core mechanics, queues, and logic routines running on our servers when processing this module.
System Execution Pipeline
Below is the step-by-step sequence of events executed by our background workers.
Select Subscription
The user selects a plan (Single, Basic, Multi, or Unlimited).
Stripe Checkout
The browser redirects to a secure Stripe Checkout page to complete payment.
Webhook Response
Stripe sends a secure webhook payload (`checkout.session.completed`) to our API.
Quota Update
The workspace is upgraded, and limits on domains and emails are updated.
Developer & Architect Notes
Technical Architecture
This module operates as a stateless service hosted across horizontally scalable server nodes. Distributed state coordinates through highly optimized Redis transactions to ensure consistency without deadlocks.
Edge Fail-Safe Rules
Critical protocols (like connection failure retries, cool-down timers, and data limits) are verified before outbound dispatches. Failures degrade gracefully, prioritizing list health and preventing blacklisting.
How billing & subscription quotas behaves.
Answers about the execution flow, failure handling and limits of this module.
How does billing work?
Subscriptions are handled through Stripe and billed monthly in advance. You can upgrade, downgrade or cancel yourself from the billing portal in your dashboard.
Can I pay in Pakistani Rupees?
Yes. Checkout supports both USD and PKR, and you choose your currency when subscribing.
What happens if I try to exceed my plan limits?
Limits on domains, sending accounts and active campaigns are enforced in the API, so you are prompted to upgrade rather than being charged automatically for overage.
What happens to my data if I cancel?
You keep access until the end of the period you have paid for. After closure, lists, campaigns and analytics are removed; suppression hashes are retained so that people who opted out are never contacted again by a later account.