Built for Manifest V3
Run the client in an extension page or service worker. Bundle code locally and request permission only for the API and your backend.
Chrome extension
Paid features for your extension.
Connect your own Stripe account, authenticate customers through your backend and check access inside your Manifest V3 extension.
Checkout in a browser tab
Open Stripe Checkout or Billing Portal in a normal tab. Keep payment attempt IDs across worker restarts and popup reloads.
Access from verified events
Your backend supplies the customer identity. Signed Stripe events drive access; a completed redirect never unlocks a paid feature by itself.
Dashboard and MCP
Choose Chrome. Get the right setup.
Onboarding skips native store identifiers. Configure your exact extension origin and hosted checkout return origin, connect Stripe, then use the extension integration prompt.
The adapter ships in the cashsdk-web npm package as cashsdk-web/extension. A runnable Manifest V3 example covers customer access, checkout, the billing portal, sign-out and payment attempts that survive a worker restart.
Checkout sells your Stripe subscriptions and one-time products. Before you publish to the Chrome Web Store, allow the store build's extension ID for Production and follow the go-live guide.
Connect your extension to paid access.
Use your existing customer accounts and Stripe prices.