Stripe Payments

Manage Stripe customers, payments, invoices, subscriptions, checkout sessions, and payouts via the Stripe API.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Stripe API access yourself.

Setup in 3 Steps

Step 1: Install	Step 2: Pair Account	Step 3: Connect Stripe
		App-specific connection GIF coming soon
Run the install command in OpenClaw	Sign in and approve the device	Open the dashboard and connect Stripe

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   Stripe API      │
│   (User Chat)   │     │   (OAuth)    │     │                  │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Stripe    │                       │
         │                       │  4. Secure Token     │
         │                       │  5. Proxy Requests   │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │  Stripe  │
   │  File    │           │ Auth     │           │  Account │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Stripe again."

Quick Start

# List customers
clawlink_call_tool --tool "stripe_list_customers" --params '{"limit": 10}'

# Get a payment intent
clawlink_call_tool --tool "stripe_get_payment_intent" --params '{"payment_intent_id": "pi_1234567890"}'

# List subscriptions
clawlink_call_tool --tool "stripe_list_subscriptions" --params '{"limit": 10}'

Authentication

All Stripe tool calls are authenticated automatically by ClawLink using the user's connected Stripe account OAuth token.

No API key is required in chat. ClawLink stores the API key securely and injects it into every Stripe API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=stripe and connect Stripe.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for stripe in the list.

Verify Connection

clawlink_list_tools --integration stripe

Response: Returns the live tool catalog for Stripe.

Reconnect

If Stripe tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=stripe
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration stripe

Security & Permissions

• Access is scoped to the Stripe account connected during OAuth setup and the permissions granted.
• All write operations require explicit user confirmation. Refunds, cancellations, and chargebacks are high-impact — confirm explicitly.
• Never commit payment amounts or fee calculations from memory — always pull from Stripe.
• Test mode and live mode operate on separate data — confirm which mode is in use.

Tool Reference

Customers

Payment Intents & Charges

Subscriptions

Invoices

Checkout Sessions

Products & Pricing

Coupons & Discounts

Billing Portal

Disputes & Fraud

Payouts

Payment Methods

Setup Intents

Code Examples

List recent customers

clawlink_call_tool --tool "stripe_list_customers" \
  --params '{
    "limit": 10,
    "email": "example.com"
  }'

Create a payment intent

clawlink_call_tool --tool "stripe_create_payment_intent" \
  --params '{
    "amount": 5000,
    "currency": "usd",
    "customer": "cus_1234567890",
    "description": "Order #12345"
  }'

Create a customer

clawlink_call_tool --tool "stripe_create_customer" \
  --params '{
    "email": "[email protected]",
    "name": "Jane Doe",
    "metadata": {
      "internal_id": "CUST-001"
    }
  }'

Create a checkout session

clawlink_call_tool --tool "stripe_create_checkout_session" \
  --params '{
    "mode": "subscription",
    "line_items": [
      {
        "price": "price_1234567890",
        "quantity": 1
      }
    ],
    "success_url": "https://example.com/success",
    "cancel_url": "https://example.com/cancel"
  }'

Create a refund

clawlink_call_tool --tool "stripe_create_refund" \
  --params '{
    "charge": "ch_1234567890",
    "amount": 2500
  }'

Create a subscription

clawlink_call_tool --tool "stripe_create_subscription" \
  --params '{
    "customer": "cus_1234567890",
    "items": [
      {
        "price": "price_1234567890"
      }
    ],
    "payment_behavior": "default_incomplete"
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Stripe is connected.
2. Call clawlink_list_tools --integration stripe to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration stripe.
5. If no Stripe tools appear, direct the user to https://claw-link.dev/dashboard?add=stripe.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe                            │
│                                                             │
│  Example: List customers → Get customer → Show details    │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → call                      │
│                                                             │
│  Example: Preview refund → User approves → Process refund   │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, get, and search operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• All monetary amounts in Stripe are in the smallest currency unit (cents for USD).
• Payment intents must be confirmed before processing — check the status after creation.
• Subscriptions can have multiple items (prices) — always specify the price ID, not just the product ID.
• Refunds can only be processed on captured charges — uncaptured charges must be cancelled instead.
• Dispute/chargeback responses must be submitted through the Stripe dashboard, not the API.
• Test mode and live mode are completely separate — confirm which environment is in use.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

   openclaw plugins list
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
3. If a fresh chat does not help, run:

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Payment Fails

1. Verify the customer exists and has valid payment methods attached.
2. Check the PaymentIntent status — some require additional confirmation steps.
3. Confirm the amount is in the smallest currency unit (cents), not dollars.
4. Ensure the currency matches the payment method type.

Resources

• Stripe API Documentation
• Stripe REST API Reference
• Stripe Payment Intents
• Stripe Subscriptions
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=clawlink-stripe
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Powered by ClawLink — an integration hub for OpenClaw