Stripe App Setup

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

### Step 2: Collect the API Key

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/skills/stripe-app-setupThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Create and configure a Stripe restricted API key so the assistant can manage payments, subscriptions, and customers under its own scoped identity

---
name: stripe-app-setup
description: Create and configure a Stripe restricted API key so the assistant can manage payments, subscriptions, and customers under its own scoped identity
compatibility: "Designed for Vellum personal assistants"
metadata:
  icon: assets/icon.svg
  emoji: "💳"
  vellum:
    category: "commerce"
    display-name: "Stripe App Setup"
    user-invocable: true
    activation-hints:
      - "the user wants the assistant to read or manage their Stripe merchant account: customers, subscriptions, refunds, invoices, payouts"
---

## Overview

Set up a **Stripe restricted API key** so the assistant can interact with a Stripe account — querying customers, managing subscriptions, processing refunds, reading invoices, and monitoring payments as a scoped entity.

Restricted API keys (RAKs) limit access to only the specific Stripe resources the assistant needs, reducing the blast radius if a key is ever compromised. RAKs are drop-in replacements for secret keys — they work identically with every Stripe API.

**Total manual effort: ~2 interactions** — create the restricted key in the Dashboard and hand it over via secure prompt.

## Prerequisites

- User must have **admin or developer access** to the Stripe account
- User must be logged into the Stripe Dashboard in their browser

## Setup Flow

### Step 0: Check Existing Configuration

Before starting, check whether Stripe is already configured by running the check script:

```bash
bun skills/stripe-app-setup/scripts/check-config.ts
```

The script outputs JSON: `{ "configured": boolean, "details": string }`.

- If `configured` is `true` — Stripe is already set up. Offer to verify the connection or reconfigure.
- If `configured` is `false` — continue to Step 1.

### Step 1: Create the Restricted API Key

Direct the user to create a new restricted key:

> Open **https://dashboard.stripe.com/apikeys** and click **+ Create restricted key**.

When Stripe asks "How will you use this API key?", select **Providing this key to another website** and enter the assistant's name.

Guide them through the permissions. A good default for managing payments, customers, and subscriptions:

| Resource            | Access Level |
| ------------------- | ------------ |
| **Customers**       | Read & Write |
| **Charges**         | Read & Write |
| **Invoices**        | Read & Write |
| **Payment Intents** | Read & Write |
| **Subscriptions**   | Read & Write |
| **Products**        | Read         |
| **Prices**          | Read         |
| **Balance**         | Read         |
| **Disputes**        | Read         |
| **Payouts**         | Read         |

Adjust permissions up or down based on the user's needs. The principle of least privilege applies — only request what the assistant will actually use. For read-only monitoring, set everything to Read.

> Click **Create key** when done.

**Important:** The restricted key is revealed only once after creation. The user must copy it immediately.

### Step 2: Collect the API Key

After the user copies their restricted key, run the store script to securely collect and store it:

```bash
bun skills/stripe-app-setup/scripts/store-key.ts
```

The script opens a secure credential prompt in the user's app, stores the key in the encrypted vault with the correct injection templates for `api.stripe.com`, and exits. If it exits 0, the key is stored. Exit code **130** means the user cancelled the prompt — nothing was stored; that's a valid choice, not an error, so ask whether they'd like to try again rather than treating it as a failure. Any other non-zero exit is a real failure.

### Step 3: Verify

After storing the key, verify the connection:

```bash
curl -s https://api.stripe.com/v1/balance
```

Run with `network_mode: "proxied"` and the stripe credential. A successful response returns the account's balance object with `available` and `pending` arrays.

If the response returns a 401, the key is invalid or revoked. If 403, the key doesn't have the required permissions for the endpoint.

### Step 4: Report Success

Summarize with the completed checklist:

"Setup complete!
✅ Restricted API key configured
✅ Connection verified — balance accessible

Key type: Restricted API key (`rk_...`)
Permissions: {list the configured permission levels}
Key management: https://dashboard.stripe.com/apikeys"

## API Usage

After setup, use `bash` with `curl` to call the Stripe API. The credential proxy injects the `Authorization: Bearer` header automatically when using `network_mode: "proxied"` with the stripe credential.

### Common API Calls

**List customers:**

```bash
curl -s https://api.stripe.com/v1/customers?limit=10
```

**Create a customer:**

```bash
curl -s https://api.stripe.com/v1/customers \
  -d "[email protected]" \
  -d "name=Jane Doe"
```

**List recent payments:**

```bash
curl -s https://api.stripe.com/v1/payment_intents?limit=10
```

**List subscriptions:**

```bash
curl -s https://api.stripe.com/v1/subscriptions?limit=10
```

**Retrieve an invoice:**

```bash
curl -s https://api.stripe.com/v1/invoices/{invoice_id}
```

**Issue a refund:**

```bash
curl -s https://api.stripe.com/v1/refunds \
  -d "payment_intent={pi_id}"
```

All calls use `network_mode: "proxied"` with the stripe credential.

### Pagination

Stripe uses cursor-based pagination. Use `starting_after` with the last object's ID to page forward:

```bash
curl -s "https://api.stripe.com/v1/customers?limit=100&starting_after=cus_lastId"
```

### Sandbox vs Live

Stripe has separate sandbox and live modes with separate API keys. Keys starting with `rk_test_` are sandbox keys; `rk_live_` are live keys. The assistant uses whichever key the user provides.

## Credential Reference

All credentials are stored under `service: stripe`:

| Field     | Description                                   | When Set |
| --------- | --------------------------------------------- | -------- |
| `api_key` | Restricted API key (`rk_live_` or `rk_test_`) | Step

Excerpt, first 6,001 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-14
   !CAUTION B 89 / 100

   first audit · source 19bc86343b63

Questions about Stripe App Setup

• github.com/vellum-ai/vellum-assistant/tree/main/skills/stripe-ap — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology