Skip to content

Update billing compliance doc #4194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Aug 3, 2025

Conversation

Blargian
Copy link
Member

Summary

Updates to the billing compliance doc

Checklist

@Blargian Blargian requested a review from a team as a code owner July 31, 2025 11:11
Copy link

vercel bot commented Jul 31, 2025

@Blargian is attempting to deploy a commit to the ClickHouse Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

vercel bot commented Jul 31, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
clickhouse-docs ✅ Ready (Inspect) Visit Preview Aug 2, 2025 11:13am

@rsickles
Copy link
Contributor

rsickles commented Jul 31, 2025

@Blargian some small edits:

  • Capitalize "Direct" in the last paragraph in the "Cloud marketplace pay-as-you-go billing" section - "for direct PAYG will apply - this includes service suspension and eventual data deletion"
  • In the section "Committed contract billing (COMMITTED SPEND CONTRACT)" remove "and credit" from this sentence "Payment terms will be set forth in the applicable order form and credit."
  • URL should change from "/docs/manage/troubleshooting-billing-issues" -> "/docs/manage/clickHouse-cloud-billing-compliance".
  • Add a space before "If.." here - "The credit card on file must be valid, not expired, and have enough available credit to cover your invoice total.If, for any reason, we are unable to charge the full amount due, the following unpaid invoice restrictions will immediately apply:"
  • Bold "order form" in this sentence "Credits applied to an organization (e.g. through committed contracts or refunds) are available for your use for the term specified in the order form or accepted private offer."

Otherwise LGTM!

@Blargian
Copy link
Member Author

Blargian commented Aug 1, 2025

@Blargian some small edits:

  • Capitalize "Direct" in the last paragraph in the "Cloud marketplace pay-as-you-go billing" section - "for direct PAYG will apply - this includes service suspension and eventual data deletion"
  • In the section "Committed contract billing (COMMITTED SPEND CONTRACT)" remove "and credit" from this sentence "Payment terms will be set forth in the applicable order form and credit."
  • URL should change from "/docs/manage/troubleshooting-billing-issues" -> "/docs/manage/clickHouse-cloud-billing-compliance".
  • Add a space before "If.." here - "The credit card on file must be valid, not expired, and have enough available credit to cover your invoice total.If, for any reason, we are unable to charge the full amount due, the following unpaid invoice restrictions will immediately apply:"
  • Bold "order form" in this sentence "Credits applied to an organization (e.g. through committed contracts or refunds) are available for your use for the term specified in the order form or accepted private offer."

Otherwise LGTM!

Thanks @rsickles, have made the changes. On the last point I don't see this sentence in the doc, the only "order form" I see is in "Contacting sales to buy credits directly, with payment options including ACH or wire transfer. Payment terms will be set forth in the applicable order form.". Am I missing something?

@rsickles
Copy link
Contributor

rsickles commented Aug 1, 2025

@Blargian oh whoops sorry for the miscommunication we need to add "order form" to that sentence (not bolded) so it reads "Credits applied to an organization (e.g. through committed contracts or refunds) are available for your use for the term specified in the order form or accepted private offer." Thanks!

@Blargian Blargian merged commit b57eb68 into ClickHouse:main Aug 3, 2025
9 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants