connect-required-verification-information

Fetches Stripe Connect account verification requirements via docs.stripe.com endpoints.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ttakci/sellerhill --skill connect-required-verification-information-ttakci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect-required-verification-information
Source: https://github.com/ttakci/sellerhill/tree/main/.grok/skills/connect-required-verification-information
Command: npx skills add https://github.com/ttakci/sellerhill --skill connect-required-verification-information-ttakci

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 documentation endpoints to return accurate, validated requirement tables instead of guesswork. ## 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: Calls get-requirements-for-setups and renders sectioned tables (Account, Company, Representative, Owners, etc.) with requirement fields, verification notes, and enforcement actions. - Setup Comparison: Supports A/B comparison of two account configurations, including ORR program (e.g., EU 2025) updates, plus 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 with enforcement deadlines. ## 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 to compare verification requirements between two Stripe Connect 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 of required fields, useful for evaluating changes like adopting the EU 2025 requirements update.

What is the difference between v1 and v2 Accounts API requirements?

For v2, capabilities are filtered against the supported v1 capability list and fields are rendered using v2_field_name values. Fields without a v2 mapping are omitted, and JSON summaries are informational only and do not match real API response shapes.

Why is a capability unavailable for my Stripe Connect setup?

Capabilities are constrained by account country, service agreement type, and API version. For example, recipient service agreements force transfers only, and some capabilities like paypal_payments are unsupported on v2 accounts. The Skill explains the conflict and offers valid alternatives.

Does Stripe Connect verification depend on business type and country?

Yes. Requirements vary by account country, legal entity type (individual or company), and business structure. The Skill fetches the country_map for your platform country to determine exactly which fields, documents, and person-related requirements apply.