stripe-best-practices
Build Modern Stripe Integrations
Stripe offers several APIs, and outdated choices can create migration or payment risks. This skill recommends current integration patterns for payments, subscriptions, and platforms.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "stripe-best-practices" from https://skillstore.io/skills/anthropics-stripe-best-practices.md and its manifest at https://skillstore.io/api/skills/anthropics-stripe-best-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "stripe-best-practices". We need a hosted page for one-time payments and automatic payment method selection.
Expected outcome:
- Use Stripe-hosted Checkout with Checkout Sessions.
- Enable dynamic payment methods in the Dashboard.
- Validate the design with Stripe's integration options and go-live checklist.
Using "stripe-best-practices". Our application saves cards through Sources and creates Charges later.
Expected outcome:
- Migrate saved payment methods to Setup Intents.
- Use Payment Intents for off-session payments.
- Plan migration from Charges and Sources using official Stripe guidance.
Using "stripe-best-practices". A marketplace needs the platform to accept liability for connected account negative balances.
Expected outcome:
Prefer destination charges, then define merchant-of-record behavior with on_behalf_of and current Connect controller properties.
Security Audit
SafeAll 12 hardcoded URLs are references to official Stripe documentation and do not perform network requests. The reconnaissance alert misclassifies guidance that prohibits deprecated APIs. No malicious intent or prompt injection was found.
Risk Factors
๐ Network access (12)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/anthropics-stripe-best-practices/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/anthropics-stripe-best-practices?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/anthropics-stripe-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/anthropics-stripe-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/anthropics-stripe-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
anthropics. (2026). stripe-best-practices security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/anthropics-stripe-best-practices/audits/8BibTeX citation
@techreport{anthropics-anthropics-stripe-best-practices-2026,
author = {anthropics},
title = {stripe-best-practices security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/anthropics-stripe-best-practices/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "stripe-best-practices security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "anthropics"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/anthropics-stripe-best-practices/audits/8"
identifiers:
- type: other
value: "skillstore:anthropics-stripe-best-practices:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
anthropics-stripe-best-practices
2026-08-21
stripe-stripe-best-practices
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Choose a Payment Architecture
Select Checkout Sessions, Payment Intents, or Billing for a new product and understand the recommended frontend surface.
Modernize a Legacy Integration
Identify deprecated Stripe APIs and map them to supported payment, setup, or checkout alternatives.
Design Platform Fund Flows
Compare direct and destination charges, liability implications, merchant-of-record settings, and current Connect account controls.
Try These Prompts
Recommend a Stripe integration for [product] with [one-time or recurring] payments. Compare hosted Checkout, embedded Checkout, and Payment Element.
Review this Stripe design: [design summary]. Identify outdated APIs, recommend supported replacements, and explain each change.
Design a Stripe Billing approach for [business model]. Cover checkout, subscription lifecycle, payment method collection, and relevant official documentation.
Evaluate Connect fund flows for [platform model]. Compare direct and destination charges, liability, merchant of record, controller properties, and capabilities.
Best Practices
- Confirm requirements before choosing among Checkout Sessions, Payment Intents, Billing, and Connect.
- Use the latest compatible Stripe API and SDK versions unless an existing system requires another version.
- Validate production readiness against current official Stripe documentation and the go-live checklist.
Avoid
- Do not recommend Charges, Sources, legacy Card Element, or outdated Connect account labels for new integrations.
- Do not collect or transmit raw card data without validated PCI eligibility and controls.
- Do not mix Connect charge types or hardcode payment methods without a documented requirement.
Frequently Asked Questions
Does this skill write Stripe integration code?
Which payment API does it prefer?
Can it help migrate from the Charges API?
Does it cover recurring revenue?
Does it provide Connect architecture guidance?
Does it guarantee PCI compliance?
Developer Details
Author
anthropicsLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
89edfdc710d0846129dcee6a929477b04f08052c
Maintenance freshness
7/24/2026
Usage
5 downloads ยท 195 views
File structure
๐ SKILL.md