Clarify billing info to avoid confusion among users #2734
Conversation
SarahSoutoul
requested review from
alexisintech,
mauricioabreu and
mzhong9723
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
docs/guides/billing/overview.mdx
Outdated
| ### Can I use an existing Stripe account with Clerk billing? | ||
|
|
||
| Unfortunately, there is no way to use an existing business entity with Clerk billing. | ||
| Unfortunately, Clerk Billing requires a new Stripe account to be created through Clerk. While Clerk connects directly to Stripe to handle payments, subscriptions, and billing flows, you cannot use a Stripe account that is already tied to another business entity. |
There was a problem hiding this comment.
Subscriptions are managed by Clerk. Stripe is used solely as a payment processor
There was a problem hiding this comment.
I'd also suggest removing the word Unfortunately.
There was a problem hiding this comment.
Done: Refine answer FAQ
docs/guides/billing/overview.mdx
Outdated
|
|
||
| ### Can I use the same Stripe account for both dev and prod environments? | ||
|
|
||
| No. Stripe accounts created for development instances (using the Clerk development gateway) are sandbox/test accounts and cannot be used for production. For a production environment, you must create a separate Stripe account. |
There was a problem hiding this comment.
🙃 The "Clerk development gateway" is a Stripe account that can be used in development. Just a minor wording comment, I think the explanation makes sense overall.
There was a problem hiding this comment.
Removed the term here: Remove wording and refine
docs/guides/billing/overview.mdx
Outdated
| ### Can I use an existing Stripe account with Clerk billing? | ||
|
|
||
| Unfortunately, there is no way to use an existing business entity with Clerk billing. | ||
| Clerk Billing requires a new Stripe account to be created through Clerk. While Clerk uses Stripe as a payment processor, you cannot use a Stripe account that is already tied to another business entity. |
There was a problem hiding this comment.
We're currently working on supporting this! Not sure if that's something we should add in the docs though
There was a problem hiding this comment.
Yes, Mauricio told me, and good shout - I think it'll be good to add that.
There was a problem hiding this comment.
Done here: Remove wording and refine
|
@mzhong9723 could I get your eyes on this again? Thank you! |
🔎 Previews:
What does this solve?
This PR solves two Linear tickets at once:
The first issue is around clarifying the need for two separate Stripe accounts between dev and prod instances AND the second issue is around updating the first question of the FAQ to avoid confusion among users.
What changed?
Checklist