> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Stripe

The Stripe connector lets your AI agent act in each user's Stripe account. Each user connects their own Stripe access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 178 tools.

**Authentication:** Bearer Token
**Categories:** Accounting & Finance, Developer Tools, Automation
**Tools:** 178: 78 read, 77 write, 23 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=STRIPE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Stripe connection

   In **AgentKit > Connections**, create a Stripe connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

   **Console steps with screenshots:**

   Register your Stripe Secret Key with Scalekit so it can authenticate requests on your behalf. This connector uses a Bearer token.

   1. ### Choose a sandbox or your live account

      Stripe separates every account into isolated environments: one or more **sandboxes** for testing, and the **live** account for real payments. Each environment has its own API keys, so pick the right one before you continue:

      - Use a **sandbox** (shown as **Test mode** in the dashboard) while you build and test your integration. Sandbox keys are prefixed `sk_test_` and `pk_test_`, and never move real money.
      - Switch to your **live** account only when you're ready to process real payments. Live keys are prefixed `sk_live_` and `pk_live_`.

      > caution: Never mix sandbox and live keys
      >
      > A sandbox Secret Key only works against that sandbox's data — it cannot see or affect your live account, and vice versa. If Scalekit requests fail with an authentication error, confirm you copied the key from the environment you intended.

   2. ### Get your Secret Key

      - Sign in to the [Stripe Dashboard](https://dashboard.stripe.com) and confirm the environment switcher in the top-left corner shows the sandbox or live account you want keys for.
      - Go to **Developers** → **API keys**.
      - Under **Standard keys**, click the **Secret key** row and reveal or copy its value.

        > Image: Stripe Developers > API keys page showing the Publishable key and Secret key under Standard keys

      > tip: Quick access from the Workbench
      >
      > The **Workbench** overview page (**Developers** → **Workbench**) also surfaces a **Testing tools** panel with your current sandbox's **Test keys** and a **View all API keys** shortcut — useful when you're already debugging a request there.
      >
      > > Image: Stripe Workbench overview page with a Testing tools panel showing the Publishable key and a hidden Secret key

      > caution: Never hard-code secrets
      >
      > Treat the Secret Key like a password — it grants full API access to whichever environment it belongs to. Store it in an environment variable or secrets manager, never in source code or version control.

   3. ### Add a connected account in Scalekit

      Connected accounts link a specific user identifier in your system to a Stripe Secret Key. Add one via the dashboard for testing, or via the Scalekit API in production. Use the Secret Key from step 2 as the `token` credential field — see **Set your credentials** above for the request shape.

      > note: Match your environment across every connected account
      >
      > If you run sandbox and live traffic through the same Scalekit connection, create separate connected accounts per user and environment so each one holds the matching `sk_test_` or `sk_live_` key.

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'stripe'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Stripe:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'stripe_create_invoice_preview_dahlia',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "stripe"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Stripe:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="stripe_create_invoice_preview_dahlia",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Stripe credentials there. If your app already has a user's credentials, add the account from your backend instead, as the console steps above show. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'stripe_create_invoice_preview_dahlia',
  toolInput: {},
  connector: 'stripe',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="stripe_create_invoice_preview_dahlia",
    tool_input={},
    connection_name="stripe",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `stripe_create_invoice_preview_dahlia`

Create Invoice Preview · Read-only

Previews the upcoming invoice for a customer or subscription without creating it, showing pending charges, renewal amounts, invoice item charges, and any applicable discounts or prorations.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `currency` (`string`, optional): The currency to preview this invoice in. Defaults to the customer's currency if not specified.
- `customer` (`string`, optional): The ID of the customer whose upcoming invoice you're previewing.
- `expand` (`array`, optional): List of fields to expand in the response.
- `invoice_items` (`array`, optional): List of ad-hoc invoice items to add to the preview (up to 250).
- `preview_mode` (`string`, optional): Whether to preview only the next invoice, or a full recurring schedule. Defaults to 'next'. One of: `next`, `recurring`.
- `subscription` (`string`, optional): The ID of the subscription to preview, e.g. to preview the effect of a plan change.
- `subscription_details` (`object`, optional): Overrides used to preview a subscription update, such as new items or a proration date.

Example input: `{}`

### `stripe_get_account_dahlia`

Get Account · Read-only

Retrieve the details of the current Stripe account.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `stripe_get_account_person_dahlia`

Get Account Person · Read-only

Retrieves an existing person associated with a connected account's legal entity.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `person` (`string`, required): The ID of the person to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"account":"<account>","person":"<person>"}`

### `stripe_get_balance_dahlia`

Get Balance · Read-only

Retrieve the current balance of the Stripe account, showing available and pending amounts by currency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `stripe_get_balance_transaction_dahlia`

Get Balance Transaction · Read-only

Retrieve a balance transaction by ID. Balance transactions represent funds moving through the Stripe account.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the balance transaction to retrieve.

Example input: `{"id":"<id>"}`

### `stripe_get_charge_dahlia`

Get Charge · Read-only

Retrieves the details of a charge that has previously been created. Supply the unique charge ID that was returned from your previous request, and Stripe will return the corresponding charge information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `charge_id` (`string`, required): The ID of the charge to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"charge_id":"<charge_id>"}`

### `stripe_get_checkout_session_dahlia`

Get Checkout Session · Read-only

Retrieve a Checkout Session by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session` (`string`, required): The ID of the Checkout Session to retrieve.

Example input: `{"session":"<session>"}`

### `stripe_get_checkout_session_line_items_dahlia`

Get Checkout Session Line Items · Read-only

Retrieves the full, paginated list of line items for a Checkout Session.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session_id` (`string`, required): The ID of the Checkout Session.
- `ending_before` (`string`, optional): Line item ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of line items to return (1-100, default 10).
- `starting_after` (`string`, optional): Line item ID to start pagination after.

Example input: `{"session_id":"<session_id>"}`

### `stripe_get_connected_account_dahlia`

Get Connected Account · Read-only

Retrieves the details of a connected account by ID. Use this to check onboarding status, requirements, and capabilities for a specific Connect account, as opposed to the platform's own account.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"account":"<account>"}`

### `stripe_get_coupon_dahlia`

Get Coupon · Read-only

Retrieve a coupon by its ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `coupon` (`string`, required): The ID of the coupon to retrieve.

Example input: `{"coupon":"<coupon>"}`

### `stripe_get_customer_dahlia`

Get Customer · Read-only

Retrieves the details of an existing customer. You need only supply the unique customer identifier that was returned upon customer creation.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_get_customer_payment_method_dahlia`

Get Customer Payment Method · Read-only

Retrieves a specific PaymentMethod that is attached to a given customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer the payment method is attached to.
- `payment_method_id` (`string`, required): The ID of the payment method to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"customer_id":"<customer_id>","payment_method_id":"<payment_method_id>"}`

### `stripe_get_customer_tax_id_dahlia`

Get Customer Tax ID · Read-only

Retrieves the tax ID object with the given identifier for a customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer the tax ID belongs to.
- `tax_id` (`string`, required): The ID of the tax ID object to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"customer_id":"<customer_id>","tax_id":"<tax_id>"}`

### `stripe_get_dispute_dahlia`

Get Dispute · Read-only

Retrieve a dispute by ID. A dispute occurs when a customer questions a charge with their card issuer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `dispute` (`string`, required): The ID of the dispute to retrieve.

Example input: `{"dispute":"<dispute>"}`

### `stripe_get_event_dahlia`

Get Event · Read-only

Retrieve an event by ID. Events are Stripe's way of notifying your application about changes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the event to retrieve.

Example input: `{"id":"<id>"}`

### `stripe_get_invoice_dahlia`

Get Invoice · Read-only

Retrieves the invoice with the given ID. Supply the unique invoice identifier that was returned from your previous request, and Stripe will return the corresponding invoice information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_get_invoice_item_dahlia`

Get Invoice Item · Read-only

Retrieves the invoice item with the given ID. Supply the unique invoice item identifier and Stripe will return the corresponding invoice item information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_item_id` (`string`, required): The ID of the invoice item to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"invoice_item_id":"<invoice_item_id>"}`

### `stripe_get_payment_intent_dahlia`

Get Payment Intent · Read-only

Retrieves the details of a PaymentIntent that was previously created. Supply the unique PaymentIntent ID and Stripe will return the corresponding PaymentIntent information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `payment_intent_id` (`string`, required): The ID of the PaymentIntent to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"payment_intent_id":"<payment_intent_id>"}`

### `stripe_get_payment_method_dahlia`

Get Payment Method · Read-only

Retrieve a PaymentMethod object.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the PaymentMethod to retrieve.

Example input: `{"id":"<id>"}`

### `stripe_get_payout_dahlia`

Get Payout · Read-only

Retrieve a payout by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `payout` (`string`, required): The ID of the payout to retrieve.

Example input: `{"payout":"<payout>"}`

### `stripe_get_plan_dahlia`

Get Plan · Read-only

Retrieve a Plan by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `plan` (`string`, required): The ID of the plan to retrieve.

Example input: `{"plan":"<plan>"}`

### `stripe_get_price_dahlia`

Get Price · Read-only

Retrieves the price with the given ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `price_id` (`string`, required): The ID of the price to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"price_id":"<price_id>"}`

### `stripe_get_product_dahlia`

Get Product · Read-only

Retrieves the details of an existing product. Supply the unique product ID from either a product creation request or the product list, and Stripe will return the corresponding product information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): The ID of the product to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"product_id":"<product_id>"}`

### `stripe_get_promotion_code_dahlia`

Get Promotion Code · Read-only

Retrieve a promotion code by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `promotion_code` (`string`, required): The ID of the promotion code to retrieve.

Example input: `{"promotion_code":"<promotion_code>"}`

### `stripe_get_quote_dahlia`

Get Quote · Read-only

Retrieve a Quote by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `quote` (`string`, required): The ID of the quote to retrieve.

Example input: `{"quote":"<quote>"}`

### `stripe_get_refund_dahlia`

Get Refund · Read-only

Retrieve the details of an existing refund.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The ID of the refund to retrieve.

Example input: `{"id":"<id>"}`

### `stripe_get_setup_intent_dahlia`

Get Setup Intent · Read-only

Retrieve a SetupIntent by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `setup_intent_id` (`string`, required): The ID of the SetupIntent to retrieve.

Example input: `{"setup_intent_id":"<setup_intent_id>"}`

### `stripe_get_subscription_dahlia`

Get Subscription · Read-only

Retrieves the subscription with the given ID. Supply the unique subscription identifier that was returned from your previous request, and Stripe will return the corresponding subscription information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription_id` (`string`, required): The ID of the subscription to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"subscription_id":"<subscription_id>"}`

### `stripe_get_subscription_item_dahlia`

Get Subscription Item · Read-only

Retrieves the subscription item with the given ID. Supply the unique subscription item identifier and Stripe will return the corresponding subscription item information.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription_item_id` (`string`, required): The ID of the subscription item to retrieve
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"subscription_item_id":"<subscription_item_id>"}`

### `stripe_get_subscription_schedule`

Get Subscription Schedule · Read-only

Retrieves the subscription schedule with the given ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription_schedule_id` (`string`, required): The ID of the subscription schedule to retrieve.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"subscription_schedule_id":"<subscription_schedule_id>"}`

### `stripe_get_tax_rate_dahlia`

Get Tax Rate · Read-only

Retrieve a tax rate by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `tax_rate` (`string`, required): The ID of the tax rate to retrieve.

Example input: `{"tax_rate":"<tax_rate>"}`

### `stripe_get_transfer_dahlia`

Get Transfer · Read-only

Retrieve a transfer by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `transfer` (`string`, required): The ID of the transfer to retrieve.

Example input: `{"transfer":"<transfer>"}`

### `stripe_get_transfer_reversal_dahlia`

Get Transfer Reversal · Read-only

Retrieves the details of a specific reversal stored on a transfer. By default only the 10 most recent reversals are stored directly on the transfer object; use this to retrieve any reversal by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `reversal_id` (`string`, required): The ID of the reversal to retrieve.
- `transfer_id` (`string`, required): The ID of the transfer the reversal belongs to.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"reversal_id":"<reversal_id>","transfer_id":"<transfer_id>"}`

