Support
Last updated November 16, 2026
Support is by email, on every plan. Write to support@creditkit.dev or use the contact form. We don't offer phone, chat or video calls.
How fast we reply
| What's wrong | First reply within |
|---|---|
| Urgent: live purchases not adding credits, charges failing for all your users, or a security problem. Start the subject with “URGENT”. | 1 business day |
| Everything else: setup questions, billing, bugs that have a workaround, feature requests. | 2 business days |
Business days are Monday to Friday, excluding US public holidays, in US Pacific time. These are times to a first reply from a person, not to a fix. We'll tell you what we found and when to expect the next update.
Before you write
- Docs and error codes: every API error says what to fix.
- Your console's Get started page shows which setup step isn't working yet.
What to include
- Your project id (
proj_…) and whether it's Test or Live. - What you did, what you expected and what happened, with the time and timezone.
- Any ids involved: the error
code, a user id, a webhook event id (ev_…) or a Stripe event id (evt_…).
Never send a secret key (sk_…) or webhook secret. We'll never ask for one. If you sent one by mistake, rotate it under Keys & webhooks.
What we help with
Setting up and running CreditKit in your app: the SDKs, the API, the paywall, webhooks, Stripe Connect and your CreditKit plan.
We don't support your end users directly: you're the seller to them, so their questions and refunds go through you (you can grant or remove credits from the Customers page). We can't write or debug your own application code beyond the CreditKit parts, and we don't do custom development.
Reporting a security problem
Email support@creditkit.dev with “URGENT security” in the subject and enough detail to reproduce it. Please give us a chance to fix it before sharing it publicly. We reply within 1 business day.
Availability
We work to keep CreditKit running all the time, but we don't offer an uptime guarantee (SLA) or service credits. See the Terms.