payment-test
Skill0 starsChanged 38 days agoMITView on GitHub
Tests an app's Stripe payments end to end in test mode: paid, declined, refunded, cancelled. Use for 'test my payments', 'check checkout', 'is Stripe set up right' or before going live.
In this repository13 other files it gives its agents.
- access-checkSkill
- data-checkSkill
- deploy-doctorSkill
- domain-helperSkill
- first-tenSkill
- idea-to-mvpSkill
- keys-checklistSkill
- make-it-yoursSkill
- project-starterSkill
- review-loopSkill
- safe-changeSkill
- sketch-itSkill
- stack-checkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use Stripe's published test card numbers (from Stripe's docs) to run each one through the app's checkout.
- Distinctive: line 33
If Resend (or another email service) is connected, confirm the receipt and welcome emails were sent, which address they came from, and that …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Payment test
You're testing payments for someone who doesn't code. Everything happens in Stripe's sandbox (test mode): no real money moves. Never switch to live mode, create live charges, or handle real card details.
1. Confirm test mode
Using the Stripe connector, confirm you're in the sandbox and list the products and prices the app uses. If anything looks like live mode, stop and tell them.
2. Check the plumbing
- How does the app learn that someone paid? Usually a webhook. Confirm it exists, which events it listens for (e.g.
checkout.session.completed,customer.subscription.deleted), and that its signing secret is an environment variable, not in code. - Confirm what should unlock after payment and where that's stored in the database.
3. Run the scenarios
Use Stripe's published test card numbers (from Stripe's docs) to run each one through the app's checkout. Use the preview link or run the app locally:
| Scenario | Expect | Result |
| Successful payment | Unlocks the right thing, receipt email arrives | |
| Card declined | Clear error, nothing unlocks | |
| Card needs extra authentication (3D Secure) | Challenge appears, then succeeds | |
| Refund (from the Stripe dashboard or connector) | Access removed if that's the rule | |
| Subscription cancelled (if subscriptions) | Access ends at the right time |
For each, check the app and the database actually changed, not just that Stripe says it worked. Use the Stripe connector to confirm each payment, refund and webhook event on Stripe's side.
If you can't use the checkout yourself (for example in a normal chat rather than the Code tab), give them a short numbered list of exactly what to click and ask them to report back or send screenshots. Never mark a step passed without seeing the result.
4. Check the emails
If Resend (or another email service) is connected, confirm the receipt and welcome emails were sent, which address they came from, and that the sending domain is verified. Flag anything that would land in spam (an unverified domain, or sending from a free email address).
5. Report
Fill in the table with ✓ or ✗ and a plain-English note for each failure: what happened and the likely fix. Offer to fix on a branch.
6. Before going live
List what must change for real payments: live API keys in Vercel (they add them; never in chat or code), a live webhook endpoint and its new signing secret, and live prices. Remind them to check Stripe's current fees for their country.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.