Plan a Stripe Connect Integration in Codex with a Sample Marketplace Flow
Use Connect Recommend to turn a fictional marketplace brief into questions about payment routing, connected accounts and responsibilities before writing an integration.
中文Setup for Codex
Use Codex and the pinned skill with its references. The exercise uses a fictional example and produces a review of design choices. A real integration needs current Stripe documentation and account-specific requirements.
- Open Stripe's fixed source below. Copy the full sibling skill directory connect-recommend, including references, into .agents/skills/connect-recommend in a practice project.
- Open Codex in the practice project and select $connect-recommend. Read any bundled task-specific reference it identifies before working through the example.
Example task
Ask $connect-recommend to describe the unresolved design choices for a fictional craft marketplace that may collect one order and distribute proceeds to two sellers. Give no commission, region or merchant-of-record assumptions. Request an interview and a draft decision table only.Expected result
The interview identifies who charges customers, how the transfer timing should work, who owns fees and negative balances, and what Dashboard access sellers need. The table leaves unconfirmed decisions open, and there are no account or payment changes.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
What should I define before selecting a Stripe Connect charge pattern?
Describe the customer-to-seller fund flow, settlement timing and desired connected-account management. Confirm who handles fees, disputes and negative balances before turning a proposed pattern into code.