Integration Stripe
Stripe payments and billing
How to use this capability
Ways to interact with this capability — pick a path to jump to the relevant section below.
SDK
Call actions from Node or React apps using the Ossy SDK — typed payloads and workspace context built in.
View section ↓
MCP
Connect Cursor to http://localhost:3006/mcp when MCP tools are available for integration-stripe.
View section ↓
HTTP
Call actions over HTTP with Bearer token authentication — create a token in Profile for scripts and automation.
View section ↓
Background tasks
Event-driven and scheduled handlers run in the background — triggered by the platform, not invoked like actions.
View section ↓
Actions
Invokable intents — call directly via SDK, POST /actions, or MCP tools. This is the agent-facing surface, not background jobs.
Billing Portal
@ossy/stripe/actions/billing-portal
sdk.invoke('@ossy/stripe/actions/billing-portal', { … })POST /actions
{ "action": "@ossy/stripe/actions/billing-portal", "payload": { … } }Background tasks
Background and scheduled handlers — triggered by events or cron, not called via SDK, POST /actions, or MCP. Ids use the tasks/ path (distinct from actions/).
Billing Portal
@ossy/stripe/tasks/billing-portal
Create Checkout
@ossy/stripe/tasks/create-checkout
Resource types
Structured entities and templates registered for resources.
Subscription
@ossy/integration-stripe/schema/subscription
APIs
HTTP endpoints exposed by this capability.
Stripe.Webhook
stripe.webhook
/api/v0/webhooks/stripe
Integrations
Third-party connectors and credential requirements.
Stripe
stripe
Credentials: STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_ID