Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Best practices for building Stripe payment integrations
Best practices for building Stripe payment integrations
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Best practices for building Stripe payment integrations
stripe, payment, checkout, subscription, billing
integrate payment processing handle subscriptions process credit cards
Charges API Sources API Card Element Payment Element in card-only mode Tokens API (unless specific need) mixing Connect charge types legacy Connect terms (Standard/Express/Custom)
latest API/SDK version (unless specified otherwise) advise PCI compliance proof for raw PAN handling use controller properties for Connect (not legacy terms)
Prefer CheckoutSessions over PaymentIntents when on-session payments Prefer Stripe-hosted Checkout over embedded Checkout when default choice Prefer embedded Checkout over Payment Element when more control needed Prefer dynamic payment methods over explicit payment_method_types when using Payment Element Prefer SetupIntents over Sources when saving payment methods Prefer Confirmation Tokens over createPaymentMethod/createToken when inspecting card before payment Prefer Billing APIs over raw PaymentIntents when subscriptions/recurring Prefer direct charges over destination charges when platform wants Stripe to take risk Prefer destination charges over direct charges when platform accepts liability
When user wants Charges API: advise migration to CheckoutSessions or PaymentIntents When user wants Card Element: advise migration to Payment Element When recurring revenue / subscription / SaaS: recommend Billing APIs + Checkout frontend When platform / marketplace / Connect: follow integration recommendations, use controller properties When migrating PAN data from another processor: point to migration process When render Payment Element before creating intent: use Confirmation Tokens
stripe:integration-options - primary integration design reference stripe:api-tour - API overview stripe:go-live - pre-launch checklist stripe:migration/charges - Charges to PaymentIntents migration stripe:migration/payment-element - Card Element to Payment Element migration stripe:billing/design-integration - subscription integration planning stripe:connect/recommendations - Connect charge type selection stripe:pan-import - PAN data migration Converted from UASP format (knowledge skill)
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.