AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

connect-required-verification-information

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

Original source
stripe
License
MIT
Pinned revision
1e24cf59cb0dd78df298afc3b7d372e5a5055ece

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read stripe--connect-required-verification-information at revision 1e24cf59cb0dd78df298afc3b7d372e5a5055ece, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 1

SKILL.md · 24000

apiVersion=v2 and a requirement doesn’t expose v2_field_name, omit that field from the rendered table. If that removes every field from a row group, omit the row. If a section becomes empty, omit that section table.

How to construct the JSON-style summary:
  • if the user asks for a JSON summary of required items, return a JSON object in this exact shape. Each array holds zero or more field names:
    {
      "requirements": {
        "currently_due": [
          "configuration.merchant.mcc",
          "company.name",
          "representative.first_name"
        ],
        "eventually_due": [
          "business_profile.url"
        ]
      }
    }
    

Do not use ellipses (...) or placeholder strings in the output — list every field name explicitly.

  • this shape is a derived summary for comparison and display. It isn’t a raw Accounts API response.
  • If apiVersion=v2, inform the user that this JSON is for information only, and doesn’t match the shape of a real API response.
  • derive each field’s due bucket from the requirement’s limit fields in the get-requirements-for-setups response:
    • treat a field as currently_due when any unverified limit amount or time is <= 0, or any verified limit amount or time is <= 0
    • otherwise treat it as eventually_due
  • populate requirements.currently_due and requirements.eventually_due from those derived buckets
  • don’t add a separate future_requirements bucket. Regulatory or ORR-driven future changes are modeled through orrProgram setup selection and A/B setup comparison, not through a third due array
  • for apiVersion=v1, use the raw requirement field names in both arrays
  • for apiVersion=v2, use v2_field_name values in both arrays
  • If apiVersion=v2, omit fields that have no v2_field_name
  • the JSON diff view compares requirement names only; it doesn’t diff verification text, thresholds, or supplemental metadata

How to respond to users

When you return results to the user:

  • restate the exact validated setup you queried, including apiVersion, platformCountry, accountCountry, dashboardType, tosType, legalEntityType, optional businessStructure, selected capabilities, and optional orrProgram
  • always provide the user with a link containing the exact URL query parameters you used so they can view the requirements themselves and verify your conclusions
    • for example: https://docs.stripe.com/_endpoint/get-requirements-for-setups?account-setup-A[platformCountry]=CA&account-setup-A[accountCountry]=FR&account-setup-A[dashboardType]=full&account-setup-A[tosType]=full&account-setup-A[legalEntityType]=individual&account-setup-A[capabilities][0]=card_payments&account-setup-A[orrProgram]=eu-2025 -> https://docs.stripe.com/connect/required-verification-information?accountSetupKeys=account-setup-A&account-setup-A%5BapiVersion%5D=v2&account-setup-A%5BplatformCountry%5D=CA&account-setup-A%5BaccountCountry%5D=FR&account-setup-A%5BdashboardType%5D=full&account-setup-A%5BtosType%5D=full&account-setup-A%5BlegalEntityType%5D=individual&account-setup-A%5BbusinessStructure%5D=undefined&account-setup-A%5Bcapabilities%5D=card_payments&account-setup-A%5BorrProgram%5D=eu-2025
    • when comparing two setups, include account-setup-B in the page URL only if you validated and queried setup B
  • if any requested choice had to be changed because of selector dependencies, say so explicitly before presenting the requirements
  • present currently due requirements separately from eventually due requirements, and label them clearly
  • explain verification bullets using extras[].value as the source of truth
  • mention when a requirement was omitted because it matched none of the table row definitions in this document
  • mention when website or MCC endpoints returned no supplemental data, so the user doesn’t mistake that for a fetch failure
  • if you receive validation_errors, ask the user to correct the setup inputs using the Interaction contract instead of guessing
  • if you receive build_errors, retry the request; if the error persists, tell the user the helper endpoint failed unexpectedly