Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/_partials/billing/enable-billing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,5 +8,5 @@ Clerk billing costs just 0.7% per transaction, plus Stripe's transaction fees wh

Once you have enabled billing, you will see the following **Payment gateway** options for collecting payments via Stripe:

- **Clerk development gateway**: A shared **test** Stripe account so developers can get started testing and building with billing **in development** without needing to create and configure a Stripe account.
- **Stripe account**: Use your own Stripe account.
- **Clerk development gateway**: A shared **test** Stripe account used for development instances. This allows developers to test and build billing flows **in development** without needing to create and configure a Stripe account.
- **Stripe account**: Use your own Stripe account for production. **A Stripe account created for a development instance cannot be used for production**. You will need to create a separate Stripe account for your production environment.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use your own Stripe account for production.

This implies a bit to me that you can't create your own Stripe account for development instances, but I guess the following sentences clarify 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I see what you mean. I guess from my understanding, in development, Clerk basically spins up a test account for you, so you don't need to create one? But in production, you'd need to create one, hence the addition of "for production". But, are you saying that one could create a Stripe account for development, and not use the one created by Clerk?

6 changes: 5 additions & 1 deletion docs/guides/billing/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,16 @@ Clerk billing allows your customers to purchase recurring subscriptions to your

### 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. However, Clerk plans to roll out support for this in the future.

### Can I see subscriptions in my Stripe account?

Clerk billing does not use Stripe products, prices, subscriptions, etc. Clerk manages plans and subscriptions/subscription items, and only uses Stripe for payment processing. You will still be able to see customer information, as well as payment information in your Stripe account.

### Can I use the same Stripe account for both dev and prod environments?

No. Stripe accounts created for development instances are sandbox/test accounts and cannot be used for production. For a production environment, you must create a separate Stripe account.

### Is Clerk a Merchant of Record (MoR) for transactions?

No, Clerk does not provide this service.
Expand Down