Payment cycle model: annual renew for 12-month and one-time focus on 3/6

DEC-0081 - Payment cycle model: annual renew for 12-month and one-time focus on 3/6

Context

Active payment docs currently treat 12-month as a one-time non-renew option with yearly labeling. Product direction was updated to make 12-month a real annual auto-renew plan and keep one-time choices focused on 3 and 6 months.

Decision

• Remove One-time 12-month non-renew from DOL English Web V2 active cycle model.
• Add Annual 12-month auto-renew as the 12-month plan.
• Keep one-time scope as 3-month and 6-month only.
• Keep one-time savings ladder at 6-month vs 3-month.
• Payment method gate:
  • Monthly/Annual: Card + Momo,
  • One-time 3/6: Card + Momo + Bank QR/Chuyen khoan.
• Overlap/cancel alignment:
  • if one-time is active, monthly/annual starts after one-time expiry,
  • monthly/annual cancellation is effective at cycle end.

Decision Value

• Reduces package ambiguity for users at checkout.
• Keeps cycle taxonomy cleaner and easier to operate.
• Preserves low-friction conversion while avoiding mixed 12-month semantics.

Rationale

Using one 12-month meaning (annual auto-renew) avoids duplicate mental models (yearly label vs one-time 12-month) and keeps one-time offers simple for short/medium horizons.

Implications

• Product/UX impact:
  • checkout copy and selectors become clearer (Monthly | Annual | One-time 3/6).
• Data/logic impact:
  • billing cycle enum and method gate references must align across docs.
• Operational impact:
  • support scripts and pricing communications should stop referencing one-time 12-month.

Alternatives considered

• Option A: keep one-time 12-month + yearly dual-label.
• Option B: annual-only 12-month (selected) + one-time 3/6.

Open follow-ups

• None for baseline lock.