Create the checkout config
Name the product, choose credit packs or plans, add the domain that will host the widget, and set the callback URL your product controls.
Stripe Checkout router for small product sites
Checkout handoff for products that do not need a billing team.
BitterCheckout gives an existing site a hosted payment path: define what you sell, use your Stripe account, paste the widget, and receive a callback when Stripe confirms payment. Your product still owns credits, access, and fulfillment.
Session routerEmbeddable widgetCallback handoffNot a ledger
Your siteButton or pricing page
BitterCheckoutConfig, widget, session request
Stripe CheckoutHosted payment collection
Your fulfillmentCredits, access, delivery
Seller path
From first config to a payment-ready embed.
Connect the Stripe handoff
Use your Stripe keys for the first live path. Stripe remains the payment processor and payout destination.
Paste the widget
Add the script and mark the buy button. BitterCheckout opens the selector and asks Stripe for the checkout session.
Test the callback
Before launch, verify your product receives the completion payload and grants the right credit, access, or entitlement.
<!-- Seller page embed -->
<scriptsrc="https://bittercheckout.com/widget.js"data-site="your-product"></script>
<buttondata-checkout-open>Buy credits</button>
<scriptsrc="https://bittercheckout.com/widget.js"data-site="your-product"></script>
<buttondata-checkout-open>Buy credits</button>
Trust boundaries
Clear ownership at every step.
Stripe owns payment processing
Card data, hosted checkout, payment methods, receipts, disputes, and payouts stay inside Stripe.
BitterCheckout owns the handoff
The service stores checkout configuration, renders the widget, creates sessions, and sends completion callbacks.
Your product owns fulfillment
Your app remains the system of record for customers, credits, subscriptions, access, delivery, refunds policy, and support decisions.
Good fit
Credit packs, small subscriptions, paid tools, gated downloads, operator utilities, and static sites that need a checkout path without building a session service.
Not the system of record
BitterCheckout does not replace your ledger, grant credits by itself, store card data, or decide whether a customer should receive access.
Questions before first payment
Can I accept live payments today?
You can create a config for your Stripe account and embed the widget. Treat a property as live only after your Stripe keys, checkout session, redirect URL, and fulfillment callback have been verified for that property.
Do I need a backend?
You do not need to build the checkout-session backend. You still need a callback or fulfillment path if your product must grant credits, access, files, or other entitlements after payment.
Which payment methods appear?
Stripe Checkout decides the available payment methods for the buyer, browser, region, and Stripe account settings. BitterCheckout routes the buyer into that hosted Stripe flow.
Where do buyers get support?
Your product owns buyer support and fulfillment decisions. BitterDesk is the operator support route for embed setup, redirect behavior, and callback wiring.