← Back to Skills Marketplace
22752
Downloads
29
Stars
0
Active Installs
22
Versions
Install in OpenClaw
/install stripe-api
Description
Stripe API integration with managed OAuth. This is a write-capable financial integration for customers, subscriptions, invoices, products, prices, and payments. Install only if you need Stripe administration. Connect with the least-privileged Stripe account and OAuth scopes available, verify the intended connection ID before each request, and revoke unused connections promptly. All write operations require explicit user approval showing the exact endpoint, target resource, object IDs, amounts, and test/live mode before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI after `maton login`; the Stripe credential stays in the gateway and is never handled locally. Only your own Maton credential is used locally — held by the CLI, or supplied as `MATON_API_KEY` in the appendix fallback. Default to read and list calls, stay on the endpoints this skill documents, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Stripe connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Stripe action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Stripe examples; they add no Stripe capability - Stripe is itself an event source, so its own events are in `references/stripe/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install only if you need Stripe administration. Use the CLI/OAuth path, connect the least-privileged Stripe account, verify test versus live mode before any write, require explicit confirmation for charges, refunds, invoice, subscription, or deletion actions, and avoid the raw HTTP fallback unless the CLI cannot be used.
Capability Assessment
Credentials
Network access, Maton authentication, and Stripe account access are proportionate to the integration. The raw HTTP fallback uses MATON_API_KEY only for environments without the CLI and includes secret-handling warnings.
Install Mechanism
Installation uses a pinned Maton CLI package or Homebrew tap and OAuth login; the artifact contains Markdown guidance and no executable install script.
Instruction Scope
The instructions default to read/list calls, require explicit approval for writes, warn that the generic gateway can reach any /stripe/ path, and treat undocumented endpoints as user-requested exceptions; one appendix fallback contains an incorrect JSON-body instruction for Stripe writes.
Persistence & Privilege
The skill documents persistent credential storage, hosted functions, triggers, and destinations, but frames them as user-approved automation, defaults functions to DENY_ALL networking, warns about persistent forwarding, and includes deletion guidance.
Purpose & Capability
The skill is intentionally write-capable for Stripe customers, subscriptions, invoices, products, prices, payments, coupons, and refunds; that is high-impact financial access but matches the stated purpose and is repeatedly disclosed.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install stripe-api - After installation, invoke the skill by name or use
/stripe-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.7
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.6
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.5
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.4
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.3
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.2
Strengthen the financial-safety rules to match the api-gateway routing reference: replace the generic high-impact category list with Stripe's actual money operations, require a livemode check before anything that moves funds, forbid blind retries after an ambiguous failure and document Idempotency-Key, and name Stripe's own fields as the untrusted-input sources
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.1
- Removed the sample skill-card.md file.
- Documentation clarified that Stripe credentials remain in the gateway and are never handled locally.
- Adjusted instructions for initiating Stripe API calls and emphasized the reviewed endpoint boundary.
- Minor updates to language and security section; no changes to API commands or functionality.
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.11
- Removed the sample file skill-card.md.
- No changes to functional code or documentation content.
- This update is a minor cleanup, removing an extraneous file from the package.
v1.0.10
stripe-api 1.0.10 Changelog
- Added installation instructions for CLI via NPM and Homebrew.
- Expanded Quick Start with CLI usage examples alongside Python.
- Documented CLI commands for connection and API management.
- Improved API documentation layout and examples for both CLI and Python.
- No breaking changes to API endpoints or functionality.
v1.0.9
**Security and admin flow upgrades for Stripe API integration.**
- Strengthened security and admin best-practice guidance: All write operations now require explicit user approval, detailing endpoint, object IDs, amounts, and test/live mode prior to execution.
- Emphasized least-privileged connection use: Connect only with needed OAuth scopes, confirm intended connection ID on each request, and promptly revoke unused connections.
- Updated documentation for stricter read-then-write workflow: Always verify target objects and context before any action.
- Changed API endpoint from `https://gateway.maton.ai/` to `https://api.maton.ai/`.
- Added warnings about financial impact and administrative responsibility for using this skill.
- Removed sample license file (LICENSE.txt).
v1.0.8
- Added a homepage field ("https://maton.ai") to the skill metadata.
- No other visible changes or updates to functionality.
v1.0.7
- Improved clarity and conciseness in the description and documentation.
- Expanded API reference with detailed endpoints, query parameters, and example responses for customers, products, prices, and balance endpoints.
- Added more example payloads and endpoint documentation for creating, updating, and deleting resources.
- Updated OAuth connection management instructions with revised sample connection IDs and responses.
- Removed homepage and compatibility metadata fields for simplification.
- General reorganization and formatting for better readability and easier navigation.
v1.0.6
No user-facing changes in this release.
v1.0.5
- Added homepage field ("https://maton.ai") to skill metadata for improved discoverability.
- No other changes to functionality or documentation.
v1.0.4
- Added a "clawdbot" metadata section specifying required environment variables and an emoji identifier.
- No other content or functional changes.
v1.0.3
No user-facing changes detected in this version.
- No updates or modifications were made to the skill files.
- Functionality, documentation, and usage remain unchanged from the previous version.
v1.0.2
- Added a note in the description linking to the api-gateway skill for other third party apps.
- Replaced all curl command examples with Python (urllib) alternatives for quick start and connection management sections.
- Added troubleshooting guidance for "Invalid API key" errors, including environment variable checks and warning about shell variable expansion when piping curl output.
- Included important usage tips for curl, such as using `curl -g` with brackets in URLs and potential issues with environment variable expansion when piping output.
- No code or functionality changes; documentation improvement only.
Metadata
Frequently Asked Questions
What is Stripe?
Stripe API integration with managed OAuth. This is a write-capable financial integration for customers, subscriptions, invoices, products, prices, and payments. Install only if you need Stripe administration. Connect with the least-privileged Stripe account and OAuth scopes available, verify the intended connection ID before each request, and revoke unused connections promptly. All write operations require explicit user approval showing the exact endpoint, target resource, object IDs, amounts, and test/live mode before execution. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI after `maton login`; the Stripe credential stays in the gateway and is never handled locally. Only your own Maton credential is used locally — held by the CLI, or supplied as `MATON_API_KEY` in the appendix fallback. Default to read and list calls, stay on the endpoints this skill documents, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Stripe connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Stripe action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Stripe examples; they add no Stripe capability - Stripe is itself an event source, so its own events are in `references/stripe/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 22752 downloads so far.
How do I install Stripe?
Run "/install stripe-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Stripe free?
Yes, Stripe is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Stripe support?
Stripe is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Stripe?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.7.
More Skills