### `stripe_get_webhook_endpoint_dahlia`

Get Webhook Endpoint · Read-only

Retrieve a webhook endpoint by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `webhook_endpoint` (`string`, required): The ID of the webhook endpoint to retrieve.

Example input: `{"webhook_endpoint":"<webhook_endpoint>"}`

### `stripe_list_account_capabilities_dahlia`

List Account Capabilities · Read-only

Returns a list of capabilities (such as card_payments or transfers) associated with a connected account, along with each capability's current status.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"account":"<account>"}`

### `stripe_list_account_external_accounts_dahlia`

List Account External Accounts · Read-only

Lists the external accounts (bank accounts and cards) attached to a connected account for receiving payouts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `ending_before` (`string`, optional): External account ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of external accounts to return (1-100, default 10).
- `object` (`string`, optional): Filter external accounts by object type. One of: `bank_account`, `card`.
- `starting_after` (`string`, optional): External account ID to start pagination after.

Example input: `{"account":"<account>"}`

### `stripe_list_account_persons_dahlia`

List Account Persons · Read-only

Returns a list of people associated with a connected account's legal entity, sorted by creation date with the most recent first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `ending_before` (`string`, optional): Person ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of persons to return (1-100, default 10).
- `relationship` (`object`, optional): Filter people by their relationship to the account's company (e.g. representative, owner, director, executive).
- `starting_after` (`string`, optional): Person ID to start pagination after.

Example input: `{"account":"<account>"}`

### `stripe_list_accounts_dahlia`

List Accounts · Read-only

List all connected accounts on your platform (Connect platforms only).

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ending_before` (`string`, optional): Cursor for pagination: return results before this account ID.
- `limit` (`integer`, optional): Maximum number of accounts to return (1–100).
- `starting_after` (`string`, optional): Cursor for pagination: return results after this account ID.

Example input: `{}`

### `stripe_list_application_fees`

List Application Fees · Read-only

Returns a list of application fees previously collected on charges made for connected accounts via Stripe Connect, most recent first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `charge` (`string`, optional): Only return application fees for the charge specified by this charge ID.
- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `ending_before` (`string`, optional): Application fee ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of application fees to return (1-100, default 10).
- `starting_after` (`string`, optional): Application fee ID to start pagination after.

Example input: `{}`

### `stripe_list_balance_transactions_dahlia`

List Balance Transactions · Read-only

List all balance transactions, optionally filtered by currency, source, or type.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `currency` (`string`, optional): Filter by three-letter ISO currency code.
- `ending_before` (`string`, optional): Balance transaction ID to end pagination before.
- `limit` (`integer`, optional): Number of transactions to return (1-100, default 10).
- `source` (`string`, optional): Filter by source object ID (charge or payout ID).
- `starting_after` (`string`, optional): Balance transaction ID to start pagination after.
- `type` (`string`, optional): Filter by transaction type. One of: `charge`, `refund`, `adjustment`, `payout`, `payout_failure`, `stripe_fee`, `network_cost`, `payment`, `payment_refund`, `transfer`, `transfer_cancel`, `transfer_failure`.

Example input: `{}`

### `stripe_list_billing_portal_configurations_dahlia`

List Billing Portal Configurations · Read-only

Returns a list of configurations that describe the functionality of the customer self-service billing portal.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Only return configurations that are active (true) or inactive (false).
- `ending_before` (`string`, optional): Configuration ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `is_default` (`boolean`, optional): Only return the default (true) or non-default (false) configuration.
- `limit` (`integer`, optional): Number of configurations to return (1-100, default 10).
- `starting_after` (`string`, optional): Configuration ID to start pagination after.

Example input: `{}`

### `stripe_list_charges_dahlia`

List Charges · Read-only

Returns a list of charges you've previously created. The charges are returned in sorted order, with the most recent charges appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Filter charges by customer ID
- `ending_before` (`string`, optional): Charge ID to end pagination before
- `limit` (`integer`, optional): Number of charges to return (1-100, default 10)
- `payment_intent` (`string`, optional): Filter charges by PaymentIntent ID
- `starting_after` (`string`, optional): Charge ID to start pagination after

Example input: `{}`

### `stripe_list_checkout_sessions_dahlia`

List Checkout Sessions · Read-only

List all Checkout Sessions.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer` (`string`, optional): Filter sessions by customer ID.
- `ending_before` (`string`, optional): Cursor for pagination. Returns sessions before this ID.
- `limit` (`integer`, optional): Maximum number of sessions to return (1-100).
- `payment_intent` (`string`, optional): Filter sessions by payment intent ID.
- `starting_after` (`string`, optional): Cursor for pagination. Returns sessions after this ID.
- `subscription` (`string`, optional): Filter sessions by subscription ID.

Example input: `{}`

### `stripe_list_coupons_dahlia`

List Coupons · Read-only

List all coupons.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ending_before` (`string`, optional): Cursor for pagination. Returns results before this coupon ID.
- `limit` (`integer`, optional): Maximum number of coupons to return (1–100).
- `starting_after` (`string`, optional): Cursor for pagination. Returns results after this coupon ID.

Example input: `{}`

### `stripe_list_credit_notes`

List Credit Notes · Read-only

Returns a list of credit notes, with the most recent appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Only return credit notes for the customer specified by this customer ID.
- `ending_before` (`string`, optional): Credit note ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `invoice` (`string`, optional): Only return credit notes for the invoice specified by this invoice ID.
- `limit` (`integer`, optional): Number of credit notes to return (1-100, default 10).
- `starting_after` (`string`, optional): Credit note ID to start pagination after.

Example input: `{}`

### `stripe_list_customer_balance_transactions_dahlia`

List Customer Balance Transactions · Read-only

Returns a list of transactions that have updated a customer's credit balance.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer whose balance transactions you want to list.
- `ending_before` (`string`, optional): Balance transaction ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of balance transactions to return (1-100, default 10).
- `starting_after` (`string`, optional): Balance transaction ID to start pagination after.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_list_customer_payment_methods_dahlia`

List Customer Payment Methods · Read-only

List all PaymentMethods attached to a specific customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer` (`string`, required): The ID of the customer whose payment methods to list.
- `ending_before` (`string`, optional): Cursor for pagination — return results before this payment method ID.
- `limit` (`integer`, optional): Maximum number of payment methods to return.
- `starting_after` (`string`, optional): Cursor for pagination — return results after this payment method ID.
- `type` (`string`, optional): Filter payment methods by type. One of: `acss_debit`, `affirm`, `afterpay_clearpay`, `alipay`, `au_becs_debit`, `bacs_debit`, `bancontact`, `blik`, `boleto`, `card`, `cashapp`, `customer_balance`, `eps`, `fpx`, `giropay`, `grabpay`, `ideal`, `klarna`, `konbini`, `link`, `mobilepay`, `oxxo`, `p24`, `paynow`, `paypal`, `pix`, `promptpay`, `sepa_debit`, `sofort`, `swish`, `us_bank_account`, `wechat_pay`, `zip`.

Example input: `{"customer":"<customer>"}`

### `stripe_list_customer_tax_ids_dahlia`

List Customer Tax IDs · Read-only

Returns a list of tax IDs registered for a customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer whose tax IDs you want to list.
- `ending_before` (`string`, optional): Tax ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of tax IDs to return (1-100, default 10).
- `starting_after` (`string`, optional): Tax ID to start pagination after.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_list_customers_dahlia`

List Customers · Read-only

Returns a list of your customers. The customers are returned sorted by creation date, with the most recent customers appearing first. Supports filtering by email and pagination for large customer lists.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `email` (`string`, optional): Filter customers by exact email address
- `ending_before` (`string`, optional): Customer ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of customers to return (1-100, default 10)
- `starting_after` (`string`, optional): Customer ID to start pagination after

Example input: `{}`

### `stripe_list_disputes_dahlia`

List Disputes · Read-only

List all disputes, optionally filtered by charge or payment intent.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `charge` (`string`, optional): Filter disputes by charge ID.
- `ending_before` (`string`, optional): Cursor for pagination: return disputes before this dispute ID.
- `limit` (`integer`, optional): Maximum number of disputes to return (1-100).
- `payment_intent` (`string`, optional): Filter disputes by payment intent ID.
- `starting_after` (`string`, optional): Cursor for pagination: return disputes after this dispute ID.

Example input: `{}`

### `stripe_list_events_dahlia`

List Events · Read-only

List all events. Events represent noteworthy activity on your Stripe account.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ending_before` (`string`, optional): Cursor for pagination: return events before this event ID.
- `limit` (`integer`, optional): Maximum number of events to return (1-100).
- `starting_after` (`string`, optional): Cursor for pagination: return events after this event ID.
- `type` (`string`, optional): Filter events by type, e.g. payment_intent.created.

Example input: `{}`

### `stripe_list_invoice_items_dahlia`

List Invoice Items · Read-only

Returns a list of your invoice items. Invoice items are returned sorted by creation date, with the most recent invoice items appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Filter invoice items by customer ID
- `ending_before` (`string`, optional): Invoice item ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `invoice` (`string`, optional): Filter invoice items by invoice ID
- `limit` (`integer`, optional): Number of invoice items to return (1-100, default 10)
- `pending` (`boolean`, optional): Filter by pending status
- `starting_after` (`string`, optional): Invoice item ID to start pagination after

Example input: `{}`

### `stripe_list_invoice_line_items_dahlia`

List Invoice Line Items · Read-only

When retrieving an invoice, you'll get a lines property containing the total count of line items and the first handful of those items. There is also a URL where you can retrieve the full (paginated) list of line items.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to list line items for
- `ending_before` (`string`, optional): Line item ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of line items to return (1-100, default 10)
- `starting_after` (`string`, optional): Line item ID to start pagination after

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_list_invoices_dahlia`

List Invoices · Read-only

Returns a list of your invoices. The invoices are returned sorted by creation date, with the most recent invoices appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `collection_method` (`string`, optional): Filter invoices by collection method. One of: `charge_automatically`, `send_invoice`.
- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Filter invoices by customer ID
- `ending_before` (`string`, optional): Invoice ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of invoices to return (1-100, default 10)
- `starting_after` (`string`, optional): Invoice ID to start pagination after
- `status` (`string`, optional): Filter invoices by status. One of: `draft`, `open`, `paid`, `uncollectible`, `void`.
- `subscription` (`string`, optional): Filter invoices by subscription ID

Example input: `{}`

### `stripe_list_payment_intents_dahlia`

List Payment Intents · Read-only

Returns a list of PaymentIntents. The PaymentIntents are returned sorted by creation date, with the most recent PaymentIntents appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Filter PaymentIntents by customer ID
- `ending_before` (`string`, optional): PaymentIntent ID to end pagination before
- `limit` (`integer`, optional): Number of results to return (1-100, default 10)
- `starting_after` (`string`, optional): PaymentIntent ID to start pagination after

Example input: `{}`

### `stripe_list_payment_methods_dahlia`

List Payment Methods · Read-only

