feat: billing free trials feature doc + tax information#705
Merged
Conversation
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughDocumentation adds native free-trial support in Kinde Billing (plan-level trial settings, UI badges, automatic Stripe-based trial-to-paid conversion), introduces trial-related access-token claims, and clarifies that sales tax/VAT and invoice behavior are determined by the connected Stripe account configuration. Changes
Sequence Diagram(s)sequenceDiagram
participant User as Client (User)
participant K as Kinde Server
participant S as Stripe
participant DB as Billing DB
User->>K: Select plan with trial (UI shows "Free trial for N day(s)")
K->>S: Create subscription with trial settings (trial_length, trial_end)
S-->>K: Subscription created (trial window active)
K->>DB: Store trial metadata & expose token claims (`has_trial_period`, `trial_expires_on`)
K-->>User: Issue access token (includes trial claims)
Note right of S: Near trial end
S->>K: (Webhook) Trial ending / subscription imminent
K->>User: Prompt for payment details (if configured)
User->>K: Submit payment details
K->>S: Attach payment method / confirm
S->>K: Charge / convert subscription on trial expiry
K->>DB: Update subscription status
K-->>User: Billing status update / access maintained per subscription
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
tamalchowdhury
changed the title
Deploying kinde-docs-preview with
|
| Latest commit: |
8e1dca6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://352d8486.kinde-docs-preview.pages.dev |
| Branch Preview URL: | https://tamal-update-billing-trials.kinde-docs-preview.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
src/content/docs/billing/about-billing/billing-faq.mdx (1)
118-127: Keep the FAQ high-level; link out for detailed trial constraints.Lines 122-123 duplicate trial defaults/constraints that are already documented in the plan-setup guide. Consider trimming this FAQ answer to behavior + one canonical link to reduce doc drift.
Based on learnings: In MDX docs, follow “document once, reference anywhere” to avoid duplicated parameter/spec detail.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/about-billing/billing-faq.mdx` around lines 118 - 127, This FAQ duplicates plan-setup specifics; edit src/content/docs/billing/about-billing/billing-faq.mdx to remove the detailed defaults from the "Trial length" and "Credit card prompt" bullet points (the "(default 30, minimum 1)" and "(default 3)") and keep a single high-level sentence describing trial behavior (customers get a configurable trial period that converts to a paid subscription) plus one canonical link to the Create plans — Configure trial period page; ensure the "Ask for credit card" note remains and the link text stays as the canonical reference.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/billing/about-billing/about-billing.mdx`:
- Line 62: The sentence "It would be amazing if you can send any feedback you
have [support@kinde.com](mailto:support@kinde.com) so we can quickly collect and
prioritize improvements." is awkward; replace it with a polished, professional
line such as: "Please send any feedback to support@kinde.com so we can collect
and prioritize improvements promptly." Update the content in the same paragraph
where that sentence appears to use this revised wording and ensure the mailto
link remains intact.
In `@src/content/docs/billing/about-billing/billing-faq.mdx`:
- Line 20: The frontmatter `updated: 2026-04-08` is set to a future date;
replace that value with a non-future date (e.g., today's or the merge date) so
the `updated` metadata in the billing-faq document is not ahead of the PR
date—locate the `updated:` frontmatter entry in
src/content/docs/billing/about-billing/billing-faq.mdx and change `2026-04-08`
to the appropriate current/merge date.
In
`@src/content/docs/billing/billing-user-experience/customize-billing-pages.mdx`:
- Line 56: Update the "2. **Payment details**" bullet to explicitly state that
the "skip payment details" exception does not apply to trial plans: after the
sentence about trial plans showing the screen later, add a clear sentence such
as "Note: trial plans cannot skip the payment details screen — users on trials
must provide payment details when prompted before the trial ends." This targets
the "Payment details" bullet in the customize-billing-pages.mdx content to
prevent readers from assuming trials are skippable.
---
Nitpick comments:
In `@src/content/docs/billing/about-billing/billing-faq.mdx`:
- Around line 118-127: This FAQ duplicates plan-setup specifics; edit
src/content/docs/billing/about-billing/billing-faq.mdx to remove the detailed
defaults from the "Trial length" and "Credit card prompt" bullet points (the
"(default 30, minimum 1)" and "(default 3)") and keep a single high-level
sentence describing trial behavior (customers get a configurable trial period
that converts to a paid subscription) plus one canonical link to the Create
plans — Configure trial period page; ensure the "Ask for credit card" note
remains and the link text stays as the canonical reference.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 7c166764-416d-4ff8-8d45-eebb4d25330c
📒 Files selected for processing (10)
src/content/docs/billing/about-billing/about-billing.mdxsrc/content/docs/billing/about-billing/billing-concepts-terms.mdxsrc/content/docs/billing/about-billing/billing-faq.mdxsrc/content/docs/billing/about-billing/kinde-billing-faqs.mdxsrc/content/docs/billing/billing-user-experience/customize-billing-pages.mdxsrc/content/docs/billing/billing-user-experience/pricing-table-display.mdxsrc/content/docs/billing/get-started/build-plans.mdxsrc/content/docs/billing/manage-plans/about-plans.mdxsrc/content/docs/billing/manage-plans/create-plans.mdxsrc/content/docs/build/tokens/about-access-tokens.mdx
src/content/docs/billing/billing-user-experience/customize-billing-pages.mdx
Outdated
Show resolved
Hide resolved
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (2)
src/content/docs/billing/billing-user-experience/free-trials.mdx (2)
11-11: Remove duplicate content betweendescriptionandai_summary.The
description(line 11) andai_summary(line 28) fields contain identical text. If both fields are required, theai_summaryshould provide a different perspective, additional context, or a condensed version rather than duplicating the description verbatim.♻️ Suggested differentiation
Consider making the
ai_summarymore concise or removing it if it doesn't add value:-ai_summary: How to offer free trials on paid plans with Kinde Billing, what customers see in the auth and pricing flow, and how trials convert to paid subscriptions via Stripe. +ai_summary: Configure Stripe-based trials for paid plans with configurable trial length and optional credit card prompts.Alternatively, if
ai_summaryis auto-generated or optional, consider removing it entirely to avoid redundancy.Also applies to: 28-28
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/billing-user-experience/free-trials.mdx` at line 11, The frontmatter has duplicate text in the description and ai_summary fields; update the ai_summary for src/content/docs/billing/billing-user-experience/free-trials.mdx so it is either removed or rewritten to be a concise, distinct summary (e.g., a one-line condensed version or a different perspective) instead of copying the description verbatim; locate and edit the description and ai_summary keys in the file and ensure ai_summary provides added value or is omitted if optional.
58-67: Consider clarifying the credit card setting vs. prompt timing.The prerequisite section (line 62) states "Ask for credit card must be on" for trials, while the "No credit card required" section (lines 66-67) explains customers aren't prompted at signup. While technically accurate (the setting enables trials, but the prompt timing is separate), this could confuse readers on first read.
💡 Optional clarification
Consider adding a brief clarifier in the prerequisites section:
-**Ask for credit card** must be **on** for the plan. Trials cannot be enabled on plans where credit card collection is turned off. You can still use a **No credit card required** message in your own marketing; see below. +**Ask for credit card** must be **on** for the plan. This setting enables trial functionality; it does not mean customers are prompted immediately (see "No credit card required" below). Trials cannot be enabled on plans where credit card collection is turned off.Or leave as-is if you prefer the flow to reveal the detail progressively.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/billing-user-experience/free-trials.mdx` around lines 58 - 67, Add a one-sentence clarifier to the prerequisite section under "What do I need before offering a trial?" stating that the "**Ask for credit card** must be **on**" setting only enables trials but does not force immediate collection of payment details; reference the "Days before trial end to prompt for credit card" setting to explain that customers can still skip entering card details at signup and be prompted later. Update text near the "**Ask for credit card** must be **on**" line so readers immediately understand the distinction before they reach the "No credit card required" section.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@src/content/docs/billing/billing-user-experience/free-trials.mdx`:
- Line 11: The frontmatter has duplicate text in the description and ai_summary
fields; update the ai_summary for
src/content/docs/billing/billing-user-experience/free-trials.mdx so it is either
removed or rewritten to be a concise, distinct summary (e.g., a one-line
condensed version or a different perspective) instead of copying the description
verbatim; locate and edit the description and ai_summary keys in the file and
ensure ai_summary provides added value or is omitted if optional.
- Around line 58-67: Add a one-sentence clarifier to the prerequisite section
under "What do I need before offering a trial?" stating that the "**Ask for
credit card** must be **on**" setting only enables trials but does not force
immediate collection of payment details; reference the "Days before trial end to
prompt for credit card" setting to explain that customers can still skip
entering card details at signup and be prompted later. Update text near the
"**Ask for credit card** must be **on**" line so readers immediately understand
the distinction before they reach the "No credit card required" section.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 9b38f224-3fe9-4a3a-a9d1-25bfd690082f
📒 Files selected for processing (1)
src/content/docs/billing/billing-user-experience/free-trials.mdx
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/content/docs/billing/manage-plans/create-plans.mdx (1)
99-105: Consider clarifying the relationship between "Ask for credit card" toggle and the trial prompt setting.The documentation has two settings with similar names:
- The main "Ask for credit card" toggle (line 60-65) - controls upfront card collection at signup
- "Ask for credit card before trial ends (days)" (line 103) - controls background prompts before trial expiry
Since the main toggle must be ON for trials (per line 95), the trial setting appears to be for reminder prompts rather than initial collection. Consider either:
- Renaming the trial setting to something like "Prompt for payment confirmation (days before trial ends)"
- Adding a brief clarification that this setting triggers reminder prompts, not the initial card collection
📝 Suggested clarification
- Set **Ask for credit card before trial ends (days)** (default: 3, minimum: 0). This must be less than the trial length. This controls when the customer is asked to provide payment details before the trial expires. + Set **Ask for credit card before trial ends (days)** (default: 3, minimum: 0). This must be less than the trial length. Since credit card details are already collected at signup (when the "Ask for credit card" toggle is enabled), this setting controls when a background reminder is sent to confirm payment details are still valid before the trial expires.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/manage-plans/create-plans.mdx` around lines 99 - 105, Clarify the distinction between the main "Ask for credit card" toggle and the trial-specific "Ask for credit card before trial ends (days)" setting in the Trials section: update the text in the Trials block to either rename the latter to "Prompt for payment confirmation (days before trial ends)" or add one concise sentence explaining that the main "Ask for credit card" toggle controls upfront card collection at signup, while the "Ask for credit card before trial ends (days)" setting controls reminder prompts sent before trial expiry; reference the exact labels "Ask for credit card" (main toggle) and "Ask for credit card before trial ends (days)" so readers can map the behavior to the UI.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Around line 109-111: Update the sentence that currently reads "A background
process automatically prompts the customer to add payment details the configured
number of days before the trial ends" to clarify that the system prompts
customers to verify or update existing payment details (not add them) when the
"Ask for credit card" option is enabled; ensure the revised text references the
trial signup behavior ("When a customer subscribes to a trial plan, they get
full access... no payment is collected upfront") and the "Ask for credit card"
requirement so readers understand the prompt is for verification/update of card
details rather than initial collection.
---
Nitpick comments:
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Around line 99-105: Clarify the distinction between the main "Ask for credit
card" toggle and the trial-specific "Ask for credit card before trial ends
(days)" setting in the Trials section: update the text in the Trials block to
either rename the latter to "Prompt for payment confirmation (days before trial
ends)" or add one concise sentence explaining that the main "Ask for credit
card" toggle controls upfront card collection at signup, while the "Ask for
credit card before trial ends (days)" setting controls reminder prompts sent
before trial expiry; reference the exact labels "Ask for credit card" (main
toggle) and "Ask for credit card before trial ends (days)" so readers can map
the behavior to the UI.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 765e1dec-91d1-43c0-aad1-b8a896ea3124
📒 Files selected for processing (1)
src/content/docs/billing/manage-plans/create-plans.mdx
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/content/docs/billing/manage-plans/create-plans.mdx (1)
58-61:⚠️ Potential issue | 🟠 MajorClarify card-collection behavior when trials are enabled.
Line 60 says enabled always prompts during signup, but Lines 77 and 98-100 describe trial flows where payment details are collected later. This is internally inconsistent and may cause incorrect setup decisions.
Suggested doc fix
-- **Enabled (default)**: Users will be prompted to enter their payment details during signup via a secure Stripe payment form. +- **Enabled (default)**: For non-trial subscriptions, users are prompted to enter payment details during signup via a secure Stripe payment form. For trial-enabled plans, users are prompted based on **Ask for credit card before trial ends (days)**.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/manage-plans/create-plans.mdx` around lines 58 - 61, The description for the "card collection" toggle is inconsistent with the trial flow sections: update the toggle text (the paragraph starting "This toggle controls whether users must enter credit card details when subscribing to the plan.") so it clarifies behavior when trials are enabled—explain that when the toggle is Enabled users are required to provide payment details at signup only for non-trial signups or for plans configured to collect cards upfront, but if a plan enables a free trial the system can defer card collection until trial conversion (as described in the "trial" sections); ensure the toggle paragraph references the trial flow sections (the trial explanation paragraphs later in the document) and add a short note linking to the trial behavior examples so readers understand when card collection happens immediately vs. later.
🧹 Nitpick comments (1)
src/content/docs/billing/manage-plans/create-plans.mdx (1)
122-122: Tighten repeated “yearly” wording.This sentence repeats “yearly” and reads a bit heavy.
Suggested wording
- A fixed charge is a recurring charge such as base price or subscription fee. You can set **billing intervals** (daily, weekly, monthly, or yearly) and optionally **offer the charge as annual** with a custom yearly price when customers choose yearly billing. + A fixed charge is a recurring charge such as base price or subscription fee. You can set **billing intervals** (daily, weekly, monthly, or yearly) and optionally **offer the charge as annual** with a custom annual price for customers who choose yearly billing.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/manage-plans/create-plans.mdx` at line 122, Revise the sentence starting "A fixed charge is a recurring charge such as base price or subscription fee..." to eliminate the repeated use of "yearly" and tighten the phrasing; for example, reword to something like: "You can set billing intervals (daily, weekly, monthly, or yearly) and optionally offer the charge at a custom annual price for customers who choose yearly billing." Locate and update the sentence in the create-plans content (the paragraph describing billing intervals and annual offering) to use the new tightened phrasing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Line 152: Update the sentence that currently reads "is included on the pricing
table as free plan" to "is included on the pricing table as a free plan" so the
article uses correct grammar; locate and edit the sentence in the create free
plan paragraph (the line with "To create a free plan, set the **Price** to
`0.00`. This ensures the plan is added to Stripe, and is included on the pricing
table as free plan.") and insert the missing article "a" before "free plan".
- Line 109: The sentence in create-plans.mdx ("When the trial period ends,
Stripe automatically converts the subscription to a paid subscription.") is too
absolute; update the copy to make conversion conditional on a valid payment
method and any account/payment requirements being in place. Change the sentence
in the trial/transition section (around the trial description) to something
like: "At the end of the trial, the subscription will convert to a paid
subscription only if valid payment details are on file; otherwise the
subscription may be canceled or require manual payment setup." Ensure the text
mentions "valid payment method on file" and removes the implication that
conversion is guaranteed.
---
Outside diff comments:
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Around line 58-61: The description for the "card collection" toggle is
inconsistent with the trial flow sections: update the toggle text (the paragraph
starting "This toggle controls whether users must enter credit card details when
subscribing to the plan.") so it clarifies behavior when trials are
enabled—explain that when the toggle is Enabled users are required to provide
payment details at signup only for non-trial signups or for plans configured to
collect cards upfront, but if a plan enables a free trial the system can defer
card collection until trial conversion (as described in the "trial" sections);
ensure the toggle paragraph references the trial flow sections (the trial
explanation paragraphs later in the document) and add a short note linking to
the trial behavior examples so readers understand when card collection happens
immediately vs. later.
---
Nitpick comments:
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Line 122: Revise the sentence starting "A fixed charge is a recurring charge
such as base price or subscription fee..." to eliminate the repeated use of
"yearly" and tighten the phrasing; for example, reword to something like: "You
can set billing intervals (daily, weekly, monthly, or yearly) and optionally
offer the charge at a custom annual price for customers who choose yearly
billing." Locate and update the sentence in the create-plans content (the
paragraph describing billing intervals and annual offering) to use the new
tightened phrasing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: e9b2252e-0480-432b-abe7-453f624e0ea6
📒 Files selected for processing (1)
src/content/docs/billing/manage-plans/create-plans.mdx
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (3)
src/content/docs/billing/manage-plans/create-plans.mdx (2)
95-99: Field name inconsistency between step and reference table.Line 99 uses "Ask for credit card before trial ends (days)" but the configuration reference table on line 117 uses "Days before trial end to prompt for credit card". The latter matches the wording in
free-trials.mdx(line 43). Consider aligning the step text with the table for consistency.📝 Suggested fix
-3. Set **Ask for credit card before trial ends (days)** (default: 3, minimum: 0). This must be less than the trial length. This controls when the customer is asked to provide payment details before the trial expires. +3. Set **Days before trial end to prompt for credit card** (default: 3, minimum: 0). This must be less than the trial length. This controls when the customer is asked to provide payment details before the trial expires.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/manage-plans/create-plans.mdx` around lines 95 - 99, The step text in the "Trials" section uses the field label "**Ask for credit card before trial ends (days)**" which is inconsistent with the configuration reference table and free-trials.mdx that use "**Days before trial end to prompt for credit card**"; update the step wording to exactly match the reference table label ("Days before trial end to prompt for credit card (days)") so the field name is consistent across the document and with free-trials.mdx.
122-122: Minor: "yearly" repetition.Static analysis flagged "custom yearly price when customers choose yearly billing" as repetitive. This is a minor style concern.
📝 Suggested alternative
-A fixed charge is a recurring charge such as base price or subscription fee. You can set **billing intervals** (daily, weekly, monthly, or yearly) and optionally **offer the charge as annual** with a custom yearly price when customers choose yearly billing. +A fixed charge is a recurring charge such as base price or subscription fee. You can set **billing intervals** (daily, weekly, monthly, or yearly) and optionally **offer the charge as annual** with a custom yearly price when customers choose annual billing.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/manage-plans/create-plans.mdx` at line 122, The sentence currently reads "custom yearly price when customers choose yearly billing" and is repetitive; update the phrasing in the sentence that defines a fixed charge (the line mentioning "billing intervals" and "offer the charge as annual") to remove redundancy—for example replace that clause with "a custom price for annual billing" or similar concise wording so the line reads smoothly without repeating "yearly".src/content/docs/billing/billing-user-experience/free-trials.mdx (1)
64-66: Consider clarifying the "No credit card required" nuance.The explanation that "Ask for credit card must still be on" while simultaneously advertising "No credit card required" is correct but initially reads as contradictory. The key distinction is that card collection happens later (based on the days-before-trial-end setting), not at signup—but a reader skimming this section might be confused.
A small wording tweak could help:
📝 Suggested clarification
-Yes. You can show a **No credit card required** message on your landing page or elsewhere in your product. In Kinde, **Ask for credit card** must still be **on** so that trials are allowed, but customers are **not** asked for payment details at signup. They are prompted later, based on **Days before trial end to prompt for credit card** (by default, **3** days before the trial ends). +Yes. You can show a **No credit card required** message on your landing page or elsewhere in your product. In Kinde, **Ask for credit card** must still be **on** so that trials are allowed, but customers are **not** asked for payment details **at initial signup**. Instead, they are prompted for payment details later—specifically, the number of days before the trial ends that you configure in **Days before trial end to prompt for credit card** (by default, **3** days before the trial ends).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/content/docs/billing/billing-user-experience/free-trials.mdx` around lines 64 - 66, Clarify the apparent contradiction in the "Can I advertise 'No credit card required' for a trial?" section by explicitly stating that although the "Ask for credit card" toggle must be enabled, customers are not prompted for payment details at signup; instead, collection happens later according to the "Days before trial end to prompt for credit card" setting (default 3 days). Edit the paragraph that mentions "Ask for credit card must still be on" to add one short sentence or parenthetical like "this enables later collection; customers aren't asked for payment details at signup" and optionally give the default timing so readers skimming won't be confused.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@src/content/docs/billing/billing-user-experience/free-trials.mdx`:
- Around line 64-66: Clarify the apparent contradiction in the "Can I advertise
'No credit card required' for a trial?" section by explicitly stating that
although the "Ask for credit card" toggle must be enabled, customers are not
prompted for payment details at signup; instead, collection happens later
according to the "Days before trial end to prompt for credit card" setting
(default 3 days). Edit the paragraph that mentions "Ask for credit card must
still be on" to add one short sentence or parenthetical like "this enables later
collection; customers aren't asked for payment details at signup" and optionally
give the default timing so readers skimming won't be confused.
In `@src/content/docs/billing/manage-plans/create-plans.mdx`:
- Around line 95-99: The step text in the "Trials" section uses the field label
"**Ask for credit card before trial ends (days)**" which is inconsistent with
the configuration reference table and free-trials.mdx that use "**Days before
trial end to prompt for credit card**"; update the step wording to exactly match
the reference table label ("Days before trial end to prompt for credit card
(days)") so the field name is consistent across the document and with
free-trials.mdx.
- Line 122: The sentence currently reads "custom yearly price when customers
choose yearly billing" and is repetitive; update the phrasing in the sentence
that defines a fixed charge (the line mentioning "billing intervals" and "offer
the charge as annual") to remove redundancy—for example replace that clause with
"a custom price for annual billing" or similar concise wording so the line reads
smoothly without repeating "yearly".
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 1fc7d5d7-e0f1-4bd9-a7c2-b6529eec0075
📒 Files selected for processing (6)
src/content/docs/billing/about-billing/about-billing.mdxsrc/content/docs/billing/about-billing/billing-faq.mdxsrc/content/docs/billing/about-billing/kinde-billing-faqs.mdxsrc/content/docs/billing/billing-user-experience/customize-billing-pages.mdxsrc/content/docs/billing/billing-user-experience/free-trials.mdxsrc/content/docs/billing/manage-plans/create-plans.mdx
🚧 Files skipped from review as they are similar to previous changes (3)
- src/content/docs/billing/billing-user-experience/customize-billing-pages.mdx
- src/content/docs/billing/about-billing/about-billing.mdx
- src/content/docs/billing/about-billing/kinde-billing-faqs.mdx
tamalchowdhury
changed the title
onderay
approved these changes
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description (required)
Related issues & labels (optional)
Summary by CodeRabbit