User Research
Choose a research method from the decision it must inform; recruit relevant experience and preserve evidence through synthesis.
Integrate payment behavior from current Stripe documentation and the approved billing model.
---
name: knoveya-stripe-best-practices
description: "Integrate payment behavior from current Stripe documentation and the approved billing model. Use for matching product work."
---
# Stripe Best Practices
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Integrate payment behavior from current Stripe documentation and the approved billing model.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Webhook verification, idempotency, and entitlement decisions are tested safely.
## Example task
Use sandbox events to test repeated delivery before production.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-stripe-best-practices as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-stripe-best-practices/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Use sandbox events to test repeated delivery before production.
Webhook verification, idempotency, and entitlement decisions are tested safely.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.