List PaymentMethods for a customer.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer` (`string`, optional): The ID of the customer whose payment methods to list.
- `ending_before` (`string`, optional): Cursor for pagination; returns results before this PaymentMethod ID.
- `limit` (`integer`, optional): Number of results to return (1–100).
- `starting_after` (`string`, optional): Cursor for pagination; returns results after this PaymentMethod ID.
- `type` (`string`, optional): Filter by payment method type. One of: `acss_debit`, `affirm`, `afterpay_clearpay`, `alipay`, `au_becs_debit`, `bacs_debit`, `bancontact`, `blik`, `boleto`, `card`, `cashapp`, `customer_balance`, `eps`, `fpx`, `giropay`, `grabpay`, `ideal`, `klarna`, `konbini`, `link`, `oxxo`, `p24`, `paynow`, `paypal`, `pix`, `promptpay`, `revolut_pay`, `sepa_debit`, `sofort`, `swish`, `us_bank_account`, `wechat_pay`, `zip`.

Example input: `{}`

### `stripe_list_payouts_dahlia`

List Payouts · Read-only

List all payouts, with optional filters by status and arrival date.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `arrival_date` (`integer`, optional): Filter by arrival date (Unix timestamp).
- `destination` (`string`, optional): Filter by destination bank account or card ID.
- `ending_before` (`string`, optional): Payout ID to end pagination before.
- `limit` (`integer`, optional): Number of payouts to return (1-100, default 10).
- `starting_after` (`string`, optional): Payout ID to start pagination after.
- `status` (`string`, optional): Filter by payout status. One of: `paid`, `pending`, `in_transit`, `canceled`, `failed`.

Example input: `{}`

### `stripe_list_plans_dahlia`

List Plans · Read-only

List all Plans.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Filter plans by active status. Pass true to list only active plans.
- `ending_before` (`string`, optional): Cursor for pagination: return results before this plan ID.
- `limit` (`integer`, optional): Maximum number of plans to return (1–100).
- `product` (`string`, optional): Filter plans by product ID.
- `starting_after` (`string`, optional): Cursor for pagination: return results after this plan ID.

Example input: `{}`

### `stripe_list_prices_dahlia`

List Prices · Read-only

Returns a list of your active prices, excluding inline prices. For the list of inactive prices, set active to false.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Only return prices that are active or inactive.
- `currency` (`string`, optional): Only return prices for the given currency.
- `ending_before` (`string`, optional): Price ID to end pagination before
- `limit` (`integer`, optional): Number of prices to return (1-100, default 10)
- `product` (`string`, optional): Only return prices for the given product.
- `starting_after` (`string`, optional): Price ID to start pagination after
- `type` (`string`, optional): Only return prices of this type. One of: `one_time`, `recurring`.

Example input: `{}`

### `stripe_list_products_dahlia`

List Products · Read-only

Returns a list of your products. The products are returned sorted by creation date, with the most recent products appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Filter products by active status
- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `ending_before` (`string`, optional): Product ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of products to return (1-100, default 10)
- `shippable` (`boolean`, optional): Filter products by shippable status
- `starting_after` (`string`, optional): Product ID to start pagination after
- `type` (`string`, optional): Filter products by type. One of: `good`, `service`.
- `url` (`string`, optional): Filter products by URL

Example input: `{}`

### `stripe_list_promotion_codes_dahlia`

List Promotion Codes · Read-only

List all promotion codes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Filter by active status. True returns only active codes, false returns only inactive.
- `code` (`string`, optional): Filter by the exact customer-facing code string.
- `coupon` (`string`, optional): Filter by the coupon ID the promotion codes belong to.
- `customer` (`string`, optional): Filter by the customer ID the promotion codes are restricted to.
- `ending_before` (`string`, optional): Cursor for reverse pagination. Returns results before this promotion code ID.
- `limit` (`integer`, optional): Maximum number of promotion codes to return (1–100).
- `starting_after` (`string`, optional): Cursor for forward pagination. Returns results after this promotion code ID.

Example input: `{}`

### `stripe_list_quotes_dahlia`

List Quotes · Read-only

List all Quotes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer` (`string`, optional): Filter quotes by customer ID.
- `ending_before` (`string`, optional): Cursor for pagination — return results before this quote ID.
- `limit` (`integer`, optional): Maximum number of quotes to return.
- `starting_after` (`string`, optional): Cursor for pagination — return results after this quote ID.
- `status` (`string`, optional): Filter quotes by status. One of: `draft`, `open`, `accepted`, `canceled`.

Example input: `{}`

### `stripe_list_refunds_dahlia`

List Refunds · Read-only

List all refunds, optionally filtered by charge or payment intent.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `charge` (`string`, optional): Filter refunds by the charge ID.
- `ending_before` (`string`, optional): A cursor for pagination. Returns objects before this refund ID.
- `limit` (`integer`, optional): A limit on the number of objects to be returned, between 1 and 100.
- `payment_intent` (`string`, optional): Filter refunds by the PaymentIntent ID.
- `starting_after` (`string`, optional): A cursor for pagination. Returns objects after this refund ID.

Example input: `{}`

### `stripe_list_setup_intents_dahlia`

List Setup Intents · Read-only

List all SetupIntents.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer` (`string`, optional): Filter by customer ID.
- `ending_before` (`string`, optional): A cursor for pagination. Returns objects before this ID.
- `limit` (`integer`, optional): Maximum number of objects to return (1–100).
- `payment_method` (`string`, optional): Filter by payment method ID.
- `starting_after` (`string`, optional): A cursor for pagination. Returns objects after this ID.

Example input: `{}`

### `stripe_list_subscription_items_dahlia`

List Subscription Items · Read-only

Returns a list of subscription items for a given subscription. Subscription items represent the component lines of a subscription.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription` (`string`, required): The ID of the subscription to list items for
- `ending_before` (`string`, optional): Subscription item ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of subscription items to return (1-100, default 10)
- `starting_after` (`string`, optional): Subscription item ID to start pagination after

Example input: `{"subscription":"<subscription>"}`

### `stripe_list_subscription_schedules`

List Subscription Schedules · Read-only

Retrieves the list of your subscription schedules, sorted by creation date with the most recent first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Only return subscription schedules for the given customer.
- `ending_before` (`string`, optional): Subscription schedule ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of subscription schedules to return (1-100, default 10).
- `scheduled` (`boolean`, optional): Only return subscription schedules that have not started yet.
- `starting_after` (`string`, optional): Subscription schedule ID to start pagination after.

Example input: `{}`

### `stripe_list_subscriptions_dahlia`

List Subscriptions · Read-only

Returns a list of your subscriptions. The subscriptions are returned sorted by creation date, with the most recent subscriptions appearing first.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `created` (`integer`, optional): Filter by exact creation timestamp (Unix seconds). For a range filter, use created_gt/created_gte/created_lt/created_lte instead.
- `created_gt` (`integer`, optional): Filter by creation date, strictly after this Unix timestamp.
- `created_gte` (`integer`, optional): Filter by creation date, at or after this Unix timestamp.
- `created_lt` (`integer`, optional): Filter by creation date, strictly before this Unix timestamp.
- `created_lte` (`integer`, optional): Filter by creation date, at or before this Unix timestamp.
- `customer` (`string`, optional): Filter subscriptions by customer ID
- `ending_before` (`string`, optional): Subscription ID to end pagination before
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of subscriptions to return (1-100, default 10)
- `price` (`string`, optional): Filter subscriptions by price ID
- `starting_after` (`string`, optional): Subscription ID to start pagination after
- `status` (`string`, optional): Filter subscriptions by status. One of: `active`, `canceled`, `incomplete`, `incomplete_expired`, `past_due`, `trialing`, `unpaid`.

Example input: `{}`

### `stripe_list_tax_rates_dahlia`

List Tax Rates · Read-only

List all tax rates.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `active` (`boolean`, optional): Filter to only return active or inactive tax rates.
- `ending_before` (`string`, optional): A cursor for pagination. Returns objects before this ID.
- `inclusive` (`boolean`, optional): Filter to return only inclusive or exclusive tax rates.
- `limit` (`integer`, optional): Maximum number of objects to return (1–100).
- `starting_after` (`string`, optional): A cursor for pagination. Returns objects after this ID.

Example input: `{}`

### `stripe_list_transfer_reversals_dahlia`

List Transfer Reversals · Read-only

Lists the reversals belonging to a specific transfer. The 10 most recent reversals are always available directly on the transfer object; use this to page through additional ones.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `transfer_id` (`string`, required): The ID of the transfer whose reversals you want to list.
- `ending_before` (`string`, optional): Reversal ID to end pagination before.
- `expand` (`array`, optional): List of fields to expand in the response.
- `limit` (`integer`, optional): Number of reversals to return (1-100, default 10).
- `starting_after` (`string`, optional): Reversal ID to start pagination after.

Example input: `{"transfer_id":"<transfer_id>"}`

### `stripe_list_transfers_dahlia`

List Transfers · Read-only

List all transfers to connected accounts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `destination` (`string`, optional): Filter transfers by the connected account ID they were sent to.
- `ending_before` (`string`, optional): Cursor for pagination: return results before this transfer ID.
- `limit` (`integer`, optional): Maximum number of transfers to return (1–100).
- `starting_after` (`string`, optional): Cursor for pagination: return results after this transfer ID.

Example input: `{}`

### `stripe_list_webhook_endpoints_dahlia`

List Webhook Endpoints · Read-only

List all webhook endpoints.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `ending_before` (`string`, optional): Cursor for pagination: return endpoints before this webhook endpoint ID.
- `limit` (`integer`, optional): Maximum number of webhook endpoints to return (1-100).
- `starting_after` (`string`, optional): Cursor for pagination: return endpoints after this webhook endpoint ID.

Example input: `{}`

### `stripe_search_charges_dahlia`

Search Charges · Read-only

Search for charges using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_customers_dahlia`

Search Customers · Read-only

Search for customers using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_invoices_dahlia`

Search Invoices · Read-only

Search for invoices using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_payment_intents_dahlia`

Search Payment Intents · Read-only

Search for payment intents using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_prices_dahlia`

Search Prices · Read-only

Search for prices using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_products_dahlia`

Search Products · Read-only

Search for products using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_search_subscriptions_dahlia`

Search Subscriptions · Read-only

Search for subscriptions using Stripe's Search Query Language. Data is typically searchable within a minute of being written; do not use this in read-after-write flows requiring strict consistency.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `query` (`string`, required): The search query string using Stripe's Search Query Language.
- `limit` (`integer`, optional): Number of results to return (1-100, default 10).
- `page` (`string`, optional): Cursor for pagination across multiple pages of search results.

Example input: `{"query":"<query>"}`

### `stripe_accept_quote_dahlia`

Accept Quote · Write

Accept a finalized Quote. Converts it into a subscription or invoice.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `quote` (`string`, required): The ID of the quote to accept.

Example input: `{"quote":"<quote>"}`

### `stripe_attach_invoice_payment_dahlia`

Attach Payment To Invoice · Write

Attaches a PaymentIntent to an invoice, crediting the invoice's amount_paid when the PaymentIntent succeeds. Use this to record an out-of-band or externally-processed payment against an invoice.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to attach the payment to.
- `expand` (`array`, optional): List of fields to expand in the response.
- `payment_intent` (`string`, optional): The ID of the PaymentIntent to attach to the invoice.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_attach_payment_method_dahlia`

Attach Payment Method · Write

Attach a PaymentMethod to a Customer.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, required): The ID of the customer to attach the PaymentMethod to.
- `id` (`string`, required): The ID of the PaymentMethod to attach.

Example input: `{"customer":"<customer>","id":"<id>"}`

### `stripe_cancel_payout_dahlia`

Cancel Payout · Write

Cancel a payout that has not yet been paid out. Only cancels payouts with status 'pending'.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `payout` (`string`, required): The ID of the payout to cancel.

Example input: `{"payout":"<payout>"}`

### `stripe_cancel_quote_dahlia`

Cancel Quote · Write

Cancel a Quote that has been finalized but not yet accepted.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `quote` (`string`, required): The ID of the quote to cancel.

Example input: `{"quote":"<quote>"}`

### `stripe_cancel_refund_dahlia`

Cancel Refund · Write

Cancels a refund that has a status of requires_action. Only refunds for payment methods that require customer action can enter that state; refunds in other states cannot be canceled.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `refund_id` (`string`, required): The ID of the refund to cancel.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"refund_id":"<refund_id>"}`

### `stripe_capture_charge_dahlia`

Capture Charge · Write

Captures the payment of an existing, uncaptured charge that was created with capture set to false. Uncaptured charges expire (7 days by default) after which capture attempts fail.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `charge_id` (`string`, required): The ID of the uncaptured charge to capture.
- `amount` (`integer`, optional): The amount to capture, which must be less than or equal to the original charge amount.
- `expand` (`array`, optional): List of fields to expand in the response.
- `receipt_email` (`string`, optional): The email address to send the receipt to, overriding any previously-specified email.
- `statement_descriptor` (`string`, optional): Text that appears on the customer's statement as the statement descriptor for a non-card charge.

Example input: `{"charge_id":"<charge_id>"}`

### `stripe_confirm_payment_intent_dahlia`

Confirm Payment Intent · Write

