skills.rest
stripe
stripeOFFICIAL
Explore all skills by this author →
Website𝕏@StripeDevGitHub

connect-required-verification-information

Fetches Stripe Connect account verification requirements via docs API endpoints.

1.8k|329|Updated Nov 11, 2024
Search Tags:#capabilities#Onboarding#API Validation#kyc#connected accounts#Stripe Connect#verification requirements
One-click install
npx skills add https://github.com/stripe/ai --skill connect-required-verification-information
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect-required-verification-information
Source: https://github.com/stripe/ai/tree/main/providers/cursor/plugin/skills/connect-required-verification-information
Command: npx skills add https://github.com/stripe/ai --skill connect-required-verification-information

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 guides an agent through a validated, dependency-aware question flow and calls Stripe's public docs endpoints to return accurate requirements.

Core Features & Use Cases

  • Guided setup validation: Collects apiVersion, platformCountry, accountCountry, dashboardType, tosType, legalEntityType, businessStructure, capabilities, and optional ORR programs in dependency order, pre-validating every option against live API responses.
  • Requirements retrieval: Calls get-requirements-for-setups plus supplemental website-requirements and MCC-restriction endpoints, then renders sectioned tables (Account, Company, Representative, Owners, etc.) with requirement, verification, and enforcement columns.
  • Setup comparison: Supports A/B comparisons of two account setups and JSON summaries of currently_due versus eventually_due fields.
  • Use Case: A platform engineer asks what a French company account on a Canadian platform needs for card_payments; the agent validates the setup, queries the endpoints, and returns the exact KYC fields and enforcement deadlines.

Quick Start

Ask the agent what verification information a Stripe Connect 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 agent validates each choice against Stripe's docs endpoints and calls get-requirements-for-setups to return the exact required fields, documents, and enforcement deadlines.

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

The agent validates setup A and setup B independently using account-setup-A and account-setup-B keys, then calls the requirements endpoint with both setups. It returns a diffable comparison of required fields between the two configurations.

Does Stripe Connect v2 API support all v1 capabilities?▼

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

Why is a capability unavailable for my Connect account setup?▼

Capabilities depend on account country, service agreement type, and API version. For example, tosType recipient forces transfers and removes most other capabilities. The agent explains the constraint and asks you to revise earlier setup choices.

What happens if the requirements endpoint returns validation errors?▼

A validation_errors response means the setup inputs were invalid, so the agent asks you to correct the conflicting fields rather than guessing. A build_errors response is treated as a retryable failure, and the request is retried before reporting any problem.

Related Skills

Explore More Software Engineering Skills→
openaiopenai
5.3k

stripe-best-practices

Guides Stripe integration decisions across payments, Connect, billing, and Treasury APIs.

Official
Intermediate
zacharyr0thzacharyr0th

stripe-connect

Manage Stripe Connect account onboarding, verification, charges, transfers, and payouts.

Community
Advanced
AeyeOpsAeyeOps

workflow-automation

Automates accounting firm workflows via event-driven triggers and recurring tasks.

Official
Advanced
openaiopenai
5.3k

stripe-docs

Reads and searches Stripe documentation and API reference via the stripe docs CLI command.

Official
Basic