Hardgraph

SKILL PROCEDURE

Stripe

Payments platform for accepting money online, running subscriptions and invoicing, and paying out to connected accounts. Use when integrating Stripe — Checkout, Payment Intents, webhooks, Connect, Billing, Elements, Tax — choosing between its APIs, or identifying which surfaces are deprecated. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.

stripecheckoutbillingconnectwebhooks
BEGINNER GUIDE

Understand Stripe before using it

WHAT IT COVERS

Payments platform for accepting money online, running subscriptions and invoicing, and paying out to connected accounts. Use when integrating Stripe — Checkout, Payment Intents, webhooks, Connect, Billing, Elements, Tax — choosing between its APIs, or identifying which surfaces are deprecated. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.

START HERE WHEN

Your work repeatedly involves one or more of these concepts. Open the full procedure below when the current task matches them.

stripecheckoutbillingconnectwebhooks

Compare related skills

SKILLCATEGORYSHARED CONCEPTSEXPLANATION
StripePaymentsCurrent skillPayments platform for accepting money online, running subscriptions and invoicing, and paying out to connected accounts. Use when integrating Stripe — Checkout, Payment Intents, webhooks, Connect, Billing, Elements, Tax — choosing between its APIs, or identifying which surfaces are deprecated. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.
PayPalPayments
checkoutwebhooks
Use when integrating PayPal payments, choosing between PayPal products, or verifying PayPal API details that drift — webhook event names, SDK parameters, version pins. Covers Orders v2 checkout, subscriptions, payouts, disputes, and the Business versus Platforms split. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.
PolarPayments
billingcheckout
Use when integrating Polar for software billing — checkout, subscriptions, usage-based billing, benefits (license keys, file downloads, Discord/GitHub access), payouts, or webhooks — or when deciding whether a merchant of record is the right model versus running your own payment-processor integration. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.
n8nAutomation
webhooks
n8n — a source-available workflow automation platform (self-hosted n8n or n8n Cloud) for connecting APIs and services through visual node graphs with optional JavaScript/Python code. Use when building integrations and automations, designing a workflow of triggers and nodes, using expressions to map data between nodes, working with the HTTP Request node and credentials, building custom nodes or the Advanced AI/agent nodes, calling n8n from webhooks or external code, deploying self-hosted n8n (Docker), or using the REST API and public/internal endpoints. Published by HardGraph, a curated graph of provenance-backed knowledge for AI agents.

Stripe

What is HardGraph? HardGraph publishes curated, provenance-backed agent skills grounded in reproducible vendor documentation.

Stripe is the payments platform for accepting money online (cards, wallets, bank debits, BNPL) plus billing and subscriptions, marketplace payouts (Connect), tax, invoicing, and treasury.

Instructions for AI agents

Reproduced from Stripe's llms.txt. These steer toward current APIs and away from deprecated ones.

  1. Resolve the current API/SDK version rather than recalling one. Check the registry — npm view stripe version, or pypi.org/project/stripe. A version remembered from training data will be wrong.
  2. Prefer the Checkout Sessions API. Do not recommend the deprecated Charges API unless there is no alternative.
  3. Never recommend the legacy Card Element. Use the Payment Element.
  4. Avoid deprecated endpoints — Sources, Tokens, Charges.
  5. Use the Accounts v2 API (/v2/core/accounts) for new Connect integrations, not v1.
  6. Enable dynamic payment methods rather than hardcoding payment_method_types.
  7. Direct users to migration guides when they ask about legacy approaches.
  8. For billing and subscriptions, use the Billing APIs plus Checkout rather than raw PaymentIntents.

Core surfaces

| Area | Start here | Notes | | --- | --- | --- | | Checkout | checkout/quickstart | Stripe-hosted payment page; preferred starting point | | Payments | payments/quickstart | Payment Intents API, custom flows | | Webhooks | webhooks | Event delivery and signature verification | | Connect | connect | Marketplaces and platforms; use Accounts v2 | | Billing | billing/quickstart | Subscriptions, invoicing, pricing | | Elements | payments/payment-element | Prebuilt UI for custom checkout | | Testing | testing | Sandbox behaviour and test cards | | Versioning | upgrades | Date-pinned releases and breaking changes |

Versioning

The API is versioned by a date pin (Stripe-Version header, or the account default). Breaking changes ship only in major releases. SDK versions move independently of the API version — resolve the current SDK from the package registry before pinning, rather than asserting a number.

References

Hardgraph / curated knowledge for agents.

STATIC EXPORT · CANONICAL SOURCE