Confirm that your customer intends to pay with current or provided payment method. Upon confirmation, the PaymentIntent will attempt to initiate a payment. If the payment method requires action (3DS, redirect), the PaymentIntent will move to requires_action.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `payment_intent_id` (`string`, required): The ID of the PaymentIntent to confirm.
- `payment_method` (`string`, optional): ID of the payment method to confirm with.
- `return_url` (`string`, optional): The URL to redirect the customer to after payment completion.

Example input: `{"payment_intent_id":"<payment_intent_id>"}`

### `stripe_confirm_setup_intent_dahlia`

Confirm Setup Intent · Write

Confirm a SetupIntent and attempt to collect a payment method for future use.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `setup_intent_id` (`string`, required): The ID of the SetupIntent to confirm.
- `payment_method` (`string`, optional): ID of the payment method to attach to this SetupIntent.
- `return_url` (`string`, optional): The URL to redirect to after the SetupIntent is confirmed.

Example input: `{"setup_intent_id":"<setup_intent_id>"}`

### `stripe_create_account_dahlia`

Create Account · Write

Creates a new connected account for use with Stripe Connect. Platforms use this to onboard sellers, service providers, or other businesses to accept payments and receive payouts.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `business_profile` (`object`, optional): Business information shown to customers, such as the business's URL and MCC.
- `business_type` (`string`, optional): The business type: individual, company, government_entity, or non_profit. One of: `individual`, `company`, `government_entity`, `non_profit`.
- `capabilities` (`object`, optional): Capabilities to request for the account, e.g. card_payments and transfers.
- `company` (`object`, optional): Information about the company, used when business_type is 'company'.
- `controller` (`object`, optional): Configuration describing who is responsible for pricing, fee collection, and dashboard access on this account.
- `country` (`string`, optional): Two-letter country code for the account holder's country.
- `default_currency` (`string`, optional): Three-letter ISO currency code representing the default currency for the account.
- `email` (`string`, optional): The email address of the account holder.
- `expand` (`array`, optional): List of fields to expand in the response.
- `individual` (`object`, optional): Information about the individual represented by the account, used when business_type is 'individual'.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the account.
- `tos_acceptance` (`object`, optional): Details on the account's acceptance of the Stripe Services Agreement.

Example input: `{}`

### `stripe_create_account_external_account_dahlia`

Create Account External Account · Write

Adds an external account (a bank account or debit card) to a connected account for receiving payouts.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `external_account` (`string`, required): A token (from Stripe.js) representing the bank account or card to attach, or a dictionary of external account details.
- `default_for_currency` (`boolean`, optional): Whether this external account should become the default for its currency.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the external account.

Example input: `{"account":"<account>","external_account":"<external_account>"}`

### `stripe_create_account_login_link_dahlia`

Create Account Login Link · Write

Creates a single-use login link for a connected account that uses the Express Dashboard, letting the account holder access their dashboard without a separate Stripe login.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `account` (`string`, required): The ID of the Express-dashboard connected account.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"account":"<account>"}`

### `stripe_create_account_person_dahlia`

Create Account Person · Write

Creates a new person associated with a connected account's legal entity, such as an owner, director, executive, or representative.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `address` (`object`, optional): The person's address.
- `dob` (`object`, optional): The person's date of birth.
- `email` (`string`, optional): The person's email address.
- `expand` (`array`, optional): List of fields to expand in the response.
- `first_name` (`string`, optional): The person's first name.
- `last_name` (`string`, optional): The person's last name.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the person.
- `phone` (`string`, optional): The person's phone number.
- `relationship` (`object`, optional): The relationship that this person has with the account's legal entity (e.g. owner, director, representative).
- `ssn_last_4` (`string`, optional): The last four digits of the person's Social Security number (U.S. only).

Example input: `{"account":"<account>"}`

### `stripe_create_application_fee_refund`

Create Application Fee Refund · Write

Refunds an application fee previously collected via Stripe Connect but not yet fully refunded. Funds are refunded to the Stripe account from which the fee was originally collected. Can be called multiple times to partially refund a fee until it is entirely refunded.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_fee_id` (`string`, required): The ID of the application fee to refund.
- `amount` (`integer`, optional): A positive integer, in the smallest currency unit, representing how much of this fee to refund. Can refund only up to the remaining unrefunded amount of the fee. Omit to refund the full remaining amount.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the fee refund.

Example input: `{"application_fee_id":"<application_fee_id>"}`

### `stripe_create_billing_meter`

Create Billing Meter · Write

Creates a billing meter that defines how to aggregate usage events for usage-based billing prices.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `default_aggregation` (`object`, required): The default settings used to aggregate this meter's events.
- `display_name` (`string`, required): The meter's name. Not visible to the customer. Max 250 characters.
- `event_name` (`string`, required): The name of the meter event to record usage for. Corresponds with the event_name field on meter events. Max 100 characters.
- `customer_mapping` (`object`, optional): Fields that specify how to map a meter event to a customer.
- `event_time_window` (`string`, optional): The time window which meter events have been pre-aggregated for, if any. One of: `day`, `hour`.
- `value_settings` (`object`, optional): Fields that specify how to calculate a meter event's value.

Example input: `{"default_aggregation":{},"display_name":"<display_name>","event_name":"<event_name>"}`

### `stripe_create_billing_meter_event`

Create Billing Meter Event · Write

Submits a usage event (e.g. API calls, minutes used) against a billing meter to drive usage-based billing.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `event_name` (`string`, required): The name of the meter event. Must match the event_name configured on a billing meter. Max 100 characters.
- `payload` (`object`, required): The payload of the event. Must contain the fields corresponding to the meter's customer_mapping.event_payload_key (default 'stripe_customer_id') and value_settings.event_payload_key (default 'value').
- `identifier` (`string`, optional): A unique identifier for the event. If not provided, one is generated. Stripe enforces uniqueness within a rolling period of at least 24 hours. Max 100 characters.
- `timestamp` (`integer`, optional): The time of the event, in Unix seconds. Must be within the past 35 calendar days or up to 5 minutes in the future. Defaults to the current time if not specified.

Example input: `{"event_name":"<event_name>","payload":{}}`

### `stripe_create_billing_portal_configuration_dahlia`

Create Billing Portal Configuration · Write

Creates a configuration that describes the functionality and behavior of the customer self-service billing portal, such as which features (subscription updates, cancellation, invoice history) are enabled.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `features` (`object`, required): Information about the features available in the portal, such as invoice_history, subscription_cancel, and payment_method_update.
- `business_profile` (`object`, optional): The business information shown to customers in the portal.
- `default_return_url` (`string`, optional): The default URL to redirect customers to when they click the portal's return-to-site link.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the configuration.

Example input: `{"features":{}}`

### `stripe_create_charge_dahlia`

Create Charge · Write

Creates a direct charge against a card or other payment source. Stripe recommends using the Payment Intents API for new integrations; this legacy endpoint remains useful for simple, immediate card charges.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): Amount to be collected, in the smallest currency unit (e.g. cents for USD).
- `currency` (`string`, required): Three-letter ISO currency code for the charge.
- `capture` (`boolean`, optional): Whether to immediately capture the charge. Defaults to true; pass false to create an authorization only.
- `customer` (`string`, optional): The ID of an existing customer to charge.
- `description` (`string`, optional): An arbitrary string attached to the charge, shown in the dashboard.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the charge.
- `receipt_email` (`string`, optional): The email address to which the receipt for this charge will be sent.

Example input: `{"amount":100,"currency":"<currency>"}`

### `stripe_create_checkout_session_dahlia`

Create Checkout Session · Write

Create a Checkout Session to accept one-time or subscription payments via Stripe-hosted page.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `mode` (`string`, required): The mode of the Checkout Session. One of: `payment`, `setup`, `subscription`.
- `success_url` (`string`, required): The URL the customer will be redirected to after a successful payment.
- `cancel_url` (`string`, optional): The URL the customer will be redirected to if they cancel the payment.
- `currency` (`string`, optional): Three-letter ISO currency code (e.g., usd, eur, gbp).
- `customer` (`string`, optional): ID of an existing Customer to associate with this session.
- `customer_email` (`string`, optional): If provided, this value will be used when the customer has not provided an email address.
- `line_items` (`array`, optional): Array of line items for this Checkout Session. Each item is a JSON object with fields: price (Stripe Price ID) and quantity. Required for payment/subscription mode.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the Checkout Session.

Example input: `{"mode":"payment","success_url":"<success_url>"}`

### `stripe_create_coupon_dahlia`

Create Coupon · Write

Create a coupon that can be redeemed for a discount on subscriptions or one-time charges.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `duration` (`string`, required): How long the discount will be in effect. 'once' applies to the first charge, 'repeating' applies for duration_in_months, 'forever' applies indefinitely. One of: `forever`, `once`, `repeating`.
- `amount_off` (`integer`, optional): Fixed amount discount in the smallest currency unit (e.g. cents). Requires currency. Use this OR percent_off.
- `currency` (`string`, optional): Three-letter ISO currency code. Required when amount_off is set.
- `duration_in_months` (`integer`, optional): Number of months the discount applies when duration is repeating.
- `id` (`string`, optional): Unique identifier for the coupon. If not provided, Stripe generates a random ID.
- `max_redemptions` (`integer`, optional): Maximum number of times this coupon can be redeemed in total.
- `metadata` (`object`, optional): Set of key-value pairs for storing additional information.
- `name` (`string`, optional): Name of the coupon displayed to customers.
- `percent_off` (`number`, optional): Percentage discount to apply. Use this OR amount_off, not both.
- `redeem_by` (`integer`, optional): Unix timestamp after which the coupon can no longer be redeemed.

Example input: `{"duration":"forever"}`

### `stripe_create_credit_note`

Create Credit Note · Write

