75 KiB
Round 3 — Investor subscriptions & payments
Attach together with
design-brief.md. The brief defines the design system, shared patterns and status vocabulary; this file holds the full acceptance criteria and exact Farsi copy.
Checkout is a single screen, desktop 480px max. Money figures use tabular numbers everywhere.
Deliver in this round
- Checkout «خرید اشتراک»: tiers, promotions, referral code states, frozen CTA, price-changed modal, waitlist modals, terms link
- Payment return: processing, success toast, pending, failure
- Channel header after joining the waitlist and while payment is pending
- داشبورد → اشتراکها: active cards with expiry escalation, expired section, suspended-creator card with refund action, empty state
- Renew and reactivate bottom sheets with date preview
- تراکنشها list, filters and detail sheet
- Notification center
- شرایط اشتراک terms page (text in the U9 comment below)
For every screen: mobile and desktop, RTL, real Farsi copy from below, and all listed states.
Stories included
- U9 — Investor: Subscribe to a Creator (ClickUp status: ready for development)
- U10 — Investor: Immediate Access After Payment (ClickUp status: ready for development)
- U11 — Investor: Automatic Access Revocation on Expiry (ClickUp status: ready for development)
- U2 — Investor Active Subscriptions View (ClickUp status: in review)
- U3 — Investor Subscription Renewal & Reactivation (ClickUp status: ready for development)
- U4 — Investor Transaction History (ClickUp status: ready for development)
- U5 — Investor Subscription Expiry Notifications (ClickUp status: ready for development)
U9 — Investor: Subscribe to a Creator
U9 — Investor: Subscribe to a Creator Story: As an investor, I want to subscribe to a creator using a domestic payment method in a simple checkout flow so that I can access premium content without friction. Scope note: This story owns the subscription checkout flow end-to-end — from tapping Subscribe through to payment completion, including referral-code validation and the waitlist path. Pricing configuration is owned by C7; renewal and reactivation by U3; post-payment access by U10; admin payment oversight by A9. ⚠️ Forward dependency note: Referral codes and their capacity limits are admin-managed in the database (principle stated in U1 Section 7). This story specifies how an investor encounters and uses them; admin tooling for managing codes is not yet written. Acceptance Criteria:
- Entry Points & Access Happy Path: Checkout is initiated by tapping the اشتراک CTA, available from: The creator profile header on the public channel page (U6 Section 5) The creator mini profile header on a standalone post page (C4b Section 2) A locked premium post's inline CTA (C5 Section 3, U7 Section 3) Tapping opens the checkout screen (Section 2) Edge Cases: Logged-out visitor tapping Subscribe → redirected to the unified auth entry flow with the current page preserved as the return destination (U1 Sections 5–6). A single ورود/ثبتنام CTA is shown. Checkout is not reachable without authentication, and the subscription is not auto-initiated on return — the investor lands back on the channel and taps Subscribe deliberately Active subscriber → the Subscribe CTA is replaced with the subscription status indicator (U6 Section 5); checkout is not reachable Payment pending (در حال بررسی) → the CTA is replaced with a frozen pending indicator (Section 5); checkout is not reachable until the payment resolves Creator viewing their own channel → no Subscribe CTA is shown Suspended creator → the channel page itself is unavailable (A2), so checkout is unreachable Pending or Rejected creator → their channel is not publicly discoverable; checkout is unreachable
- Checkout Screen — Structure Happy Path: Checkout is a single screen — no multi-step wizard, no intermediate gate. It contains, in order: Section A — Creator identity Avatar, username, verified badge — confirms who is being paid before money moves Section B — Invite-only explanation A short note explaining that subscriptions are invite-only and capacity-limited during the beta, and that referral codes come from the creator Section C — Tier selection Every enabled tier (per C7 Section 2), each showing: Tier label (ماهانه · سهماهه · ششماهه · سالانه) Total price for the full duration Per-month equivalent — essential for comparing a ۳,۳۶۰,۰۰۰ yearly against a ۴۰۰,۰۰۰ monthly; an investor cannot reason about tiers without it Strike-through of monthly × duration where the tier's total is lower, making the saving visible تخفیف badge and promotional pricing where a promotion is active (Section 3) Single-select — exactly one tier at a time; none pre-selected Section D — Referral code A single text field for the code Section E — Payment Total amount payable پرداخت CTA — frozen until both a tier is selected and the code field is non-empty (Section 4) Edge Cases: Disabled tiers do not appear at all — not greyed, not listed A creator offering only ماهانه shows a single tier; selection is still explicit, not auto-selected, so the investor consciously confirms what they're buying Checkout reflects pricing at the moment the screen loads. If the creator changes pricing while the investor is mid-checkout, validation at payment time (Section 5) catches the mismatch Farsi copy: Screen heading: خرید اشتراک Invite-only note: اشتراک در این کانال بهصورت دعوتنامهای و با ظرفیت محدود است. برای دریافت کد دعوت با کریتور در ارتباط باشید. Tier section label: دوره اشتراک Per-month equivalent: معادل {amount} تومان در ماه Referral code field label: کد دعوت Referral code placeholder: کد دعوت را وارد کنید Total payable label: مبلغ قابل پرداخت Payment CTA: پرداخت
- Promotional Pricing Display Happy Path: Where a tier has an active promotion (C7 Section 6), that tier displays: The standing tier price struck through — not the monthly × duration comparison The promotional price as the live figure, in both total and per-month terms A تخفیف badge showing the discount percentage The monthly-derived comparison recedes in this state — one clear "before" figure, never two competing struck-through numbers Time-remaining display — threshold-based:
Time remaining Display More than 48 hours تا {end_date} — a plain date 48 hours or less Live countdown: {n} ساعت باقی مانده Less than 1 hour کمتر از ۱ ساعت باقی مانده Indefinite promotion No time indication at all Rationale: a plain date is factual and useful for a purchase decision — an investor weighing a yearly commitment benefits from knowing a deadline exists, even a distant one. A countdown is pressure, so it appears only when the deadline is genuinely near. Showing "۱۲۰ ساعت باقی مانده" would be manufactured urgency, which erodes trust in a credibility-first product. Edge Cases: Promotions apply to new subscriptions only (C7 Section 6), which is precisely what this flow is — so every promotion visible here is applicable A promotion expiring between screen load and payment is caught by validation at payment time (Section 5) — the investor is informed rather than silently charged a different amount The countdown updates live while the screen is open; it does not require a refresh Farsi copy: Discount badge: {n}٪ تخفیف Promotion end date (>48h): تا {end_date} Countdown (≤48h): {n} ساعت باقی مانده Countdown (<1h): کمتر از ۱ ساعت باقی مانده 4. CTA Gating & Code Validation Happy Path: The پرداخت CTA is frozen (opacity: 0.4, cursor: not-allowed) until both conditions are met: A tier is selected The referral code field is non-empty Soft validation on blur: when the investor moves focus off the code field, a quiet inline check runs. A mistyped code is caught immediately rather than after they've spent time comparing tiers Authoritative validation on tap: tapping پرداخت re-validates server-side before any redirect. This check is definitive — capacity can change between blur and tap Edge Cases: Blur validation is advisory only — it never unfreezes or blocks the CTA on its own; the tap-time check governs If blur validation cannot complete (network hiccup), it fails silently — the investor is not blocked, and tap-time validation handles it Code validation is case-insensitive Changing the selected tier after entering a code does not re-trigger validation — the code grants access to the creator's channel, not to a specific tier Error States (code field, on blur or tap): Invalid or inactive code → inline error; the investor stays on the screen with selections intact Code belongs to a different creator → treated as invalid, with the same generic message. No information is leaked about which creator a code belongs to Capacity full → not an error; triggers the waitlist flow (Section 6) Farsi copy: Invalid code error: کد دعوت واردشده معتبر نیست. Code valid confirmation (on blur): کد دعوت معتبر است. ✓ Frozen CTA tooltip: برای ادامه، یک دوره اشتراک انتخاب کنید و کد دعوت را وارد کنید. 5. Payment Flow Happy Path: On tapping پرداخت with a valid code and available capacity, the investor is redirected to ZarinPal On successful payment, ZarinPal returns the investor to the platform Access is granted only after server-side confirmation of the payment callback — never on client-side redirect alone The investor lands on the creator's channel page with premium content unlocked, and a success toast confirms the subscription (full post-payment behaviour owned by U10) Price changed between screen load and payment: Payment is halted before any redirect — the investor is never charged an amount different from what they saw A modal is shown (not a toast — this is a blocking condition requiring explicit re-confirmation, and a transient message could be missed, letting the investor tap پرداخت again without registering the change) The modal states plainly what changed: the previous price, the new price, and the new total Two actions: تأیید و پرداخت proceeds at the new price; انصراف returns to checkout, which has refreshed to current pricing The same handling applies to a promotion expiring mid-checkout — the standing price is shown and re-confirmation required Pending payment state: Where the ZarinPal callback is not received within a reasonable timeout, the subscription is marked در حال بررسی, the investor is notified, and access is granted once confirmed (mirroring U3 Section 5) While pending, the Subscribe CTA on the creator's channel is replaced with a frozen indicator reading پرداخت در حال بررسی — visible, non-interactive, clearly not an invitation to act. Tapping it shows a brief explanation This deliberately inverts the waitlist decision (Section 6), where freezing is explicitly rejected. The situations are opposite: freezing here prevents an undesirable action (duplicate payment); freezing there would prevent a desirable one (acting fast when capacity opens) The state resolves automatically — confirmed: subscription activates and access unlocks; failed: the CTA returns to اشتراک Edge Cases: ZarinPal is the only payment method in Phase 0. BNPL and installment options (e.g. SnappPay) are deliberately deferred — they add a second integration, reconciliation path, and failure mode without serving the hypotheses Phase 0 exists to test. Revisit in Phase 1 if price resistance appears in creator interviews Capacity filled between screen load and payment → the waitlist flow is shown instead of proceeding (Section 6) The investor's full name (collected in U1 Section 3) is passed to ZarinPal for payment reconciliation Error States: Payment failed or declined at gateway → investor returns to checkout with tier and code preserved; error message shown; retry available Investor abandons the ZarinPal page → no subscription created, no charge; returning to the app leaves them where they were Network failure before redirect → error shown, selections preserved, retry available Farsi copy: Price-change modal heading: قیمت تغییر کرده است Price-change modal body: قیمت این اشتراک از {old_amount} تومان به {new_amount} تومان تغییر کرده است. مبلغ قابل پرداخت: {new_total} تومان Re-confirm CTA: تأیید و پرداخت Cancel CTA: انصراف Payment failure error: پرداخت ناموفق بود. لطفاً دوباره تلاش کنید. Network error: خطا در اتصال. دوباره تلاش کنید. Pending payment status (frozen CTA): پرداخت در حال بررسی Pending payment explanation (on tap): پرداخت شما در حال بررسی است. پس از تأیید، اشتراک شما فعال میشود. 6. Waitlist — Capacity Full Happy Path: When a valid code is submitted but the creator's capacity is full, the investor is shown a waitlist offer rather than an error — their code is legitimate; the room is simply full The offer explains plainly that capacity is currently full and that they can be notified when it opens Two actions: join or decline In both cases, the investor is returned to the creator's channel page — where their interest lives, and where they can still read free content and follow Already on the waitlist: An investor already on this creator's waitlist who reaches this point sees a different message — an acknowledgement rather than an offer, with no join action and a single CTA returning to the channel This is likely a common path, not an edge case: a waitlisted investor receives the capacity-opened notification, taps through, and loses the race to someone faster. The message should read as considerate, not as an error The opt-out remains available from the channel header note, so this is never a dead end Access requirement: The waitlist requires a valid-but-full code — it is not open to anyone without a code Rationale: the code is the creator's invitation. The waitlist is a queue for invited people when the room is full. Opening it to everyone would mean a creator raising capacity for their own audience could have those slots taken by strangers Notification behaviour: The waitlist is a notification subscription, not a queue position — nothing is reserved When the admin raises the referral code's max_uses, all waitlisted investors for that creator are notified simultaneously via in-app notification and SMS. First to act gets the slot The notification persists until the investor either subscribes or opts out — it is not one-shot. Capacity may open, fill instantly, and open again; a single-fire notification would silently drop someone who lost a race through no fault of their own Subscribe CTA after joining — never frozen: Joining the waitlist does not change the Subscribe CTA's state. It stays اشتراک and fully live at all times Rationale: the moment capacity opens is exactly when a waitlisted investor needs to act fastest. Freezing or relabelling their primary action would make them lose the race to someone who never joined the waitlist at all Instead, a small non-blocking note appears beneath the CTA on the channel header confirming they'll be notified, with an inline opt-out Opt-out: The investor can stop receiving waitlist notifications at any time via the inline action on that note Included in Phase 0 rather than deferred because the notification persists — a recurring notification with no way to stop it is a dark pattern. It is also trivially cheap: a boolean on a record that already exists Edge Cases: Subscribing successfully removes the investor from that creator's waitlist automatically An investor may be on multiple creators' waitlists simultaneously — each is independent If the creator is suspended while an investor is waitlisted, notifications for that creator are suppressed until reinstatement; the waitlist entry itself is preserved Farsi copy: Waitlist offer heading: ظرفیت تکمیل است Waitlist offer body: کد دعوت شما معتبر است، اما ظرفیت اشتراک این کانال در حال حاضر تکمیل شده. میتوانید در لیست اطلاعرسانی قرار بگیرید تا بهمحض باز شدن ظرفیت به شما خبر دهیم. Join CTA: به من اطلاع بده Decline CTA: انصراف Join success toast: در لیست اطلاعرسانی قرار گرفتید. Already-waitlisted message: ظرفیت تکمیل است. شما در لیست اطلاعرسانی هستید و بهمحض باز شدن ظرفیت به شما خبر میدهیم. Already-waitlisted CTA: بازگشت به کانال Channel header note (after joining): در صورت باز شدن ظرفیت به شما اطلاع داده میشود. Inline opt-out action: لغو اطلاعرسانی Opt-out confirmation toast: اطلاعرسانی لغو شد. Capacity-opened in-app notification: ظرفیت اشتراک کانال {creator_username} باز شد. برای عضویت اقدام کنید. Capacity-opened SMS: ظرفیت اشتراک کانال {creator_username} در [نام پلتفرم] باز شد. برای عضویت: [لینک به کانال] 7. No Referral Code Happy Path: An investor without a code can still reach and view the full checkout screen — including all tiers, prices, per-month equivalents, and any active promotions The invite-only explanation (Section 2, Section B) tells them access requires a code from the creator The پرداخت CTA remains frozen, since the code field is empty (Section 4) They can leave and pursue a code — the creator's social links are available on the channel header (U6 Section 2), which is where they would realistically ask Rationale for showing prices without a code: a codeless investor who leaves knowing exactly what a subscription costs is far more likely to go ask the creator for one. Hiding pricing behind the gate would mean they'd have to ask for both a code and a price, weakening the creator's own pitch. Edge Cases: Following remains free and ungated (U8) — an investor without a code is never turned away empty-handed; they can follow, read free content, and return when they have a code The waitlist is not available without a valid code (Section 6) 8. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text, per the Stripi-inspired design system All prices, per-month equivalents, totals, and countdowns use font-feature-settings: "tnum" — non-negotiable per the design system's tabular-figures rule, and essential for a countdown where digits change in place Checkout opens as a full-screen view on mobile with a back affordance returning to the originating page Creator identity block sits at the top, separated from tier selection by a {colors.hairline} divider Invite-only explanation renders in {colors.ink-mute} (#64748d), {typography.body-md} — informative, not alarming Each tier renders as a selectable card-feature-light row; the selected tier uses a {colors.primary} (#533afd) border and a filled radio indicator, unselected tiers use {colors.hairline} border Total price renders in {typography.heading-sm}, {colors.ink}; per-month equivalent in {typography.caption}, {colors.ink-mute} — clear hierarchy between what they pay and how it compares Strike-through price renders in {colors.ink-mute} with a line-through, positioned before the live price تخفیف badge uses {colors.ruby} (#ea2261) background with white text, pill-tag-soft style — consistent with C7's treatment, the one place ruby is used affirmatively rather than as an error Promotion end date (>48h) renders in {colors.ink-mute}, {typography.caption} — quiet, factual. The countdown (≤48h) renders in {colors.warning} (#f59e0b) — the platform's designated time-sensitive warning token, consistent with U2's subscription-expiry escalation Referral code field uses text-input style; focus state swaps border to {colors.primary}; valid-code confirmation renders in {colors.primary} with a checkmark پرداخت CTA uses button-primary-pill (#533afd), pinned to the bottom of the screen so it remains reachable while scrolling tiers; frozen state uses opacity: 0.4 with cursor: not-allowed Total payable amount sits directly above the CTA in {typography.heading-sm} — the last thing seen before committing Price-change modal and waitlist offer both present as modals over the checkout screen, not separate pages Frozen pending-payment indicator uses {colors.ink-mute} (#64748d) with opacity: 0.4 and a clock icon — visually distinct from both an active CTA and an error Waitlist note on the channel header renders in {colors.ink-mute}, {typography.caption} — deliberately quiet, never competing with the live Subscribe CTA Error messages render in {colors.ruby} (#ea2261) Minimum touch target for all interactive elements: 44×44px Checkout is mobile-first; desktop centers in a single column with max-width 480px
Latest comment on U9 (content: «شرایط اشتراک» terms page)
شرایط اشتراک --- جایگاه: صفحهای مستقل، با لینک از صفحه پرداخت (U9، بخش ۲) در نزدیکی دکمه پرداخت. بهصورت inline نمایش داده نمیشود — صفحه پرداخت باید روی تصمیم خرید متمرکز بماند و شرایط با یک کلیک در دسترس باشد. ⚠️ نیاز به بررسی حقوقی: این متن، محتوای محصول است که تعهدات پلتفرم را تعریف میکند، نه متن حقوقی بررسیشده. پیش از لانچ باید توسط مشاور حقوقی بازبینی شود — بهویژه بخشهای بازگشت وجه و مسئولیت. --- ۱. اشتراک چیست؟ با خرید اشتراک، به محتوای ویژه (پریمیوم) کانال یک کریتور برای مدت انتخابشده دسترسی پیدا میکنید. دسترسی شما بلافاصله پس از تأیید پرداخت فعال میشود و تا پایان دوره ادامه دارد. اشتراک بهصورت خودکار تمدید نمیشود. پیش از پایان دوره به شما اطلاع داده میشود تا در صورت تمایل، اشتراک خود را تمدید کنید. --- ۲. بازگشت وجه اشتراکها بهدلیل ماهیت دیجیتال و دسترسی فوری به محتوا، بهطور کلی قابل بازگشت نیستند. در موارد استثنایی — از جمله مشکلات پرداخت یا عدم دسترسی به محتوای خریداریشده — میتوانید از طریق پشتیبانی درخواست بررسی دهید. هر درخواست بهصورت جداگانه بررسی میشود. در صورت تأیید بازگشت وجه، مبلغ به همان کارتی که با آن پرداخت کردهاید بازگردانده میشود. بازگشت وجه به کارت دیگر یا بهصورت اعتبار داخل پلتفرم انجام نمیشود. --- ۳. در صورت غیرفعال شدن کانال کریتور اگر دسترسی به کانال یک کریتور در طول دوره اشتراک شما متوقف شود، بلافاصله از طریق پیامک و اعلان در پلتفرم به شما اطلاع داده میشود و دو گزینه خواهید داشت: ۱. درخواست بازگشت وجه — مبلغ دوره استفادهنشده بهصورت نسبی محاسبه و به کارت شما بازگردانده میشود. ۲. انتظار برای بازگشت کانال — اگر درخواست بازگشت وجه ندهید، در صورت فعال شدن مجدد کانال، مدتزمان توقف به اشتراک شما اضافه میشود و تاریخ انقضای جدید به شما اعلام خواهد شد. اگر هیچ اقدامی نکنید، گزینه دوم بهطور خودکار اعمال میشود. --- ۴. تغییر قیمت قیمتی که هنگام خرید پرداخت کردهاید تا پایان دوره اشتراک شما ثابت میماند. تغییر قیمت توسط کریتور روی اشتراک فعلی شما تأثیری ندارد. در زمان تمدید، قیمت جاری آن کانال اعمال میشود و پیش از پرداخت به شما نمایش داده خواهد شد. --- ۵. تخفیفها تخفیفهای دورهای هنگام خرید اشتراک جدید، تمدید اشتراک فعلی، و خرید مجدد پس از پایان دوره قابل استفاده هستند. تخفیف روی اشتراکی که پیشتر خریداری کردهاید اعمال نمیشود، اما میتوانید در زمان تمدید یا خرید مجدد از آن بهرهمند شوید. پایان یافتن یک تخفیف روی اشتراکی که با قیمت تخفیفخورده خریداری شده تأثیری ندارد؛ شما تا پایان دوره از همان قیمت بهرهمند میشوید. --- ۶. محتوا و مسئولیت محتوای منتشرشده در کانالها — شامل تحلیلها، پیشبینیها و دیدگاهها — توسط کریتورها تولید میشود و مسئولیت آن بهعهده خود آنهاست. [نام پلتفرم] بستری برای انتشار و اعتبارسنجی عملکرد تحلیلگران فراهم میکند و هیچیک از محتوای منتشرشده را تأیید، تضمین یا بهعنوان توصیه سرمایهگذاری ارائه نمیدهد. تصمیمات سرمایهگذاری شما بر عهده خودتان است. --- ۷. مشکلات پرداخت اگر مبلغی از حساب شما کسر شده اما اشتراک فعال نشده، از بخش تراکنشها شماره پیگیری را به پشتیبانی ارسال کنید. پس از بررسی، دسترسی شما فعال یا مبلغ بازگردانده میشود. --- متن لینک در صفحه پرداخت: شرایط اشتراک عنوان صفحه: شرایط اشتراک
U10 — Investor: Immediate Access After Payment
U10 — Investor: Immediate Access After Payment Story: As an investor, I want to receive immediate access to premium content after a successful payment so that my subscription works instantly without manual steps. Scope note: This story owns the post-payment journey — the return from ZarinPal, access propagation across surfaces, and confirmation notifications to both parties. The checkout flow up to the gateway redirect is owned by U9; access control logic by C5 Section 2; expiry and revocation by U11. Acceptance Criteria:
- Return from Gateway & Confirmation State Happy Path: On successful payment, ZarinPal redirects the investor back to the platform The platform shows a brief processing state while server-side confirmation completes — this is not instantaneous, and the investor must never be left on a blank or ambiguous screen On confirmation, the investor lands on the creator's channel page with premium content unlocked, and a success toast appears No success screen, no intermediate page — the investor is placed directly in front of the content they paid for Edge Cases: The processing state is non-dismissible — the investor cannot navigate away mid-confirmation and land in an ambiguous state If confirmation completes in under a second, the processing state may not be perceptible — that is fine; it must exist, not necessarily be seen If the investor closes the app during processing, confirmation continues server-side. On next open, the subscription is active and access is granted (Section 3) If confirmation exceeds a reasonable timeout, the flow moves to the pending-payment path (Section 5) Farsi copy: Processing state: در حال تأیید پرداخت... Success toast: اشتراک شما فعال شد.
- Access Propagation Across Surfaces Happy Path: Once a subscription is active, premium content from that creator is unlocked everywhere it appears — the paywall is a single access check, not a per-surface state
Surface Behaviour on activation Creator channel page Unlocked immediately — this is where the investor lands خانه feed Locked cards from that creator unlock on next feed load or refresh Standalone post pages Unlocked on next load Locked teasers already rendered on screen elsewhere Unlock on next load of that surface Edge Cases: The خانه feed is not force-refreshed in the background. If the investor navigates to خانه after subscribing, it loads fresh and shows unlocked content. A feed loaded before subscribing and left open in a stale state resolves on its next natural load — no special invalidation is required in Phase 0 Subscribing auto-follows the creator (U8 Section 2) if not already following, so their posts begin appearing in خانه from this point forward The Subscribe CTA on the creator's profile header is replaced with the subscription status indicator (مشترک هستید ✓, U6 Section 5) The unfollow control freezes while the subscription is active (U8 Section 2) If the investor was on this creator's waitlist, they are removed from it automatically (U9 Section 6) 3. Subscription Record Creation Happy Path: On confirmation, a subscription record is created with: Creator, tier, and duration purchased Amount actually paid — the promotional price if a promotion applied, not the standing price Start date/time (moment of confirmation) and expiry date/time ZarinPal reference number The subscription appears immediately in the investor's اشتراکها section (U2) The transaction appears immediately in تراکنشها (U4) with status موفق Edge Cases: Expiry is calculated from the confirmation timestamp, not from the moment of gateway redirect — an investor is never charged for minutes lost to processing The price paid is locked to this subscription — later standing-price or promotional changes by the creator never alter it (C7 Section 8) If the investor closed the app during confirmation, the record is created regardless; they find an active subscription on next open, with notifications (Section 4) already delivered 4. Confirmation Notifications To the investor: SMS and in-app notification confirming the subscription, containing the tier, amount paid, and expiry date — the receipt this flow would otherwise lack, since no success screen is shown Sent immediately on confirmation To the creator: In-app notification of the new subscriber, containing the subscriber's username, the tier purchased, and the amount This is the one subscription-related event creators are notified about. Follows are deliberately not notified (U8 Section 6) — reserving notifications for events carrying real signal is precisely what keeps this one meaningful Edge Cases: Creator notification is in-app only, not SMS — a creator onboarding an audience could receive several in a day, and SMS at that volume becomes noise. The investor's notification is SMS-backed because it is a financial receipt The subscriber's username is shared, not their phone number or legal name — the creator sees who subscribed at the same level of identity the platform shows publicly If the creator is suspended at the moment of confirmation, no subscription should exist — checkout is unreachable for suspended creators (U9 Section 1). This is defensive only SMS follows the standard retry policy: up to 3 attempts, 10-minute intervals (U5 Section 3) Farsi copy — investor: In-app title: اشتراک شما فعال شد In-app body: اشتراک {tier} کانال {creator_username} فعال شد. مبلغ پرداختی: {amount} تومان — تاریخ انقضا: {expiry_date} SMS: اشتراک {tier} کانال {creator_username} در [نام پلتفرم] فعال شد. مبلغ: {amount} تومان — انقضا: {expiry_date} Farsi copy — creator: In-app title: مشترک جدید In-app body: {investor_username} اشتراک {tier} کانال شما را خریداری کرد. مبلغ: {amount} تومان 5. Pending Confirmation Path Happy Path: Where the ZarinPal callback is not received within a reasonable timeout, the subscription is marked در حال بررسی rather than failed — money may have been deducted, and treating it as a failure would be wrong The investor is informed and returned to the creator's channel; premium content remains locked until confirmation The Subscribe CTA is replaced with a frozen پرداخت در حال بررسی indicator (U9 Section 5), preventing a duplicate payment attempt On later confirmation, access is granted and the full notification set (Section 4) fires — the investor is not left to discover it themselves Edge Cases: The transaction appears in تراکنشها with status در حال بررسی and its ZarinPal reference number, which is the reference support needs (U4 Section 4) If the payment is ultimately not confirmed, the transaction moves to ناموفق, the Subscribe CTA returns to اشتراک, and no subscription is created A deducted-but-unconfirmed payment is resolved via support and admin tooling (A9), with the outcome being either retroactive access grant or refund Farsi copy: Pending toast on return: پرداخت شما در حال بررسی است. پس از تأیید، اشتراک شما فعال میشود. Delayed confirmation in-app notification: پرداخت شما تأیید شد و اشتراک {tier} کانال {creator_username} فعال شد. تاریخ انقضا: {expiry_date} Delayed confirmation SMS: پرداخت شما تأیید شد. اشتراک کانال {creator_username} در [نام پلتفرم] فعال شد — انقضا: {expiry_date} 6. Failure Path Happy Path (of failure handling): If ZarinPal reports a failed or declined payment, the investor returns to checkout — not the channel — with their tier selection and referral code preserved An error message explains the failure; the پرداخت CTA is live for an immediate retry No subscription is created; no access is granted Edge Cases: The failed attempt is recorded in تراکنشها with status ناموفق (U4 Section 2) — the investor can see what was attempted even though nothing was charged No notification is sent for a failed payment to either party — the investor is already looking at the error, and a creator has no interest in attempts that didn't complete If the investor abandons the ZarinPal page without completing, no record is created at all — abandonment is not failure Farsi copy: Failure error on checkout: پرداخت ناموفق بود. لطفاً دوباره تلاش کنید. 7. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text, per the Stripi-inspired design system Processing state renders as a full-screen centered state with a spinner and در حال تأیید پرداخت... — no navigation affordances, since the investor should not leave mid-confirmation Success toast uses the standard snackbar pattern, auto-dismissing after a few seconds — deliberately lightweight, since the receipt arrives via SMS and in-app notification rather than occupying the screen All amounts, dates, and reference numbers use font-feature-settings: "tnum" — per the design system's tabular-figures rule for monetary and numeric values Dates rendered in Shamsi calendar throughout, consistent with U2/U3/U4 Frozen پرداخت در حال بررسی indicator uses {colors.ink-mute} (#64748d) at opacity: 0.4 with a clock icon — visually distinct from both a live CTA and an error state Error messages render in {colors.ruby} (#ea2261) All screens mobile-first
U11 — Investor: Automatic Access Revocation on Expiry
U11 — Investor: Automatic Access Revocation on Expiry Story: As an investor, I want to have my access automatically revoked when a subscription expires so that the system is fair and self-managing. Scope note: This story owns the expiry event — what the system does at the moment a subscription lapses, and the state the investor is left in. Pre-expiry warnings and notifications are owned by U2 Section 3 and U5; reactivation is owned by U3 Section 4; suspension-driven access loss (a different mechanism entirely) is owned by A2. Acceptance Criteria:
- The Expiry Event Happy Path: A subscription expires automatically at its recorded expiry date and time — no manual step by the investor, creator, or admin Expiry is evaluated to the minute, matching how it was recorded at purchase (U10 Section 3) On expiry, the system atomically: Marks the subscription expired Revokes premium content access for that creator Moves the subscription from the active list to اشتراکهای منقضیشده (U3 Section 2) Unfreezes the unfollow control (Section 4) Sends the expiry notification (U5 Section 4) Edge Cases: Expiry fires regardless of whether the investor is using the app — it is a server-side state change, not a client-side check Expiry fires regardless of the creator's status. If the creator is suspended at the moment of expiry, the subscription still expires on schedule; the investor's refund right under A2 Section 6 persists independently and has no deadline No auto-renewal exists. A subscription always ends at its term unless the investor deliberately renews (U3) — stated explicitly in the subscription terms, and a deliberate product choice rather than an omission
- Access Revocation Behaviour Happy Path: Once expired, premium content from that creator reverts to locked teasers everywhere it appears — the identical pattern defined in C5 Section 3 and U7, with no distinction between "never subscribed" and "subscription lapsed"
Surface Behaviour after expiry Creator channel page Premium posts revert to locked teasers on next load خانه feed Premium posts from that creator revert to locked cards on next feed load Standalone post pages Locked teaser on next load اشتراکها Subscription moves to اشتراکهای منقضیشده with reactivation CTA Edge Cases: Content already open on screen at the moment of expiry is not removed mid-session. The lock takes effect on the next page load or refresh, not retroactively within an open session (C5 Section 5). Snatching content from under someone reading it would be hostile, and the value already delivered cannot be recovered anyway Free content from that creator remains fully accessible — expiry affects premium access only The follow relationship persists — their posts continue appearing in خانه, with premium ones locked. This is deliberate: a lapsed subscriber who still follows is the most likely person to reactivate, and continuing to see locked cards from a creator they follow is the strongest reactivation prompt available Prediction outcomes on the creator's profile header (U6) and public track record page remain visible — the paywall governs analysis and reasoning, never recorded results 3. Subscribe CTA State Happy Path: On expiry, the subscription status indicator (مشترک هستید ✓, U6 Section 5) is replaced by the live اشتراک CTA Tapping it opens the standard checkout flow (U9) Edge Cases: A lapsed investor re-entering checkout is treated as a reactivation (U3 Section 4) — the new period starts from today, not from the old expiry date A referral code is required again. A lapsed subscriber re-entering checkout must supply a valid code, and capacity is re-checked at that moment If capacity is now full, the lapsed subscriber gets the waitlist path (U9 Section 6) like anyone else — prior subscription grants no priority. This is worth flagging to you as a real product consequence: a creator who fills their capacity while an investor's subscription is lapsed may lock out a returning paying customer in favour of a new one Promotional pricing applies to reactivation (C7 Section 6) — a win-back promotion reaches exactly this investor 4. Follow State on Expiry Happy Path: On expiry, the unfollow control unfreezes automatically — no action required from the investor (U8 Section 2) The investor remains following the creator; only the restriction on unfollowing is lifted Edge Cases: If the investor reactivates later, the unfollow control freezes again (U8 Section 2) If the investor unfollows after expiry, that creator's posts stop appearing in خانه entirely. Reactivating later re-applies auto-follow (U8 Section 2) 5. Notifications Happy Path: The expiry notification — SMS and in-app — is sent at the moment of expiry, as fully specified in U5 Section 4 No additional notification is introduced by this story Edge Cases: The expiry notification is suppressed if the investor already renewed before expiry (U5 Section 6) — renewal means there is no expiry event to announce No notification is sent to the creator when a subscriber lapses. Creators are notified of new subscriptions (U10 Section 4) but not of churn — a departure notification is discouraging, offers nothing actionable in the moment, and the churn signal properly belongs in the creator's dashboard (C9) as data rather than as an interruption 6. Record Retention Happy Path: Expired subscriptions are retained indefinitely in اشتراکهای منقضیشده (U3 Section 2) — no automatic cleanup in Phase 0 The original transaction remains permanently in تراکنشها with status موفق (U4 Section 2) — expiry does not alter the historical record of a completed payment Edge Cases: Multiple expired subscriptions to the same creator (subscribe, lapse, reactivate, lapse again) each retain their own record — the history is a complete chronological account, not a single overwritten row Expiry never alters the amount paid on a historical record 7. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text, per the Stripi-inspired design system Expired subscription cards use card-feature-light with the منقضیشده badge in {colors.ink-mute} (#64748d) background with white text — neutral, not a {colors.ruby} error treatment. An expired subscription is a normal lifecycle state, not a failure Reactivation CTA uses button-primary-pill (#533afd) Locked teasers post-expiry are visually identical to never-subscribed locked teasers — no "you used to have access" variant, which would add noise without adding value All dates use Shamsi calendar with font-feature-settings: "tnum" Minimum touch target: 44×44px Mobile-first throughout
U2 — Investor Active Subscriptions View
Story: As an investor, I want to view all my active subscriptions with remaining time so that I always know what I'm paying for and when it expires. Design system note: This story introduces a new color token {colors.warning} = #f59e0b (amber) — used for moderate time-sensitive warnings. {colors.ruby} (#ea2261) is used for urgent/critical warnings (3 days or less remaining), consistent with its existing role as the error/critical color in the design system. Acceptance Criteria:
- Access & Entry Point Happy Path: Investor accesses their subscriptions from the داشبورد tab → اشتراکها sub-section The section displays a list of all active subscriptions the investor currently holds Each subscription card shows all relevant information at a glance (see Section 2) Edge Cases: If the investor has no active subscriptions, an empty state is shown with a clear message and a CTA that navigates the investor to the خانه tab If the investor has both active and expired subscriptions, active ones are shown first — expired ones are shown below in a separate اشتراکهای منقضیشده section (relevant to U3) Farsi copy: Tab label: داشبورد Sub-section label: اشتراکها Empty state message: شما هنوز اشتراکی ندارید. Empty state CTA: رفتن به خانه
- Subscription Card Happy Path: Each active subscription is displayed as a card containing: Creator avatar Creator username Subscription tier (monthly / quarterly / semi-annual / yearly) — in Farsi Subscription start date Subscription expiry date Remaining time label — see Section 3 for full label and color logic Subscription status badge: فعال A تمدید (renew) CTA button Tapping anywhere on the card (except the renew CTA) navigates the investor to that creator's channel Edge Cases: If the creator's account has been suspended, the subscription card is still shown — but the card is visually dimmed and tapping it does not navigate to the channel; a note explains that the creator's channel is temporarily unavailable If the creator's account is suspended and the subscription is close to expiry, the warning states in Section 3 still apply — the subscription timer is independent of the creator's status Error States: If the subscription list fails to load, an error message is shown with a retry option Farsi copy: Subscription tier labels: ماهانه · سهماهه · ششماهه · سالانه Start date label: تاریخ شروع Expiry date label: تاریخ انقضا Status badge (active): فعال Renew CTA: تمدید Suspended creator note: کانال این کریتور موقتاً در دسترس نیست. Load error: خطا در بارگذاری اشتراکها. دوباره تلاش کنید.
- Remaining Time Label & Warning Logic The remaining time label on each subscription card follows a progressive escalation system across three tiers:
Remaining Time Label Label Color Warning Message SMS More than 7 days {n} روز مانده {colors.ink-mute} #64748d None None 4–7 days {n} روز مانده {colors.warning} #f59e0b None None 3 days remaining کمتر از ۳ روز مانده {colors.ruby} #ea2261 Shown beneath card SMS sent 2 days remaining کمتر از ۲ روز مانده {colors.ruby} #ea2261 Shown beneath card — 1 day remaining کمتر از ۱ روز مانده {colors.ruby} #ea2261 Shown beneath card — Warning message behavior: Warning message appears beneath the subscription card when 3 days or less remain Warning message uses {colors.ruby} (#ea2261) with a warning icon SMS — 3 days before expiry: Sent automatically by the system exactly when the subscription crosses the 3-day threshold Sent once only — not repeated daily Includes a direct link to the اشتراکها section of the platform Farsi copy: Remaining time labels: More than 7 days: {n} روز مانده 4–7 days: {n} روز مانده 3 days: کمتر از ۳ روز مانده 2 days: کمتر از ۲ روز مانده 1 day: کمتر از ۱ روز مانده Warning message (3 days or less): اشتراک شما در حال انقضاست. همین الان تمدید کنید. SMS (3 days before expiry): اشتراک شما در کانال {creator_username} در [نام پلتفرم] کمتر از ۳ روز دیگر منقضی میشود. برای تمدید: [لینک به بخش اشتراکها] 4. Post-Expiry Notification Immediately after a subscription expires, the system automatically sends an SMS to the investor informing them of the expiry The expired subscription is moved from the active list to the اشتراکهای منقضیشده section (U3) An in-app notification is also sent at the moment of expiry The SMS includes a direct link to the اشتراکها section of the platform Farsi copy: Post-expiry SMS: اشتراک شما در کانال {creator_username} در [نام پلتفرم] منقضی شد. برای تمدید: [لینک به بخش اشتراکها] Post-expiry in-app notification: اشتراک شما در کانال {creator_username} منقضی شد. برای تمدید وارد داشبورد خود شوید. 5. Subscription Count & Summary Happy Path: At the top of the اشتراکها section, a simple summary line shows the total number of active subscriptions This gives the investor a quick overview without needing to scroll Edge Cases: If the investor has only expired subscriptions and no active ones, the summary line shows zero and the empty state is shown Farsi copy: Summary line: {n} اشتراک فعال Zero active: اشتراک فعالی ندارید. 6. Sorting & Order Active subscriptions are sorted by expiry date ascending by default — the subscription expiring soonest appears first This ensures the investor's attention is naturally drawn to subscriptions that need renewal Edge Cases: If two subscriptions have the same expiry date, they are sorted alphabetically by creator username as a tiebreaker 7. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text Subscription cards use card-feature-light style — {colors.canvas} background, {colors.hairline} border, {rounded.lg} radius, Level 1 shadow Status badge فعال uses {colors.primary} (#533afd) background with white text in pill-tag-soft style Remaining time label color follows the three-tier escalation logic defined in Section 3 Warning message (3 days or less) renders in {colors.ruby} (#ea2261) with a warning icon Suspended creator card uses opacity: 0.5 with a lock icon and the unavailability note Renew CTA uses button-primary-pill style (#533afd, pill radius) Dates and numeric values use font-feature-settings: "tnum" per design system Minimum touch target for all interactive elements: 44×44px Screen is mobile-first; cards stack in a single column
U3 — Investor Subscription Renewal & Reactivation
Story: As an investor, I want to renew or reactivate a subscription from my dashboard so that I don't lose access without an easy way to recover it. Acceptance Criteria:
- Access & Entry Points Happy Path: Investor can initiate renewal or reactivation from two entry points: Active subscription card → via the تمدید CTA button (for subscriptions that are still active but approaching expiry) Expired subscription card in the اشتراکهای منقضیشده section → via a فعالسازی مجدد CTA button Both entry points are within the داشبورد tab → اشتراکها sub-section Edge Cases: If the creator's channel has been suspended at the time the investor attempts renewal or reactivation, the action is blocked — a specific message is shown explaining the channel is temporarily unavailable If the creator has changed their subscription price since the investor's original subscription, the new price is shown clearly in the renewal/reactivation flow before payment is confirmed Farsi copy: Active subscription renew CTA: تمدید Expired subscription reactivation CTA: فعالسازی مجدد Suspended creator block message: در حال حاضر امکان تمدید یا فعالسازی مجدد اشتراک این کریتور وجود ندارد. کانال موقتاً در دسترس نیست.
- Expired Subscriptions View Happy Path: Expired subscriptions are shown below active subscriptions in the اشتراکها sub-section under a clearly labeled اشتراکهای منقضیشده heading Each expired subscription card shows: Creator avatar Creator username Subscription tier Expiry date Status badge: منقضیشده فعالسازی مجدد CTA button Edge Cases: Expired subscriptions are sorted by expiry date descending — most recently expired appears first If the investor has no expired subscriptions, the اشتراکهای منقضیشده section is not shown at all — no empty state needed for this sub-section specifically Expired subscriptions are kept in this list indefinitely in Phase 0 — no automatic removal Error States: If the expired subscription list fails to load, an error message is shown with a retry option Farsi copy: Section heading: اشتراکهای منقضیشده Status badge (expired): منقضیشده Reactivation CTA: فعالسازی مجدد Load error: خطا در بارگذاری اشتراکها. دوباره تلاش کنید.
- Renewal Flow (Active Subscription) Happy Path: Investor taps تمدید on an active subscription card A renewal bottom sheet / modal appears showing: Creator avatar and username A clear statement of the investor's current active subscription period All available subscription tiers (1, 3, 6, 12 months) with their prices — current tier is pre-selected A dynamic date preview showing exactly what period the investor is purchasing — updates in real time when the investor switches between tiers Total amount to be charged Payment CTA Investor selects a tier and confirms payment On successful payment: The subscription expiry date is extended from the current expiry date — not from today (to avoid penalising early renewals) A success message is shown The subscription card updates immediately to reflect the new expiry date and remaining time An in-app notification and SMS confirmation are sent Subscription Tiers:
Tier Duration Farsi Label ماهانه 1 month ماهانه سهماهه 3 months سهماهه ششماهه 6 months ششماهه سالانه 12 months سالانه Date Preview Logic: The date preview is shown beneath the tier selector and updates dynamically as the investor switches tiers Renewal always extends from the current expiry date — regardless of when the investor initiates the renewal Edge Cases: Early renewal extends from the current expiry date — e.g., if a monthly subscription has 10 days left and the investor renews today for another month, the new expiry is current expiry + 30 days If the creator has updated their subscription price, the new price is shown with a note informing the investor of the price change Investor can switch to a different tier during renewal (e.g., upgrade from monthly to quarterly) — the new expiry is calculated based on the new tier starting from the current expiry date Error States: Payment failure: specific error message shown, subscription status unchanged, investor can retry Network error: error message shown with retry option Session timeout during payment: investor is returned to the renewal modal with their selections preserved Farsi copy: Renewal modal heading: تمدید اشتراک Current subscription statement: شما تا {current_expiry_date} اشتراک فعال دارید. Tier selection label: دوره اشتراک Tier options: ماهانه · سهماهه · ششماهه · سالانه Date preview – from: تمدید از: {current_expiry_date} Date preview – to: تا: {new_expiry_date} Total amount label: مبلغ قابل پرداخت Price change note: قیمت این اشتراک توسط کریتور تغییر کرده است. Payment CTA: پرداخت و تمدید Success message: اشتراک شما با موفقیت تمدید شد. New expiry date confirmation: تاریخ انقضای جدید: {new_expiry_date} Payment failure error: پرداخت ناموفق بود. لطفاً دوباره تلاش کنید. Network error: خطا در اتصال. دوباره تلاش کنید. SMS confirmation: اشتراک شما در کانال {creator_username} در [نام پلتفرم] با موفقیت تمدید شد. تاریخ انقضای جدید: {new_expiry_date}. [لینک به بخش اشتراکها] 4. Reactivation Flow (Expired Subscription) Happy Path: Investor taps فعالسازی مجدد on an expired subscription card A reactivation bottom sheet / modal appears showing: Creator avatar and username All available subscription tiers (1, 3, 6, 12 months) with their prices — no tier pre-selected A dynamic date preview showing exactly what period the investor is purchasing — updates in real time when the investor switches between tiers Total amount to be charged Payment CTA Investor selects a tier and confirms payment On successful payment: A new subscription period starts from today (not from the original expiry date) The subscription moves from اشتراکهای منقضیشده back to the active subscriptions list A success message is shown The subscription card updates immediately An in-app notification and SMS confirmation are sent Date Preview Logic: Start date is always today's date End date is calculated as today + selected tier duration Updates in real time as the investor switches tiers Edge Cases: Reactivation is treated as a new subscription period — it always starts from the payment date, not the previous expiry date If the creator has changed their subscription price since the investor's last subscription, the new price is shown with a note Investor can select a different tier from their original subscription during reactivation Error States: Payment failure: specific error message shown, subscription remains expired, investor can retry Network error: error message shown with retry option Session timeout during payment: investor is returned to the reactivation modal with their selections preserved Farsi copy: Reactivation modal heading: فعالسازی مجدد اشتراک Tier selection label: دوره اشتراک Tier options: ماهانه · سهماهه · ششماهه · سالانه Date preview – start: شروع از: امروز — {today_date} Date preview – end: تا: {new_expiry_date} Total amount label: مبلغ قابل پرداخت Price change note: قیمت این اشتراک توسط کریتور تغییر کرده است. Payment CTA: پرداخت و فعالسازی Success message: اشتراک شما با موفقیت فعالسازی شد. New expiry date confirmation: تاریخ انقضا: {new_expiry_date} Payment failure error: پرداخت ناموفق بود. لطفاً دوباره تلاش کنید. Network error: خطا در اتصال. دوباره تلاش کنید. SMS confirmation: اشتراک شما در کانال {creator_username} در [نام پلتفرم] با موفقیت فعالسازی شد. تاریخ انقضا: {new_expiry_date}. [لینک به بخش اشتراکها] 5. Payment Integration Notes All payments are processed via ZarinPal domestic payment gateway Payment flow opens ZarinPal's payment page — on completion, the investor is returned to the platform Payment confirmation is handled via ZarinPal's callback — access is granted only after server-side confirmation, not just client-side redirect In case of ambiguous payment status (callback not received within a reasonable timeout), the system marks the subscription as در حال بررسی and notifies the investor — access is granted once confirmed Farsi copy: Pending payment status: پرداخت در حال بررسی است. پس از تأیید، اشتراک شما فعال میشود. Pending payment in-app notification: پرداخت شما در حال بررسی است. به محض تأیید اطلاع داده میشود. 6. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text Expired subscription cards use card-feature-light style with status badge منقضیشده in {colors.ink-mute} (#64748d) background with white text Reactivation and renewal CTAs use button-primary-pill style (#533afd, pill radius) Renewal and reactivation flows use a bottom sheet on mobile — slides up from the bottom, overlays the current screen Tier selection uses a segmented control or pill-style selector — selected tier highlighted with {colors.primary} fill, unselected tiers use button-secondary style Date preview block is visually distinct from the rest of the modal — rendered on {colors.canvas-soft} (#f6f9fc) background with {rounded.md} radius to draw attention Date values use font-feature-settings: "tnum" per design system Total amount uses font-feature-settings: "tnum" per design system Success state shows a checkmark animation before returning to the updated subscription card Payment failure state shows {colors.ruby} (#ea2261) error message with a retry CTA Minimum touch target for all interactive elements: 44×44px Screen is mobile-first
U4 — Investor Transaction History
Story: As an investor, I want to see my full transaction history so that I can track my spending on the platform. Acceptance Criteria:
- Access & Entry Point Happy Path: Investor accesses their transaction history from the داشبورد tab → تراکنشها sub-section The section displays a chronological list of all transactions the investor has made on the platform — sorted by date descending (most recent first) Edge Cases: If the investor has never made a transaction, an empty state is shown with a clear message and a CTA directing them to the خانه tab to discover creators Transactions from all states (successful, failed, pending) are shown — not just successful ones Farsi copy: Tab label: داشبورد Sub-section label: تراکنشها Empty state message: هنوز هیچ تراکنشی انجام ندادهاید. Empty state CTA: رفتن به خانه
- Transaction List Happy Path: Each transaction is displayed as a row or card containing: Creator avatar and username Transaction type (new subscription, renewal, reactivation) Subscription tier purchased (1, 3, 6, or 12 months) — in Farsi Amount paid — in Toman (تومان) Transaction date and time — in Shamsi (Jalali) calendar Transaction status badge (successful, failed, pending) ZarinPal reference number — for support purposes List is paginated — maximum 20 rows per page Edge Cases: If a transaction is in pending state (ZarinPal callback not yet received), it is shown at the top of the list regardless of date — pending transactions take visual priority If a transaction failed, the row is shown with the failed status badge — the investor can see what was attempted even if no money was charged If a creator's account has been suspended since the transaction was made, the creator's username and avatar are still shown as they were at the time of the transaction — historical record must remain intact Transactions are never removed from the history — full permanent record Error States: If the transaction list fails to load, an error message is shown with a retry option Farsi copy: Transaction type labels: New subscription: اشتراک جدید Renewal: تمدید اشتراک Reactivation: فعالسازی مجدد Subscription tier labels: ماهانه · سهماهه · ششماهه · سالانه Amount label: مبلغ Date label: تاریخ Reference number label: شماره پیگیری Load error: خطا در بارگذاری تراکنشها. دوباره تلاش کنید.
- Transaction Status Badges
Status Farsi Label Color Successful موفق {colors.primary} #533afd Failed ناموفق {colors.ruby} #ea2261 Pending در حال بررسی {colors.warning} #f59e0b Status badge is always visible on each transaction row — no need to expand the row to see status Pending transactions show an additional note beneath the row explaining what pending means Farsi copy: Pending explanation note: پرداخت شما در حال بررسی است. در صورت کسر وجه، اشتراک به زودی فعال میشود. 4. Transaction Detail View Happy Path: Tapping a transaction row expands it or opens a detail sheet showing full information: Creator avatar and username Transaction type Subscription tier Subscription period (from date → to date) — shown for successful transactions only Amount paid — in Toman Transaction date and time — in Shamsi calendar Transaction status ZarinPal reference number A پشتیبانی (support) CTA for failed or pending transactions — opens a contact/support channel Edge Cases: For failed transactions, the detail view shows a clear note that no money was charged and suggests the investor try again For pending transactions, the detail view shows the ZarinPal reference number prominently — this is the most useful piece of information for a support query Subscription period (from/to dates) is only shown for successful transactions — failed and pending transactions do not have a subscription period Error States: If the detail view fails to load, an error message is shown with a retry option Farsi copy: Detail sheet heading: جزئیات تراکنش Subscription period label: دوره اشتراک Subscription period format: از {start_date} تا {end_date} Amount label: مبلغ پرداختشده Date label: تاریخ تراکنش Reference number label: شماره پیگیری زرینپال Failed transaction note: این تراکنش ناموفق بوده و مبلغی از حساب شما کسر نشده است. Pending transaction note: در صورت بروز مشکل، شماره پیگیری را برای پشتیبانی ارسال کنید. Support CTA: تماس با پشتیبانی Detail load error: خطا در بارگذاری جزئیات. دوباره تلاش کنید. 5. Filtering Happy Path: Investor can filter transactions by status: All (default) Successful only Failed only Pending only Filter is applied instantly — no need to tap a separate apply button Edge Cases: If a filter returns no results, a contextual empty state is shown — not the global empty state from Section 1 Filter selection persists during the session but resets on next visit Farsi copy: Filter label: وضعیت Filter options: همه · موفق · ناموفق · در حال بررسی Filtered empty state: تراکنشی با این وضعیت یافت نشد. 6. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text Transaction rows use card-feature-light style — {colors.canvas} background, {colors.hairline} border, {rounded.lg} radius, Level 1 shadow Status badges use pill-tag-soft style with colors as defined in Section 3 All amounts use font-feature-settings: "tnum" per design system — financial figures must always use tabular figures All dates use Shamsi (Jalali) calendar format throughout — {day} {month_name} {year} (e.g., ۱۵ خرداد ۱۴۰۴) Pending transaction rows have a subtle {colors.warning} (#f59e0b) left border to draw attention without being alarming Failed transaction rows have a subtle {colors.ruby} (#ea2261) left border ZarinPal reference number is displayed using font-feature-settings: "tnum" — easy to read and copy Tapping the reference number copies it to clipboard with a brief confirmation toast Minimum touch target for all interactive elements: 44×44px Screen is mobile-first; transaction rows stack in a single column Farsi copy: Clipboard copy confirmation toast: شماره پیگیری کپی شد.
U5 — Investor Subscription Expiry Notifications
The full notification sequence for U5 is: 7 days before expiry → visual warning only (card color change — already in U2) 3 days before expiry → SMS + in-app notification (mandatory) At expiry → SMS + in-app notification (mandatory) language-text U5 — Investor Subscription Expiry Notifications Story: As an investor, I want to receive a notification before my subscription expires so that I have time to renew before losing access. Relationship to U2: U2 defines the visual warning states on subscription cards (color escalation at 7 days and 3 days). U5 formally owns the notification sequence — SMS and in-app notifications triggered at the 3-day threshold and at the moment of expiry. Both stories must be implemented together for the full expiry communication experience to work correctly. ⚠️ Forward dependency note: Push notifications (via a domestic push notification service) are deferred to Phase 1. Phase 0 relies exclusively on SMS and in-app notifications — both are reliable on Iranian infrastructure without VPN dependency or device permission complexity. Acceptance Criteria:
- Notification Philosophy Expiry notifications are mandatory — users cannot opt out This is a user protection feature, not a marketing communication — users must always know when they are about to lose access to content they are paying for All notifications are triggered automatically by the system — no manual step required from the admin or creator Phase 0 notification channels: SMS and in-app notification only
- Notification Sequence The complete expiry notification sequence per subscription is as follows:
Trigger Channel Timing 3 days before expiry SMS + in-app Exactly when subscription crosses the 3-day threshold At expiry SMS + in-app Exactly when subscription expires Rules: Each notification in the sequence is sent once only — no repetition The 3-day notification is sent regardless of whether the investor has already renewed — if they renewed early, the notification is suppressed since the subscription is no longer expiring The expiry notification is sent regardless of creator account status — even if the creator is suspended, the investor is still notified that their subscription has expired Both notifications include a direct link to the اشتراکها sub-section of the داشبورد tab so the investor can act immediately 3. 3-Day Pre-Expiry Notification Happy Path: System detects that a subscription's remaining time has crossed the 3-day threshold SMS and in-app notification are sent simultaneously to the investor The notification clearly identifies which creator's channel is expiring — not a generic message The notification includes a direct link to the اشتراکها section Edge Cases: If the investor renews their subscription before the 3-day notification is sent (i.e., early renewal), the notification is suppressed — no need to remind them about an expiry that is no longer imminent If the investor renews between the 3-day notification and the expiry, the expiry notification is also suppressed — renewed subscriptions do not trigger expiry notifications If multiple subscriptions are expiring within 3 days, a separate notification is sent for each — they are not batched into one message Error States: If SMS delivery fails, the system retries up to 3 times with a 10-minute interval between retries If all retries fail, the failure is logged for admin visibility — in-app notification is still shown regardless of SMS delivery status If in-app notification fails to deliver (user is offline), it is queued and delivered upon next app open Farsi copy: In-app notification title: اشتراک شما در حال انقضاست In-app notification body: اشتراک شما در کانال {creator_username} کمتر از ۳ روز دیگر منقضی میشود. همین الان تمدید کنید. In-app notification CTA: تمدید اشتراک SMS: اشتراک شما در کانال {creator_username} در [نام پلتفرم] کمتر از ۳ روز دیگر منقضی میشود. برای تمدید به این آدرس بروید: [لینک به بخش اشتراکها] 4. At-Expiry Notification Happy Path: System detects that a subscription has expired (expiry date/time has passed) SMS and in-app notification are sent simultaneously to the investor The notification clearly states that access to the creator's premium content has been revoked The notification includes a direct link to the اشتراکها section for reactivation Edge Cases: If the investor already renewed before expiry, this notification is suppressed — renewed subscriptions do not trigger expiry notifications If multiple subscriptions expire at the same time, a separate notification is sent for each If the creator's account is suspended at the time of expiry, the notification is still sent — the investor must be informed their subscription has expired regardless of creator status The at-expiry notification is sent even if the 3-day notification was suppressed (e.g., a subscription that was purchased and expired within 3 days — edge case but must be handled) Error States: Same retry logic as Section 3: up to 3 retries for SMS with 10-minute intervals In-app notification queued for delivery on next app open if user is offline Farsi copy: In-app notification title: اشتراک شما منقضی شد In-app notification body: اشتراک شما در کانال {creator_username} منقضی شد و دسترسی به محتوای ویژه قطع شده است. برای ادامه دسترسی، اشتراک خود را فعالسازی مجدد کنید. In-app notification CTA: فعالسازی مجدد SMS: اشتراک شما در کانال {creator_username} در [نام پلتفرم] منقضی شد. برای فعالسازی مجدد به این آدرس بروید: [لینک به بخش اشتراکها] 5. In-App Notification Center Happy Path: All in-app notifications are accessible from a notification bell icon in the top bar of the app Unread notifications are indicated by a badge count on the bell icon Each notification in the center is shown with: Notification title Notification body (truncated to 2 lines — expandable on tap) Timestamp — in Shamsi calendar, relative format for recent notifications (e.g., ۲ ساعت پیش) and absolute for older ones A direct CTA button where applicable (تمدید اشتراک / فعالسازی مجدد) Tapping a notification marks it as read and navigates the investor to the relevant section Edge Cases: Notifications are kept in the notification center for 30 days — older ones are automatically removed If the investor taps an expiry notification for a subscription they have already renewed, they are still navigated to the اشتراکها section — no error shown Unread count badge disappears when the investor opens the notification center — even if they do not tap individual notifications Error States: If the notification center fails to load, an error message is shown with a retry option Farsi copy: Notification center heading: اعلانها Empty state: اعلانی وجود ندارد. Relative timestamp examples: همین الان · ۵ دقیقه پیش · ۲ ساعت پیش · دیروز Load error: خطا در بارگذاری اعلانها. دوباره تلاش کنید. 6. Suppression Logic Summary To avoid sending irrelevant notifications, the system must check subscription status before sending each notification:
Condition 3-Day Notification Expiry Notification Subscription still active and not renewed ✅ Send ✅ Send Subscription renewed before 3-day threshold ❌ Suppress ❌ Suppress Subscription renewed after 3-day notification but before expiry N/A (already sent) ❌ Suppress Creator account suspended ✅ Send ✅ Send Investor account suspended ❌ Suppress ❌ Suppress 7. UI / UX Layout is RTL throughout; Yekan Bakh is the typeface for all Farsi text Notification bell icon is placed in the top bar — visible from all main tabs Unread badge uses {colors.ruby} (#ea2261) background with white text — maximum 2 digits shown (99+ for counts above 99) Notification cards in the center use card-feature-light style — {colors.canvas} background, {colors.hairline} border, {rounded.lg} radius Unread notifications have a subtle {colors.primary-bg-subdued-hover} (#b9b9f9) left border to distinguish from read ones Read notifications have no left border — visually quieter CTA buttons within notifications use button-primary-pill style (#533afd, pill radius) — compact size Timestamps use {colors.ink-mute} (#64748d) in {typography.caption} size Minimum touch target for all interactive elements: 44×44px Notification center is a slide-in panel from the right side on mobile (RTL — so right side is the leading edge)