Last updated: November 12, 2026

Terms of Service

These Terms of Service (“Terms”) govern your access to and use of CreditKit's embeddable credit ledger, storefront widgets, SDKs, and Stripe Connect settlement infrastructure.

1. Scope of Infrastructure Service

CreditKit provides developer APIs, isolated Shadow DOM web widgets (creditkit.js), React hooks (useCreditKit), and a PostgreSQL FIFO credit ledger that enables software creators (“Developers”) to meter usage, issue free starter allowances, and sell prepaid credit packages or recurring subscriptions to their end-users (“Visitors”).

CreditKit acts strictly as a technical metering and checkout orchestration provider. CreditKit does not take custody of merchant funds or act as a money transmitter.

2. Stripe Connect Settlement & Platform Fees

Live payment processing is executed directly through Stripe Checkout and Stripe Connect. When a Visitor purchases a credit pack on your application, funds settle to your connected Stripe account (acct_...) according to your active project plan tier:

PlanSubscriptionApplication FeeWhite-Label
Starter$0/mo5.0%Required badge
Builder$29/mo2.0%White-label + Downsells & Promos
Studio$99/mo1.0%White-label + Live 50/50 A/B Split Lab

When Stripe notifies CreditKit of a charge.refunded or charge.dispute.created event, CreditKit automatically revokes the remaining unspent credits on the associated credit lot.

3. Two-Phase Holds & Upstream 5xx Auto-Refunds

When your application uses Two-Phase Reserve mode (mode: "reserve" or CreditKit.gate()), CreditKit places a 5-minute reservation lock on the Visitor's soonest-expiring credit lots.

If your upstream provider or backend service fails with a 5xx error or times out and your server issues a refund on the holdId (or lets the 5-minute TTL expire), the exact credit quantities are restored to their original lots.

4. API Keys, Authorized Origins & Security

Publishable keys (pk_live_... and pk_test_...) are designed for client-side embedding and are restricted to requests originating from your configured Authorized Origin (appUrl).

Secret keys (sk_live_...) grant administrative ledger access and must never be exposed in browser bundles or public repositories. If a Secret Key is compromised, you must rotate it immediately via the Roll Key control in the CreditKit Console.

5. Merchant Responsibilities & Acceptable Use

As the merchant of record on your connected Stripe account, you are solely responsible for customer support, applicable sales or VAT taxes, and dispute resolution with your end-users. You may not use CreditKit to sell unlawful goods, deceptive credit packs, or prohibited financial instruments under Stripe's Restricted Business List.

6. Warranties & Limitation of Liability

CreditKit is provided “as is” without warranties of any kind. In no event shall CreditKit's aggregate liability exceed the total platform fees paid by you to CreditKit in the twelve (12) months preceding the claim.

7. Service Operator, Governing Law & Legal Contact

These Terms constitute a binding agreement between you and CreditKit (“CreditKit”, “we”, “us”, or “our”), operating creditkit.dev. These Terms and any dispute arising out of or related to the Service are governed by the laws of the State of California and applicable federal laws of the United States, without regard to conflict-of-law principles, with exclusive venue in the state or federal courts located in San Francisco County, California.

For legal notices, billing questions, or security disclosures, contact support@creditkit.dev or use our Contact page.