Issues a credit note to adjust the amount of a finalized invoice (e.g. to refund or credit a customer against that invoice). One of amount, lines, or shipping_cost must be provided.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoice` (`string`, required): The ID of the invoice to credit.
- `amount` (`integer`, optional): The integer amount in the smallest currency unit representing the total amount of the credit note. One of amount, lines, or shipping_cost must be provided.
- `credit_amount` (`integer`, optional): The integer amount in the smallest currency unit to credit to the customer's balance, automatically applied to their next invoice.
- `email_type` (`string`, optional): Type of email to send to the customer. One of: `credit_note`, `none`.
- `lines` (`array`, optional): Line items that make up the credit note. One of amount, lines, or shipping_cost must be provided.
- `memo` (`string`, optional): The credit note's memo, which appears on the credit note PDF.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the credit note.
- `out_of_band_amount` (`integer`, optional): The integer amount in the smallest currency unit that is or will be credited outside of Stripe.
- `reason` (`string`, optional): Reason for issuing this credit note. One of: `duplicate`, `fraudulent`, `order_change`, `product_unsatisfactory`.
- `refund_amount` (`integer`, optional): The integer amount in the smallest currency unit to refund. If set, a refund is created for the charge associated with the invoice.

Example input: `{"invoice":"<invoice>"}`

### `stripe_create_customer_balance_transaction_dahlia`

Create Customer Balance Transaction · Write

Creates an immutable transaction that adjusts a customer's credit balance, which is automatically applied to the customer's next invoices.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): The signed integer amount, in the smallest currency unit, to apply to the customer's credit balance. A negative amount is a credit; a positive amount is a debit.
- `currency` (`string`, required): Three-letter ISO currency code for the balance transaction.
- `customer_id` (`string`, required): The ID of the customer whose balance to adjust.
- `description` (`string`, optional): An arbitrary string attached to the object, useful for displaying to users.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the balance transaction.

Example input: `{"amount":100,"currency":"<currency>","customer_id":"<customer_id>"}`

### `stripe_create_customer_dahlia`

Create Customer · Write

Creates a new customer object. Use this to store a customer's payment and billing details. The customer object allows you to perform recurring charges and track multiple charges associated with the same customer.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `address` (`object`, optional): The customer's address as a JSON object with fields: line1, line2, city, state, postal_code, country.
- `description` (`string`, optional): An arbitrary string that you can attach to a customer object. It is displayed alongside the customer in the dashboard.
- `email` (`string`, optional): Customer's email address. It is displayed alongside the customer in the dashboard and can be useful for searching and tracking.
- `metadata` (`object`, optional): Set of key-value pairs that you can attach to an object. Useful for storing additional information about the customer.
- `name` (`string`, optional): The customer's full name or business name.
- `payment_method` (`string`, optional): The ID of the PaymentMethod to attach to the customer.
- `phone` (`string`, optional): The customer's phone number.
- `shipping` (`object`, optional): The customer's shipping information as a JSON object with name, address, and optional phone fields.
- `tax_exempt` (`string`, optional): The customer's tax exemption status. One of: none, exempt, or reverse. One of: `none`, `exempt`, `reverse`.

Example input: `{}`

### `stripe_create_customer_portal_session_dahlia`

Create Customer Portal Session · Write

Creates a session of the customer portal. A portal session describes the instantiation of the customer portal for a particular customer. By visiting the session's URL, the customer can manage their subscriptions and billing details. Portal sessions are short-lived and will expire if the customer does not visit the URL.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, required): The ID of an existing customer
- `configuration` (`string`, optional): The ID of an existing configuration to use for this session
- `locale` (`string`, optional): The IETF language tag of the locale customer portal is displayed in
- `on_behalf_of` (`string`, optional): The `on_behalf_of` account to use for this session
- `return_url` (`string`, optional): The default URL to redirect customers to when they click on the portal's link to return to your website

Example input: `{"customer":"<customer>"}`

### `stripe_create_customer_tax_id_dahlia`

Create Customer Tax ID · Write

Creates a new tax ID (such as a VAT or GST number) for a customer, for use on invoices and tax reporting.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer_id` (`string`, required): The ID of the customer to add the tax ID to.
- `type` (`string`, required): The type of tax ID, e.g. eu_vat, us_ein, gb_vat. One of: `ad_nrt`, `ae_trn`, `al_tin`, `am_tin`, `ao_tin`, `ar_cuit`, `au_abn`, `au_arn`, `aw_tin`, `az_tin`, `ba_tin`, `bb_tin`, `bd_bin`, `bf_ifu`, `bg_uic`, `bh_vat`, `bj_ifu`, `bo_tin`, `br_cnpj`, `br_cpf`, `bs_tin`, `by_tin`, `ca_bn`, `ca_gst_hst`, `ca_pst_bc`, `ca_pst_mb`, `ca_pst_sk`, `ca_qst`, `cd_nif`, `ch_uid`, `ch_vat`, `cl_tin`, `cm_niu`, `cn_tin`, `co_nit`, `cr_tin`, `cv_nif`, `de_stn`, `do_rcn`, `ec_ruc`, `eg_tin`, `es_cif`, `et_tin`, `eu_oss_vat`, `eu_vat`, `fo_vat`, `gb_vat`, `ge_vat`, `gi_tin`, `gn_nif`, `hk_br`, `hr_oib`, `hu_tin`, `ic_nif`, `id_npwp`, `il_vat`, `in_gst`, `is_vat`, `it_cf`, `jp_cn`, `jp_rn`, `jp_trn`, `ke_pin`, `kg_tin`, `kh_tin`, `kr_brn`, `kz_bin`, `la_tin`, `li_uid`, `li_vat`, `lk_vat`, `ma_vat`, `md_vat`, `me_pib`, `mk_vat`, `mr_nif`, `mx_rfc`, `my_frp`, `my_itn`, `my_sst`, `ng_tin`, `no_vat`, `no_voec`, `np_pan`, `nz_gst`, `om_vat`, `pe_ruc`, `ph_tin`, `pl_nip`, `py_ruc`, `ro_tin`, `rs_pib`, `ru_inn`, `ru_kpp`, `sa_vat`, `sg_gst`, `sg_uen`, `si_tin`, `sn_ninea`, `sr_fin`, `sv_nit`, `th_vat`, `tj_tin`, `tr_tin`, `tw_vat`, `tz_vat`, `ua_vat`, `ug_tin`, `us_ein`, `uy_ruc`, `uz_tin`, `uz_vat`, `ve_rif`, `vn_tin`, `za_vat`, `zm_tin`, `zw_tin`.
- `value` (`string`, required): The value of the tax ID.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"customer_id":"<customer_id>","type":"ad_nrt","value":"<value>"}`

### `stripe_create_invoice_dahlia`

Create Invoice · Write

This endpoint creates a draft invoice for a given customer. The draft invoice created pulls in all pending invoice items on that customer, including prorations. The invoice remains a draft until you finalize the invoice, which allows you to pay, send, and delete the invoice.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, required): The ID of the customer to bill.
- `auto_advance` (`boolean`, optional): Controls whether Stripe performs automatic collection of the invoice.
- `collection_method` (`string`, optional): Either charge_automatically or send_invoice. One of: `charge_automatically`, `send_invoice`.
- `currency` (`string`, optional): Three-letter ISO currency code.
- `days_until_due` (`integer`, optional): The number of days from when the invoice is created until it is due (send_invoice only).
- `default_payment_method` (`string`, optional): ID of the default payment method for this invoice.
- `description` (`string`, optional): An arbitrary string attached to the invoice.
- `footer` (`string`, optional): Footer text displayed on the invoice.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the invoice.
- `pending_invoice_items_behavior` (`string`, optional): Controls whether the customer's pending invoice items are attached to this invoice. One of: `include`, `exclude`.
- `subscription` (`string`, optional): The ID of the subscription to invoice.

Example input: `{"customer":"<customer>"}`

### `stripe_create_invoice_item_dahlia`

Create Invoice Item · Write

Create an invoice item to be added to a pending invoice.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `currency` (`string`, required): Three-letter ISO currency code for the invoice item.
- `customer` (`string`, required): The ID of the customer to create the invoice item for.
- `amount` (`integer`, optional): The amount in the smallest currency unit (e.g. cents for USD).
- `description` (`string`, optional): An arbitrary string describing the invoice item.
- `invoice` (`string`, optional): The ID of an existing invoice to attach this item to.
- `price` (`string`, optional): The ID of a Price to use for this invoice item.
- `quantity` (`integer`, optional): Non-negative integer quantity of units for this invoice item.

Example input: `{"currency":"<currency>","customer":"<customer>"}`

### `stripe_create_payment_intent_dahlia`

Create Payment Intent · Write

Creates a PaymentIntent object. After the PaymentIntent is created, attach a payment method and confirm to continue the payment. You can also create and confirm a PaymentIntent in a single step by using the confirm parameter.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): Amount intended to be collected in the smallest currency unit (e.g., 100 cents for $1.00 USD).
- `currency` (`string`, required): Three-letter ISO currency code (lowercase, e.g., usd, eur, gbp).
- `capture_method` (`string`, optional): Controls when the funds will be captured from the customer's account. One of: `automatic`, `automatic_async`, `manual`.
- `confirm` (`boolean`, optional): Set to true to attempt to confirm this PaymentIntent immediately after creation.
- `customer` (`string`, optional): ID of the Customer this PaymentIntent belongs to, if one exists.
- `description` (`string`, optional): An arbitrary string attached to the object. Often useful for displaying to users.
- `metadata` (`object`, optional): Set of key-value pairs that you can attach to an object.
- `payment_method` (`string`, optional): ID of the payment method to attach to this PaymentIntent.
- `payment_method_types` (`array`, optional): The payment method types to allow for this PaymentIntent (e.g. ["card"], ["card", "sepa_debit"]). Stripe's API requires this as an array, even for a single type.
- `receipt_email` (`string`, optional): Email address to send the receipt to after successful payment.
- `return_url` (`string`, optional): The URL to redirect to after payment is confirmed (used when confirm=true).
- `statement_descriptor` (`string`, optional): Text shown on the customer's bank or card statement (max 22 characters).

Example input: `{"amount":100,"currency":"<currency>"}`

### `stripe_create_payment_method_dahlia`

Create Payment Method · Write

Create a PaymentMethod object. Attach it to a Customer to enable reusable payment.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `type` (`string`, required): The type of payment method to create. Excludes 'link': Stripe rejects direct creation of a link PaymentMethod ("You cannot create a type `link` PaymentMethod directly") regardless of input — it can only be obtained via other flows (e.g. an automatic_payment_methods-enabled PaymentIntent/SetupIntent). One of: `acss_debit`, `affirm`, `afterpay_clearpay`, `alipay`, `au_becs_debit`, `bacs_debit`, `bancontact`, `blik`, `boleto`, `card`, `cashapp`, `customer_balance`, `eps`, `fpx`, `giropay`, `grabpay`, `ideal`, `klarna`, `konbini`, `oxxo`, `p24`, `paynow`, `paypal`, `pix`, `promptpay`, `revolut_pay`, `sepa_debit`, `sofort`, `swish`, `us_bank_account`, `wechat_pay`, `zip`.
- `billing_details` (`object`, optional): Billing information associated with the PaymentMethod, as a JSON object with fields: name, email, phone.
- `card` (`object`, optional): Card details (for type=card), as a JSON object with fields: number, exp_month, exp_year, cvc. Use Stripe test numbers like 4242424242424242.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the PaymentMethod.

Example input: `{"type":"acss_debit"}`

### `stripe_create_payout_dahlia`

Create Payout · Write

Create a payout to send funds to a bank account or debit card.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): Amount in the smallest currency unit (e.g., cents for USD). Must be a positive integer.
- `currency` (`string`, required): Three-letter ISO 4217 currency code for the payout.
- `description` (`string`, optional): An arbitrary string to describe the payout.
- `destination` (`string`, optional): The ID of a bank account or debit card to send the payout to.
- `method` (`string`, optional): The method used to send the payout. 'standard' (bank transfer) or 'instant' (instant payout to debit card). One of: `standard`, `instant`.
- `statement_descriptor` (`string`, optional): A string that appears on the recipient's bank statement (max 22 characters).

Example input: `{"amount":100,"currency":"<currency>"}`

### `stripe_create_plan_dahlia`

Create Plan · Write

Create a Plan (legacy billing API). Consider using Prices instead for new integrations.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): Amount to charge per billing interval, in the smallest currency unit (e.g. cents for USD).
- `currency` (`string`, required): Three-letter ISO currency code (lowercase) for the plan.
- `interval` (`string`, required): Billing frequency for the plan. One of: `day`, `week`, `month`, `year`.
- `product` (`string`, required): The product ID (or inline product object) this plan belongs to.
- `id` (`string`, optional): An optional custom identifier for the plan. Must be unique.
- `interval_count` (`integer`, optional): Number of intervals between billings. For example, interval=month and interval_count=3 means every 3 months.
- `nickname` (`string`, optional): A friendly name for the plan shown in the Stripe dashboard.
- `trial_period_days` (`integer`, optional): Number of trial period days granted when subscribing to this plan.

Example input: `{"amount":100,"currency":"<currency>","interval":"day","product":"<product>"}`

### `stripe_create_price_dahlia`

Create Price · Write

Creates a new price for an existing product. Prices define how much and how often to charge for products. This includes one-time prices and recurring prices for subscriptions.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `currency` (`string`, required): Three-letter ISO currency code.
- `active` (`boolean`, optional): Whether the price can be used for new purchases. Defaults to true.
- `billing_scheme` (`string`, optional): Describes how to compute the price per period. Either per_unit or tiered. One of: `per_unit`, `tiered`.
- `lookup_key` (`string`, optional): A lookup key used to retrieve prices dynamically from a static string.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the price.
- `nickname` (`string`, optional): A brief description of the price, hidden from customers.
- `product` (`string`, optional): The ID of the product that this price will belong to.
- `recurring` (`object`, optional): Recurring billing details as a JSON object with fields: interval (day, week, month, year) and optional interval_count. Omit for a one-time price.
- `tax_behavior` (`string`, optional): Specifies whether the price is considered inclusive of taxes or exclusive of taxes. One of: `exclusive`, `inclusive`, `unspecified`.
- `unit_amount` (`integer`, optional): A positive integer in cents (or 0 for a free price) representing how much to charge.

Example input: `{"currency":"<currency>"}`

### `stripe_create_product_dahlia`

Create Product · Write

Creates a new product object. Products describe the specific goods or services you offer to your customers. Products are used in conjunction with Prices to configure how much and how often you charge customers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): The product's name, meant to be displayable to the customer.
- `active` (`boolean`, optional): Whether the product is currently available for purchase. Defaults to true.
- `description` (`string`, optional): The product's description, meant to be displayable to the customer. Use this field to optionally store a long form explanation of the product.
- `images` (`array`, optional): A list of up to 8 URLs of images for this product.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the product.
- `shippable` (`boolean`, optional): Whether this product is shipped (i.e., physical goods).
- `statement_descriptor` (`string`, optional): An arbitrary string to be displayed on your customer's credit card or bank statement.
- `tax_code` (`string`, optional): A tax code ID. Stripe Tax uses this to classify the product for tax calculations.
- `unit_label` (`string`, optional): A label that represents units of this product. When set, this will be included in customers' receipts, invoices, Checkout, and the customer portal.
- `url` (`string`, optional): A URL of a publicly-accessible webpage for this product.

Example input: `{"name":"<name>"}`

### `stripe_create_promotion_code_dahlia`

Create Promotion Code · Write

Create a promotion code for a coupon that customers can redeem.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `coupon` (`string`, required): The ID of the coupon to apply to this promotion code.
- `active` (`boolean`, optional): Whether the promotion code is currently active. Defaults to true.
- `code` (`string`, optional): Human-readable code that customers enter at checkout. If not set, Stripe generates a random code.
- `customer` (`string`, optional): Restrict this promotion code to a specific customer ID.
- `expires_at` (`integer`, optional): Unix timestamp after which the promotion code can no longer be redeemed.
- `max_redemptions` (`integer`, optional): Maximum number of times this promotion code can be redeemed.
- `metadata` (`object`, optional): Set of key-value pairs for storing additional information.

Example input: `{"coupon":"<coupon>"}`

### `stripe_create_quote_dahlia`

Create Quote · Write

Create a Quote for a subscription or one-time payment, which can be sent to customers for approval.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, optional): The ID of the customer the quote belongs to.
- `description` (`string`, optional): A description visible to customers on the quote.
- `expires_at` (`integer`, optional): Unix timestamp at which the quote will expire.
- `footer` (`string`, optional): Footer text shown at the bottom of the quote document.
- `header` (`string`, optional): Header text shown at the top of the quote document.
- `line_items` (`array`, optional): A list of line items to include on the quote.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the quote.
- `subscription_data` (`object`, optional): Subscription data to apply when converting the quote to a subscription.

Example input: `{}`

### `stripe_create_refund_dahlia`

Create Refund · Write

Create a refund for a charge or payment intent. Refunds a charge that has previously been created, with optional partial amount.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, optional): A positive integer in the smallest currency unit representing how much to refund. Defaults to full refund if omitted.
- `charge` (`string`, optional): The identifier of the charge to refund. Either charge or payment_intent must be provided.
- `payment_intent` (`string`, optional): The identifier of the PaymentIntent to refund. Alternative to charge.
- `reason` (`string`, optional): The reason for the refund. One of: `duplicate`, `fraudulent`, `requested_by_customer`.

Example input: `{}`

### `stripe_create_setup_intent_dahlia`

Create Setup Intent · Write

Create a SetupIntent to collect payment method details for future off-session payments.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `confirm` (`boolean`, optional): Set to true to attempt to confirm this SetupIntent immediately.
- `customer` (`string`, optional): ID of the Stripe customer this SetupIntent is associated with.
- `description` (`string`, optional): An arbitrary string description for the SetupIntent.
- `payment_method` (`string`, optional): ID of the payment method to attach to this SetupIntent.
- `payment_method_types` (`array`, optional): The payment method types this SetupIntent is allowed to use (e.g. ["card"], ["card", "sepa_debit"]). Stripe's API requires this as an array, even for a single type.
- `usage` (`string`, optional): Indicates how the payment method is intended to be used in the future. One of: `off_session`, `on_session`.

Example input: `{}`

### `stripe_create_subscription_dahlia`

Create Subscription · Write

Creates a new subscription on an existing customer. Each customer can have multiple active subscriptions if needed.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, required): The identifier of the customer to subscribe.
- `items` (`array`, required): List of subscription items, each with a price ID and optional quantity.
- `cancel_at_period_end` (`boolean`, optional): Boolean indicating whether this subscription should cancel at the end of the current period.
- `collection_method` (`string`, optional): Either charge_automatically or send_invoice. One of: `charge_automatically`, `send_invoice`.
- `currency` (`string`, optional): Three-letter ISO currency code for the subscription.
- `days_until_due` (`integer`, optional): Number of days a customer has to pay invoices (used with send_invoice collection method).
- `default_payment_method` (`string`, optional): ID of the default payment method for this subscription.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the subscription.
- `payment_behavior` (`string`, optional): Controls how Stripe handles the first invoice when payment is required and collection_method=charge_automatically. Use default_incomplete to let the subscription go to status=incomplete (generating a PaymentIntent the client confirms) instead of hard-failing when the customer has no default payment method. One of: `allow_incomplete`, `default_incomplete`, `error_if_incomplete`, `pending_if_incomplete`.
- `trial_end` (`string`, optional): Unix timestamp for when the trial period ends. Use 'now' to end an existing trial.
- `trial_period_days` (`integer`, optional): Integer representing the number of trial period days before the customer is charged.

Example input: `{"customer":"<customer>","items":[]}`

### `stripe_create_subscription_item_dahlia`

Create Subscription Item · Write

Add a new item to an existing subscription.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `price` (`string`, required): The ID of the price to use for this subscription item.
- `subscription` (`string`, required): The ID of the subscription to add this item to.
- `proration_behavior` (`string`, optional): Determines how to handle prorations when adding this item. One of: `create_prorations`, `none`, `always_invoice`.
- `quantity` (`integer`, optional): The quantity of the plan to which the customer should be subscribed.

Example input: `{"price":"<price>","subscription":"<subscription>"}`

### `stripe_create_subscription_schedule`

Create Subscription Schedule · Write

Creates a subscription schedule that predefines future phases/changes to a subscription (upgrades, downgrades, trial-to-paid transitions) on a fixed timeline. Provide either 'customer' with 'phases', or 'from_subscription' to migrate an existing subscription onto a schedule.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer` (`string`, optional): The identifier of the customer to create the subscription schedule for. Required unless from_subscription is set.
- `default_settings` (`object`, optional): Default settings for the subscription schedule, applied to phases that don't override them (e.g. default_payment_method, collection_method, application_fee_percent).
- `end_behavior` (`string`, optional): Behavior when the schedule ends: 'release' (default, keeps the underlying subscription running as-is) or 'cancel' (cancels the underlying subscription). One of: `cancel`, `release`.
- `expand` (`array`, optional): List of fields to expand in the response.
- `from_subscription` (`string`, optional): Migrate an existing subscription to be managed by a subscription schedule, using the subscription's item(s), set to auto-renew using the subscription's interval. When set, phase values cannot also be set.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the subscription schedule.
- `phases` (`array`, optional): List of phases for the subscription schedule. Each phase can have different prices/quantities and duration. The end_date of one phase equals the start_date of the next.
- `start_date` (`string`, optional): When the subscription schedule starts. Use 'now' to start immediately, or a Unix timestamp to backdate/postdate the start.

