connect-required-verification-information

Fetches Stripe Connect account verification requirements via docs API endpoints.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill connect-required-verification-information-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-required-verification-information
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/connect-required-verification-information
Command: npx skills add https://github.com/divinaarmuela/Content --skill connect-required-verification-information-divinaarmuela

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining which verification fields, documents, and business details a Stripe Connect connected account must provide is complex because requirements vary by platform country, account country, dashboard type, service agreement, business type, and capabilities. This Skill queries Stripe's public docs endpoints and renders the exact requirements for any validated setup. ## Core Features & Use Cases - Guided setup validation: Walks the user through a dependency-ordered flow (API version, platform country, account country, dashboard type, service agreement, business type, capabilities) using multiple-choice questions, validating every option against live API responses. - Requirements retrieval and rendering: Calls the get-requirements-for-setups endpoint and transforms the response into per-section tables (Account, Company, Representative, Owners, etc.) with requirement fields, verification guidance, and enforcement actions. - Setup comparison and supplemental checks: Supports A/B comparison of two setups, JSON summaries of currently due versus eventually due fields, and supplemental website and MCC restriction tables per capability. - Use Case: A platform engineer onboarding a French company account from a Canadian platform asks what verification information is needed for card payments; the Skill validates the setup and returns the exact required fields and documents. ## Quick Start Ask what verification information a Stripe connected account needs for your platform country, account country, business type, and capabilities.

Frequently Asked Questions about connect-required-verification-information

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

FAQPage Schema
How do I find required verification information for a Stripe Connect account?

Provide your platform country, account country, dashboard type, service agreement, business type, and capabilities. The Skill validates each choice against Stripe's docs endpoints and returns the exact required fields, documents, and enforcement deadlines for that setup.

How do I compare verification requirements between two Connect account setups?

The Skill validates setup A and setup B independently, then calls the requirements endpoint with both account-setup-A and account-setup-B keys. It returns a diffable comparison showing which requirement fields differ between the two configurations.

Does Stripe Connect v2 API support all v1 capabilities?

No. The Skill fetches the get-v2-supported-v1-capabilities endpoint and filters out any capability not supported under v2. If you request an unsupported capability like paypal_payments, it explains the conflict and offers switching to v1 or choosing another capability.

Why is a capability unavailable for my Connect account setup?

Capabilities are constrained by account country, service agreement type, and API version. For example, recipient service agreements force the transfers capability, and v2 accounts drop unsupported v1 capabilities. The Skill explains the specific constraint and asks you to revise the setup.

What happens if the requirements endpoint returns validation errors?

Validation errors mean the setup inputs are invalid, so the Skill asks you to correct the conflicting choices rather than guessing. Build errors are treated as retryable failures, and the request is retried before reporting an unexpected endpoint failure.