Stripe

The Stripe connector is broad — it covers the core payments API, Connect (marketplace onboarding and payouts), and Issuing (cards). Because agents that move money are the most sensitive class of integration, every Stripe operation requires an explicit approval in your tool-decision policy.

Setup

1. Stripe dashboard

• Developers → API keys — note restricted key for TapPass
• Create a restricted key scoped to only the resources you’ll let agents touch (read vs write per resource)

2. Configure TapPass

# Stripe Connect OAuth (for platform/marketplace accounts):
STRIPE_CLIENT_ID=ca_...
STRIPE_CLIENT_SECRET=sk_...
# For webhooks:
STRIPE_WEBHOOK_SECRET=whsec_...

The secret API key (sk_live_... / sk_test_...) the connector calls with is stored as a vault credential — connect via GET /api/connect/stripe or the dashboard. STRIPE_TEST_MODE=1 marks the deployment as test mode (UI labels and audit trail).

Operations

The connector ships 40+ operations covering Payment Intents, charges, refunds, customers, invoices, payouts, products/prices, subscriptions, and Issuing — e.g.:

Operation	Op group
create_payment_intent	write
get_charge, list_charges	read
create_refund	write
list_customers, create_customer	read / write
create_subscription, cancel_subscription	write
create_issuing_card, approve_issuing_authorization	write

Amounts and targets can be capped per-operation in the provider spec (e.g. max_amount, allowed_currencies, max_refund_amount). Treat write ops as default-deny in your own policy: opt in explicitly in your tool-decision policy.

Usage

Your agent never calls Stripe directly. When the model requests a Stripe operation as a tool call through the governed gateway, TapPass resolves the provider, fetches the connected credential from the vault, executes the operation, and audits the call — write operations only proceed when policy approves them.

Policy example

Allow refunds up to €50 for tier-1 support agents only:

For example, you can allow create_refund only for the support-tier-1 role and only up to a capped amount. Rules like this are authored in the dashboard, from a template, or in plain English.

Idempotency

TapPass automatically sets Idempotency-Key headers for Stripe write operations, derived from the audit event ID. Safe to retry — Stripe will return the original result.

Data residency

Stripe offers EU data residency (the request stays in EU regions) — enable it in your Stripe dashboard under Settings → Data residency.