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-setupsresponse:- treat a field as
currently_duewhen any unverified limit amount or time is<= 0, or any verified limit amount or time is<= 0 - otherwise treat it as
eventually_due
- treat a field as
- populate
requirements.currently_dueandrequirements.eventually_duefrom those derived buckets - don’t add a separate
future_requirementsbucket. Regulatory or ORR-driven future changes are modeled throughorrProgramsetup 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, usev2_field_namevalues in both arrays - If
apiVersion=v2, omit fields that have nov2_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, optionalbusinessStructure, selectedcapabilities, and optionalorrProgram - 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-Bin the page URL only if you validated and queried setup B
- for example:
- 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[].valueas 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