Payments

What This Skill Does

The Payments skill for OpenClaw AI provides an expert-level framework for integrating modern payment infrastructures into software projects. It serves as a comprehensive navigator for developers to handle complex financial transactions, subscription management, and regulatory compliance. By codifying best practices such as merchant-of-record (MoR) selection, webhook-first verification, and PCI-compliant handling, it eliminates common failure points during the implementation phase of checkout flows.

Installation

To integrate this skill into your environment, use the OpenClaw CLI: clawhub install openclaw/skills/skills/ivangdavila/payments

Use Cases

This skill is designed for SaaS founders, backend engineers, and product managers who need to build or audit payment systems. Use it when you are selecting a payment provider, such as deciding between Stripe's flexibility or the tax-compliance ease of Paddle. It is also essential for developers mapping out subscription lifecycle events, setting up idempotent webhook handlers, or designing secure checkout interfaces that adhere to global security standards like PCI-DSS.

Example Prompts

1. "OpenClaw, I am building a B2B SaaS for the EU market. Should I use Stripe or LemonSqueezy, and what are the specific tax implications for my setup?"
2. "Can you help me design a robust webhook verification logic for Stripe that ensures my server doesn't process duplicate events?"
3. "I need a checklist for my production readiness review regarding subscription billing, specifically focusing on how to handle credit card expiration and churn reduction."

Tips & Limitations

The most critical rule to remember is that the client-side is for UI display only; never trust browser-side callbacks as confirmation of payment. Always verify transactions through server-side webhooks. Furthermore, always represent prices as integers in the smallest currency unit (e.g., cents for USD) to avoid floating-point errors. Note that while this skill provides architectural guidance and best practices, it does not execute code directly; it relies on the developer to implement the provided recommendations within their own backend environment. Always test your workflows in sandbox environments before deploying to production, especially when handling subscription lifecycle transitions.