Add checkout and subscriptions to your web app without putting a restricted key in the browser.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Builds checkout, billing portal, subscription state, and the server handlers that own payment decisions.
Uses the publishable key in the client and resolves the restricted key only inside server tools.
Registers the deployed webhook endpoint and verifies the connected Stripe account before launch.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
Restricted server key with only the Stripe resource permissions documented by the installed skill.
Create or manage this keyPublishable key used by Stripe.js in the app client.
Create or manage this keyA blocker comes with the next move
Contrast probes https://api.stripe.com/v1 from the server. It classifies a missing key, invalid key or permission, and an unreachable provider separately instead of returning a generic failure.
Each blocked result explains what failed and links to the provider screen where you can fix it. Run verification again and the project moves to Verified only after the provider accepts the probe.
Keep checkout and webhooks on one path
The agent wires the customer-facing flow and the deployed webhook together, so a successful checkout and the app database agree without a separate dashboard checklist.