Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Integrate payments with provider selection, checkout flows, subscription billing, and security best practices.
Integrate payments with provider selection, checkout flows, subscription billing, and security best practices.
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.
ContextLoadChoosing Stripe vs Paddle vs LemonSqueezyproviders.mdImplementing checkout, webhooks, refundsintegration.mdSubscription billing, trials, upgradessubscriptions.mdPCI compliance, fraud preventionsecurity.md
Never store card data. Use provider-hosted checkout or tokenization. PCI compliance burden explodes the moment raw card numbers touch your server. Webhooks are truth. Client-side success callbacks lie. A payment succeeded only when your webhook confirms it. Design for webhook-first verification. Test mode exists for a reason. Use test cards, simulate failures, verify webhook handling. Production surprises cost real money and real customers. Pricing psychology: $9.99/mo feels cheaper than $120/year, but annual retention is 2-3x higher. Default to annual with monthly option, not the reverse.
NeedRecommendationUS/global B2CStripe (best docs, widest coverage)SaaS selling to EU (VAT headache)Paddle, LemonSqueezy (merchant of record)Simple product, no dev resourcesGumroad, Lemonsqueezy hostedMarketplace with splitsStripe ConnectHigh-risk or adultSpecialized processors (CCBill, Epoch) See providers.md for detailed comparison.
Before going live: Webhook endpoint secured and verified Idempotency keys on all charges Failure states handled (declined, expired, insufficient) Receipts and invoices configured Refund flow tested Subscription lifecycle events handled (upgrade, downgrade, cancel) Currency handling explicit (store in cents/smallest unit)
Storing CVV anywhere, ever → Instant PCI violation Trusting client-side payment confirmation → Fraud vector No retry logic for failed webhooks → Lost transactions Hardcoding prices in frontend → Easy manipulation Missing cancel_at_period_end handling → Angry customers
SituationReferenceEvaluating payment processorsproviders.mdBuilding checkout, handling webhooksintegration.mdRecurring billing, metering, trialssubscriptions.mdFraud, PCI, chargebackssecurity.md
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.