connect-required-verification-information

Fetches Stripe Connect account verification requirements for validated onboarding configurations.

2|Updated Aug 12, 2026
One-click install
npx skills add https://github.com/prianshumitra/Rentify --skill connect-required-verification-information-prianshumitra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect-required-verification-information
Source: https://github.com/prianshumitra/Rentify/tree/main/backend/.agents/skills/connect-required-verification-information
Command: npx skills add https://github.com/prianshumitra/Rentify --skill connect-required-verification-information-prianshumitra

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 data instead of guesswork. ## Core Features & Use Cases - Guided Setup Validation: Collects platform country, account country, dashboard type, service agreement, legal entity type, business structure, and capabilities through a dependency-aware question flow that pre-validates every option. - Requirements Retrieval: Calls Stripe's get-requirements-for-setups endpoint and renders sectioned tables (Account, Company, Representative, Owners, etc.) with requirement fields, verification guidance, and enforcement actions. - Setup Comparison: Supports comparing two account configurations (A/B) to show requirement differences, 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 desired 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 what verification information a Stripe Connect account needs?▼

Provide your platform country, account country, dashboard type, service agreement, business type, and desired capabilities. The Skill validates each choice against Stripe's requirement-selections endpoint, then queries get-requirements-for-setups and returns sectioned tables of required fields with verification guidance.

How to compare verification requirements between two Stripe Connect setups?▼

Both setups are validated independently as account-setup-A and account-setup-B, then submitted together to the requirements endpoint. The result shows which fields differ between the two configurations, useful when planning upgrades or regulatory program changes.

Does Stripe Connect v2 support all v1 capabilities?▼

No. When apiVersion is v2, capabilities are filtered against the get-v2-supported-v1-capabilities list, and unsupported capabilities like paypal_payments are dropped. The Skill explains the incompatibility and offers switching to v1 or choosing a different capability.

Why is a capability unavailable for my Stripe connected account setup?▼

Capabilities are constrained by account country, service agreement type, and API version. For example, recipient service agreements force transfers only, and v2 accounts drop unsupported v1 capabilities. The Skill shows the filtered valid list and explains any exclusions.

What happens if Stripe requirements endpoint returns validation errors?▼

Validation errors mean the setup inputs are invalid and must be corrected before interpreting results; the Skill asks you to revise the conflicting fields. Build errors are treated as retryable failures rather than business conclusions.