Example input: `{}`

### `stripe_create_tax_rate_dahlia`

Create Tax Rate · Write

Create a tax rate that can be applied to invoices and subscriptions.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `display_name` (`string`, required): Label shown to customers on invoices and receipts, e.g. VAT or GST.
- `inclusive` (`boolean`, required): Whether the tax is included in the price (true) or added on top (false).
- `percentage` (`number`, required): The tax rate percentage as a decimal, e.g. 20.0 for 20%.
- `country` (`string`, optional): Two-letter ISO country code the tax rate applies to, e.g. DE or US.
- `description` (`string`, optional): Internal description of the tax rate, not shown to customers.
- `jurisdiction` (`string`, optional): The jurisdiction for the tax rate, displayed on invoices.
- `metadata` (`object`, optional): Set of key-value pairs for storing additional information.
- `state` (`string`, optional): State, county, province, or region the tax rate applies to.

Example input: `{"display_name":"<display_name>","inclusive":true,"percentage":20}`

### `stripe_create_transfer_dahlia`

Create Transfer · Write

Create a transfer to send funds to a connected Stripe account (Connect platforms).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount` (`integer`, required): Amount to transfer in the smallest currency unit (e.g. cents for USD).
- `currency` (`string`, required): Three-letter ISO currency code (lowercase) for the transfer.
- `destination` (`string`, required): The ID of the connected Stripe account to transfer funds to.
- `description` (`string`, optional): An optional description of the transfer.
- `source_transaction` (`string`, optional): The ID of a charge to use as the source for the transfer.

Example input: `{"amount":100,"currency":"<currency>","destination":"<destination>"}`

### `stripe_create_transfer_reversal_dahlia`

Create Transfer Reversal · Write

Reverses a transfer, in full or in part. Multiple partial reversals are allowed until the entire transfer amount has been reversed. A fully-reversed transfer cannot be reversed again.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `transfer_id` (`string`, required): The ID of the transfer to reverse.
- `amount` (`integer`, optional): The amount in the smallest currency unit to reverse. Omit to reverse the entire remaining transfer amount.
- `description` (`string`, optional): An arbitrary string attached to the reversal object.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the reversal.
- `refund_application_fee` (`boolean`, optional): Whether the application fee should be refunded when reversing this transfer.

Example input: `{"transfer_id":"<transfer_id>"}`

### `stripe_create_webhook_endpoint_dahlia`

Create Webhook Endpoint · Write

Create a webhook endpoint to receive Stripe event notifications at your HTTPS URL. Supports subscribing to any number of event types (or use * to receive all events).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `enabled_events` (`array`, required): Array of event types to subscribe to. Use ["*"] to receive all events.
- `url` (`string`, required): The HTTPS URL of your webhook endpoint.
- `description` (`string`, optional): An optional description of the webhook endpoint.

Example input: `{"enabled_events":[],"url":"<url>"}`

### `stripe_detach_payment_method_dahlia`

Detach Payment Method · Write

Detach a PaymentMethod from a Customer, making it reusable for other customers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The ID of the PaymentMethod to detach.

Example input: `{"id":"<id>"}`

### `stripe_expire_checkout_session_dahlia`

Expire Checkout Session · Write

Expire a Checkout Session before it has been completed. Can only expire sessions in 'open' status.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `session` (`string`, required): The ID of the Checkout Session to expire.

Example input: `{"session":"<session>"}`

### `stripe_finalize_invoice_dahlia`

Finalize Invoice · Write

Stripe automatically finalizes drafts before sending them. However, if you'd like to finalize a draft invoice manually, you can do so using this method. After an invoice is finalized, it can be paid or sent to customers.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to finalize.
- `auto_advance` (`boolean`, optional): Controls whether Stripe performs automatic collection of the invoice after finalization.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_finalize_quote_dahlia`

Finalize Quote · Write

Finalize a Quote to make it ready to be accepted by the customer.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `quote` (`string`, required): The ID of the quote to finalize.
- `expires_at` (`integer`, optional): Unix timestamp at which the finalized quote will expire.

Example input: `{"quote":"<quote>"}`

### `stripe_pay_invoice_dahlia`

Pay Invoice · Write

Stripe automatically creates and then attempts to collect payment on invoices for customers on subscriptions according to your subscriptions settings. However, if you'd like to attempt payment on an invoice out of the normal collection schedule or for some other reason, you use this endpoint.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to pay.
- `forgive` (`boolean`, optional): In cases where the source used to pay the invoice has insufficient funds, the invoice becomes past_due. Setting forgive to true forgives the invoice and marks it as paid.
- `payment_method` (`string`, optional): ID of the payment method to use for this invoice payment.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_resume_subscription_dahlia`

Resume Subscription · Write

Initiates resumption of a paused subscription, optionally resetting the billing cycle anchor and creating prorations. Only available for subscriptions using the charge_automatically collection method.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `subscription_id` (`string`, required): The ID of the paused subscription to resume.
- `billing_cycle_anchor` (`string`, optional): The billing cycle anchor to apply when resuming: 'now' or 'unchanged'. Defaults to 'now'. One of: `now`, `unchanged`.
- `expand` (`array`, optional): List of fields to expand in the response.
- `proration_behavior` (`string`, optional): How to handle prorations resulting from the billing_cycle_anchor being 'unchanged'. One of: `always_invoice`, `create_prorations`, `none`.

Example input: `{"subscription_id":"<subscription_id>"}`

### `stripe_send_invoice_dahlia`

Send Invoice · Write

Manually sends an invoice to the customer's email out of the normal automatic billing schedule. In test mode, no email is actually sent even though an invoice.sent event fires.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the finalized invoice to send.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_update_account_capability_dahlia`

