stripe-app-setup

Create and securely store a Stripe restricted API key with least-privilege access.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CerisonAutomation/clud --skill stripe-app-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-app-setup
Source: https://github.com/CerisonAutomation/clud/tree/main/skills/stripe-app-setup
Command: npx skills add https://github.com/CerisonAutomation/clud --skill stripe-app-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you create and securely store a Stripe restricted API key so your assistant can access only the required Stripe resources, reducing risk while enabling payment, subscription, customer, invoice, and refund workflows.

Core Features & Use Cases

  • Restricted API key creation: Guides you through creating a Stripe Restricted API Key (RAK) with least-privilege permissions.
  • Secure credential storage: Prompts for the key and stores it in the credential vault with Stripe-domain injection templates for Authorization headers.
  • Connectivity verification: Checks the stored credential by calling Stripe’s balance endpoint and reports clear outcomes for 401/403 errors.
  • Practical integration readiness: Ensures the assistant can make both read and (with confirmation) write calls such as listing customers, checking subscriptions, retrieving invoices, and issuing refunds.

Quick Start

Tell the assistant: “Run stripe-app-setup and help me configure my Stripe restricted API key, then verify access to account balance.”

Frequently Asked Questions about stripe-app-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a restricted API key for Stripe to manage payments and subscriptions?

To set up a restricted API key for Stripe, you run the provided check and store scripts to securely collect an rk_* key and enforce least-privilege access for managing payments, subscriptions, and refunds.

What is the least-privilege approach for Stripe API credential storage?

The least-privilege approach for Stripe credential storage involves creating a Restricted API Key that limits access strictly to required resources, securely storing it in a vault, and injecting Stripe-domain Authorization headers for subsequent API calls.

How do I verify Stripe API connectivity after storing a restricted key?

You verify Stripe API connectivity by checking the stored credential against Stripe's balance endpoint, ensuring the restricted key is valid and correctly handling any 401 or 403 authentication errors that occur.

Can I use a restricted Stripe key to issue refunds and retrieve invoices?

Yes, you can use a restricted Stripe key to issue refunds and retrieve invoices. The key enables both read and confirmed write calls, including listing customers, checking subscriptions, and managing payment workflows.

Why does my Stripe restricted key return a 401 or 403 error when checking balance?

A Stripe restricted key returns a 401 or 403 error during balance verification when the credential is invalid, lacks sufficient permissions, or the Authorization header injection for api.stripe.com is incorrectly configured.