Update Account Capability · Write

Updates an existing account capability by requesting it or removing a previous request. Request or remove a capability by updating its 'requested' parameter.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `capability` (`string`, required): The capability identifier, e.g. card_payments or transfers.
- `expand` (`array`, optional): List of fields to expand in the response.
- `requested` (`boolean`, optional): Whether to request the capability. Pass true to request it; pass false to remove a previous request.

Example input: `{"account":"<account>","capability":"<capability>"}`

### `stripe_update_account_dahlia`

Update Account · Write

Updates a connected account by setting the values of the parameters passed. Any parameters not provided are left unchanged.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account to update.
- `business_profile` (`object`, optional): Business information shown to customers, such as the business's URL and MCC.
- `company` (`object`, optional): Information about the company, used when business_type is 'company'.
- `default_currency` (`string`, optional): Three-letter ISO currency code representing the default currency for the account.
- `email` (`string`, optional): The email address of the account holder.
- `expand` (`array`, optional): List of fields to expand in the response.
- `individual` (`object`, optional): Information about the individual represented by the account.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the account.
- `tos_acceptance` (`object`, optional): Details on the account's acceptance of the Stripe Services Agreement.

Example input: `{"account":"<account>"}`

### `stripe_update_account_person_dahlia`

Update Account Person · Write

Updates an existing person associated with a connected account's legal entity.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `person` (`string`, required): The ID of the person to update.
- `address` (`object`, optional): The person's address.
- `email` (`string`, optional): The person's email address.
- `expand` (`array`, optional): List of fields to expand in the response.
- `first_name` (`string`, optional): The person's first name.
- `last_name` (`string`, optional): The person's last name.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the person.
- `phone` (`string`, optional): The person's phone number.
- `relationship` (`object`, optional): The relationship that this person has with the account's legal entity.

Example input: `{"account":"<account>","person":"<person>"}`

### `stripe_update_charge_dahlia`

Update Charge · Write

Updates the specified charge by setting the values of the parameters passed. Any parameters not provided are left unchanged.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `charge_id` (`string`, required): The ID of the charge to update.
- `description` (`string`, optional): An arbitrary string attached to the charge.
- `expand` (`array`, optional): List of fields to expand in the response.
- `fraud_details` (`object`, optional): Information about the charge's riskiness, e.g. marking it as fraudulent or safe.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the charge.
- `receipt_email` (`string`, optional): This is the email address that the receipt for this charge will be sent to.

Example input: `{"charge_id":"<charge_id>"}`

### `stripe_update_checkout_session_dahlia`

Update Checkout Session · Write

Updates an open Checkout Session, such as extending its expiration or changing its line items. Related guide: dynamically updating a Checkout Session.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `session_id` (`string`, required): The ID of the Checkout Session to update.
- `collected_information` (`object`, optional): Information about the customer collected within the session. Can only be set when updating embedded or custom sessions.
- `expand` (`array`, optional): List of fields to expand in the response.
- `line_items` (`array`, optional): The full list of items the customer is purchasing. When updating, you must retransmit the entire array; include an existing item's id to retain it.

Example input: `{"session_id":"<session_id>"}`

### `stripe_update_coupon_dahlia`

Update Coupon · Write

Update a coupon's name or metadata.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `coupon` (`string`, required): The ID of the coupon to update.
- `metadata` (`object`, optional): Set of key-value pairs for storing additional information. Replaces existing metadata.
- `name` (`string`, optional): Updated name for the coupon, shown to customers.

Example input: `{"coupon":"<coupon>"}`

### `stripe_update_customer_dahlia`

Update Customer · Write

Updates the specified customer by setting the values of the parameters passed. Any parameters not provided will be left unchanged.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer to update.
- `address` (`object`, optional): The customer's address as a JSON object with fields: line1, line2, city, state, postal_code, country.
- `description` (`string`, optional): An arbitrary string that you can attach to a customer object.
- `email` (`string`, optional): Customer's email address.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the customer. Pass an empty value to remove a key.
- `name` (`string`, optional): The customer's full name or business name.
- `phone` (`string`, optional): The customer's phone number.
- `tax_exempt` (`string`, optional): The customer's tax exemption status. One of: none, exempt, or reverse. One of: `none`, `exempt`, `reverse`.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_update_dispute_dahlia`

Update Dispute · Write

Update a dispute to submit evidence to the card issuer and potentially win the chargeback.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `dispute` (`string`, required): The ID of the dispute to update.
- `customer_email_address` (`string`, optional): Customer's email address as evidence.
- `customer_name` (`string`, optional): Customer's name as evidence.
- `product_description` (`string`, optional): Description of the product or service as evidence.
- `shipping_documentation` (`string`, optional): File ID for shipping documentation evidence.
- `submit` (`boolean`, optional): If true, immediately submit evidence to the card issuer.

Example input: `{"dispute":"<dispute>"}`

### `stripe_update_invoice_item_dahlia`

Update Invoice Item · Write

Update an invoice item's amount, description, or metadata.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `invoiceitem` (`string`, required): The ID of the invoice item to update.
- `amount` (`integer`, optional): The new amount in the smallest currency unit (e.g. cents for USD).
- `description` (`string`, optional): An updated description for the invoice item.
- `quantity` (`integer`, optional): Non-negative integer quantity of units for this invoice item.

Example input: `{"invoiceitem":"<invoiceitem>"}`

### `stripe_update_payment_intent_dahlia`

Update Payment Intent · Write

Updates properties on a PaymentIntent object without confirming it. Updating certain properties, such as payment_method, requires confirming the PaymentIntent again afterward.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `payment_intent_id` (`string`, required): The ID of the PaymentIntent to update.
- `amount` (`integer`, optional): Amount intended to be collected, in the smallest currency unit.
- `currency` (`string`, optional): Three-letter ISO currency code.
- `customer` (`string`, optional): ID of the customer this PaymentIntent belongs to.
- `description` (`string`, optional): An arbitrary string attached to the object, useful for displaying to users.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the PaymentIntent.
- `receipt_email` (`string`, optional): Email address the receipt for the resulting payment will be sent to.

Example input: `{"payment_intent_id":"<payment_intent_id>"}`

### `stripe_update_payment_method_dahlia`

Update Payment Method · Write

Updates a PaymentMethod object. The PaymentMethod must already be attached to a customer to be updated.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `payment_method_id` (`string`, required): The ID of the payment method to update.
- `billing_details` (`object`, optional): Billing information associated with the payment method.
- `card` (`object`, optional): If this is a card PaymentMethod, a hash of updatable card fields (currently only exp_month and exp_year).
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the payment method.

Example input: `{"payment_method_id":"<payment_method_id>"}`

### `stripe_update_payout_dahlia`

Update Payout · Write

Updates the specified payout by setting the values of the parameters passed. This request only accepts metadata as an argument.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `payout_id` (`string`, required): The ID of the payout to update.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the payout.

Example input: `{"payout_id":"<payout_id>"}`

### `stripe_update_plan_dahlia`

Update Plan · Write

Update a Plan's nickname, active status, or metadata.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `plan` (`string`, required): The ID of the plan to update.
- `active` (`boolean`, optional): Whether the plan is currently available for new subscriptions.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the plan object.
- `nickname` (`string`, optional): A brief description of the plan, hidden from customers.
- `trial_period_days` (`integer`, optional): Default number of trial days for subscriptions created using this plan.

Example input: `{"plan":"<plan>"}`

### `stripe_update_price_dahlia`

Update Price · Write

Updates the specified price by setting the values of the parameters passed. Any parameters not provided are left unchanged. Core pricing fields like unit_amount and currency are immutable once a price is created.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `price_id` (`string`, required): The ID of the price to update.
- `active` (`boolean`, optional): Whether the price can be used for new purchases. Defaults to true.
- `expand` (`array`, optional): List of fields to expand in the response.
- `lookup_key` (`string`, optional): A lookup key used to retrieve this price dynamically from a static string.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the price.
- `nickname` (`string`, optional): A brief description of the price, hidden from customers.
- `tax_behavior` (`string`, optional): Whether the price is considered inclusive or exclusive of tax. One of: `exclusive`, `inclusive`, `unspecified`.

Example input: `{"price_id":"<price_id>"}`

### `stripe_update_product_dahlia`

Update Product · Write

Updates the specific product by setting the values of the parameters passed. Any parameters not provided will be left unchanged.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): The ID of the product to update.
- `active` (`boolean`, optional): Whether the product is currently available for purchase.
- `description` (`string`, optional): The product's description.
- `images` (`array`, optional): A list of up to 8 URLs of images for this product.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the product.
- `name` (`string`, optional): The product's name.
- `unit_label` (`string`, optional): A label that represents units of this product.
- `url` (`string`, optional): A URL of a publicly-accessible webpage for this product.

Example input: `{"product_id":"<product_id>"}`

### `stripe_update_promotion_code_dahlia`

Update Promotion Code · Write

Update a promotion code's active status or metadata.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `promotion_code` (`string`, required): The ID of the promotion code to update.
- `active` (`boolean`, optional): Set to false to deactivate the promotion code so it can no longer be redeemed.
- `metadata` (`object`, optional): Set of key-value pairs for storing additional information. Replaces existing metadata.

Example input: `{"promotion_code":"<promotion_code>"}`

### `stripe_update_quote_dahlia`

Update Quote · Write

Update a draft Quote.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `quote` (`string`, required): The ID of the quote to update.
- `customer` (`string`, optional): The ID of the customer to associate with the quote.
- `description` (`string`, optional): A description visible to customers on the quote.
- `expires_at` (`integer`, optional): Unix timestamp at which the quote will expire.
- `footer` (`string`, optional): Footer text shown at the bottom of the quote document.
- `header` (`string`, optional): Header text shown at the top of the quote document.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the quote.

Example input: `{"quote":"<quote>"}`

### `stripe_update_refund_dahlia`

Update Refund · Write

Update the metadata on a refund.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The ID of the refund to update.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the refund as metadata.

Example input: `{"id":"<id>"}`

### `stripe_update_setup_intent_dahlia`

Update Setup Intent · Write

Updates a SetupIntent object prior to confirmation, such as changing the associated customer, payment method types, or description.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `setup_intent_id` (`string`, required): The ID of the SetupIntent to update.
- `customer` (`string`, optional): The ID of the Customer this SetupIntent belongs to.
- `description` (`string`, optional): An arbitrary string attached to the object, useful for displaying to users.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the SetupIntent.
- `payment_method` (`string`, optional): ID of the payment method to attach to this SetupIntent.

Example input: `{"setup_intent_id":"<setup_intent_id>"}`

### `stripe_update_subscription_dahlia`

Update Subscription · Write

Updates an existing subscription to match the specified parameters. When updating a subscription, any parameters not provided will be left unchanged.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription_id` (`string`, required): The ID of the subscription to update.
- `cancel_at_period_end` (`boolean`, optional): Boolean indicating whether this subscription should cancel at the end of the current period.
- `collection_method` (`string`, optional): Either charge_automatically or send_invoice. One of: `charge_automatically`, `send_invoice`.
- `days_until_due` (`integer`, optional): Number of days a customer has to pay invoices (send_invoice collection method only).
- `default_payment_method` (`string`, optional): ID of the default payment method for this subscription.
- `items` (`array`, optional): List of subscription items to update. Each item includes id, price, and/or quantity.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the subscription.
- `proration_behavior` (`string`, optional): Determines how to handle prorations when the billing cycle changes. One of: `always_invoice`, `create_prorations`, `none`.

Example input: `{"subscription_id":"<subscription_id>"}`

### `stripe_update_subscription_item_dahlia`

Update Subscription Item · Write

Update a subscription item, for example to change the price or quantity.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `item` (`string`, required): The ID of the subscription item to update.
- `price` (`string`, optional): The ID of the new price to switch this subscription item to.
- `proration_behavior` (`string`, optional): Determines how to handle prorations when modifying this item. One of: `create_prorations`, `none`, `always_invoice`.
- `quantity` (`integer`, optional): The updated quantity of the subscription item.

Example input: `{"item":"<item>"}`

### `stripe_update_subscription_schedule`

Update Subscription Schedule · Write

Updates an existing subscription schedule, e.g. to change its phases, end behavior, or default settings. Past phases can be omitted when specifying phases.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `subscription_schedule_id` (`string`, required): The ID of the subscription schedule to update.
- `default_settings` (`object`, optional): Default settings for the subscription schedule, applied to phases that don't override them.
- `end_behavior` (`string`, optional): Behavior when the schedule ends: 'release' (default, keeps the underlying subscription running as-is) or 'cancel' (cancels the underlying subscription). One of: `cancel`, `release`.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the subscription schedule. Individual keys can be unset by posting an empty value.
- `phases` (`array`, optional): List of phases for the subscription schedule. Note that past phases can be omitted; the end_date of one phase equals the start_date of the next.
- `proration_behavior` (`string`, optional): If the update changes the billing configuration of the current phase, indicates how prorations should be handled. Defaults to 'create_prorations'. One of: `always_invoice`, `create_prorations`, `none`.

Example input: `{"subscription_schedule_id":"<subscription_schedule_id>"}`

### `stripe_update_tax_rate_dahlia`

Update Tax Rate · Write

Update a tax rate's display name, description, or active status.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `tax_rate` (`string`, required): The ID of the tax rate to update.
- `active` (`boolean`, optional): Set to false to deactivate the tax rate.
- `description` (`string`, optional): An arbitrary string attached to the tax rate for your internal use.
- `display_name` (`string`, optional): The display name of the tax rate, shown to customers on invoices.
- `jurisdiction` (`string`, optional): The jurisdiction for the tax rate.

Example input: `{"tax_rate":"<tax_rate>"}`

### `stripe_update_transfer_dahlia`

Update Transfer · Write

Update a transfer's metadata.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `transfer` (`string`, required): The ID of the transfer to update.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the transfer. Stripe's update endpoint only accepts metadata — description cannot be changed after creation.

Example input: `{"transfer":"<transfer>"}`

### `stripe_update_webhook_endpoint_dahlia`

Update Webhook Endpoint · Write

Update a webhook endpoint's URL, enabled events, or disabled status.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `webhook_endpoint` (`string`, required): The ID of the webhook endpoint to update.
- `description` (`string`, optional): An updated description for the webhook endpoint.
- `disabled` (`boolean`, optional): Whether the webhook endpoint is disabled.
- `enabled_events` (`array`, optional): Updated list of event types this endpoint should receive.
- `url` (`string`, optional): The new HTTPS URL for the webhook endpoint.

Example input: `{"webhook_endpoint":"<webhook_endpoint>"}`

### `stripe_zz_test_echo_probe_dahlia`

ZZ Test Echo Probe · Write

Temporary throwaway tool for verifying raw wire bytes against an echo service. Not for real use — delete after testing.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `big_id` (`string`, optional): Body-spread large ID field, typed as string to avoid protobuf Struct's double-precision ceiling on NumberValue.
- `customer` (`string`, optional): Body-spread field.
- `expand` (`string`, optional): Query-mapped field.

Example input: `{}`

### `stripe_cancel_payment_intent_dahlia`

Cancel Payment Intent · Destructive

Cancels a PaymentIntent object when it's in a cancellable state. Depending on the payment method, it may be possible to cancel a PaymentIntent once it has been confirmed and is in requires_capture state.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `payment_intent_id` (`string`, required): The ID of the PaymentIntent to cancel.
- `cancellation_reason` (`string`, optional): Reason for canceling this PaymentIntent. One of: `duplicate`, `fraudulent`, `requested_by_customer`, `abandoned`.

Example input: `{"payment_intent_id":"<payment_intent_id>"}`

### `stripe_cancel_setup_intent_dahlia`

Cancel Setup Intent · Destructive

Cancel a SetupIntent that has not been confirmed.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `setup_intent_id` (`string`, required): The ID of the SetupIntent to cancel.
- `cancellation_reason` (`string`, optional): The reason for canceling the SetupIntent. One of: `abandoned`, `requested_by_customer`, `duplicate`.

Example input: `{"setup_intent_id":"<setup_intent_id>"}`

### `stripe_cancel_subscription_dahlia`

Cancel Subscription · Destructive

Cancels a customer's subscription immediately. The customer will not be charged again for the subscription. By default the subscription is canceled immediately but if prorate is set, any remaining charges are refunded.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `subscription_id` (`string`, required): The ID of the subscription to cancel.
- `cancellation_details` (`object`, optional): Details about why this subscription was cancelled.
- `invoice_now` (`boolean`, optional): Will generate a final invoice that charges for any un-invoiced metered usage.
- `prorate` (`boolean`, optional): Will generate a proration invoice item that credits remaining unused time until the subscription period end.

Example input: `{"subscription_id":"<subscription_id>"}`

### `stripe_cancel_subscription_schedule`

Cancel Subscription Schedule · Destructive

Cancels a subscription schedule and its associated subscription immediately (if the schedule has an active subscription). A subscription schedule can only be canceled if its status is 'not_started' or 'active'.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `subscription_schedule_id` (`string`, required): The ID of the subscription schedule to cancel.
- `invoice_now` (`boolean`, optional): If the subscription schedule is active, indicates whether a final invoice will be generated for any un-invoiced metered usage and pending proration items. Defaults to true.
- `prorate` (`boolean`, optional): If the subscription schedule is active, indicates whether the cancellation should be prorated. Defaults to true.

Example input: `{"subscription_schedule_id":"<subscription_schedule_id>"}`

### `stripe_close_dispute_dahlia`

Close Dispute · Destructive

Close a dispute and accept the chargeback. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `dispute` (`string`, required): The ID of the dispute to close.

Example input: `{"dispute":"<dispute>"}`

### `stripe_delete_account_dahlia`

Delete Account · Destructive

Deletes a connected account you manage. Test-mode accounts can be deleted at any time; live-mode accounts can only be deleted once all balances are zero and the account does not use the standard Stripe dashboard.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account to delete.

Example input: `{"account":"<account>"}`

### `stripe_delete_account_external_account_dahlia`

Delete Account External Account · Destructive

Deletes a specified external account (bank account or card) from a connected account.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `id` (`string`, required): Unique identifier for the external account to delete.

Example input: `{"account":"<account>","id":"<id>"}`

### `stripe_delete_account_person_dahlia`

Delete Account Person · Destructive

Deletes an existing person's relationship to a connected account's legal entity. The representative cannot be deleted through this endpoint.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `account` (`string`, required): The ID of the connected account.
- `person` (`string`, required): The ID of the person to delete.

Example input: `{"account":"<account>","person":"<person>"}`

### `stripe_delete_coupon_dahlia`

Delete Coupon · Destructive

Delete a coupon. Customers that have already applied this coupon are not affected.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `coupon` (`string`, required): The ID of the coupon to delete.

Example input: `{"coupon":"<coupon>"}`

### `stripe_delete_customer_dahlia`

Delete Customer · Destructive

Permanently deletes a customer. It cannot be undone. Also immediately cancels any active subscriptions on the customer.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer to delete.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_delete_customer_discount_dahlia`

Delete Customer Discount · Destructive

Removes the currently applied discount (coupon) from a customer.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer to remove the discount from.

Example input: `{"customer_id":"<customer_id>"}`

### `stripe_delete_customer_tax_id_dahlia`

Delete Customer Tax ID · Destructive

Deletes an existing tax ID object from a customer.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): The ID of the customer the tax ID belongs to.
- `tax_id` (`string`, required): The ID of the tax ID object to delete.

Example input: `{"customer_id":"<customer_id>","tax_id":"<tax_id>"}`

### `stripe_delete_invoice_dahlia`

Delete Invoice · Destructive

Permanently deletes a one-off invoice that is still in draft status. This cannot be undone. Finalized invoices, or invoices tied to a subscription, must be voided instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): The ID of the draft invoice to delete.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_delete_invoice_item_dahlia`

Delete Invoice Item · Destructive

Delete an invoice item. Can only delete items that have not been finalized in an invoice.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `invoiceitem` (`string`, required): The ID of the invoice item to delete.

Example input: `{"invoiceitem":"<invoiceitem>"}`

### `stripe_delete_plan_dahlia`

Delete Plan · Destructive

Delete a Plan. Customers subscribed to this plan are not affected.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `plan` (`string`, required): The ID of the plan to delete.

Example input: `{"plan":"<plan>"}`

### `stripe_delete_product_dahlia`

Delete Product · Destructive

Deletes a product. This is only possible if the product has no prices associated with it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `product_id` (`string`, required): The ID of the product to delete.

Example input: `{"product_id":"<product_id>"}`

### `stripe_delete_subscription_discount_dahlia`

Delete Subscription Discount · Destructive

Removes the currently applied discount (coupon) from a subscription.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `subscription_id` (`string`, required): The ID of the subscription to remove the discount from.

Example input: `{"subscription_id":"<subscription_id>"}`

### `stripe_delete_subscription_item_dahlia`

Delete Subscription Item · Destructive

Delete a subscription item, removing it from the subscription.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `item` (`string`, required): The ID of the subscription item to delete.
- `proration_behavior` (`string`, optional): Determines how to handle prorations when deleting this item. One of: `create_prorations`, `none`, `always_invoice`.

Example input: `{"item":"<item>"}`

### `stripe_delete_webhook_endpoint_dahlia`

Delete Webhook Endpoint · Destructive

Delete a webhook endpoint. Once deleted, the endpoint will no longer receive events from Stripe.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `webhook_endpoint` (`string`, required): The ID of the webhook endpoint to delete.

Example input: `{"webhook_endpoint":"<webhook_endpoint>"}`

### `stripe_mark_invoice_uncollectible_dahlia`

Mark Invoice Uncollectible · Destructive

Marks an invoice as uncollectible, which is useful for tracking bad debt that will be written off for accounting purposes.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to mark as uncollectible.
- `expand` (`array`, optional): List of fields to expand in the response.

Example input: `{"invoice_id":"<invoice_id>"}`

### `stripe_reverse_payout_dahlia`

Reverse Payout · Destructive

Reverses a payout by debiting the destination bank account. Only available for payouts to US and Canadian bank accounts. For a pending manual payout, cancel it instead of reversing it.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `payout_id` (`string`, required): The ID of the payout to reverse.
- `expand` (`array`, optional): List of fields to expand in the response.
- `metadata` (`object`, optional): Set of key-value pairs to attach to the reversal.

Example input: `{"payout_id":"<payout_id>"}`

### `stripe_void_credit_note`

Void Credit Note · Destructive

Marks a previously issued credit note as void. This cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `credit_note_id` (`string`, required): The ID of the credit note to void.

Example input: `{"credit_note_id":"<credit_note_id>"}`

### `stripe_void_invoice_dahlia`

Void Invoice · Destructive

Mark a finalized invoice as void. This cannot be undone. Voiding an invoice is similar to deletion, however it only applies to finalized invoices and maintains a papertrail where the invoice can still be found.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `invoice_id` (`string`, required): The ID of the invoice to void.

Example input: `{"invoice_id":"<invoice_id>"}`

## Related

Other ways to connect Stripe:

- [MCP server](/agentkit/connectors/stripemcp/): Vendor MCP, OAuth, 12 tools

Other Accounting & Finance connectors ([all 47](/agentkit/connectors/?category=accounting-finance)):

- [QuickBooks](/agentkit/connectors/quickbooks/): Scalekit connector, OAuth, 117 tools
- [Xero](/agentkit/connectors/xero/): Scalekit connector, OAuth, 94 tools
- [Brex](/agentkit/connectors/brex/): Scalekit connector, OAuth, 68 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
