afrexai-stripe-productionProvides best practices and code patterns for building, scaling, and operating production Stripe payment systems from checkout to enterprise billing.
Install via ClawdBot CLI:
clawdbot install 1kalin/afrexai-stripe-productionGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://afrexai-cto.github.io/context-packs/Audited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
A new software-as-a-service company needs to quickly implement a subscription billing system with minimal development overhead. They prioritize a fast launch using Stripe Checkout for hosted payment pages, ensuring PCI compliance and handling recurring payments for monthly/annual plans.
An online retailer requires a branded, embedded payment experience to maintain UX consistency across their website. They use Stripe's Payment Element for custom UI control, integrating one-time purchases and managing customer data securely without handling raw card details.
A cloud service provider charges customers based on metered usage, such as API calls or compute hours. They implement Stripe's metered billing with webhooks to track usage records, automate invoicing, and scale billing logic as customer consumption grows.
A marketplace platform needs to handle payments between buyers and multiple sellers, including split payments and commission tracking. They use Stripe's Direct API with Connect for platform integrations, managing complex payout workflows while ensuring idempotency and webhook reliability.
A large enterprise requires a scalable billing solution for tiered pricing, per-seat subscriptions, and hybrid models with base fees plus overages. They leverage Stripe's advanced features like tax automation, customer portals for self-service, and monitoring for payment failures at high volume.
This model involves charging customers a fixed amount at regular intervals, such as monthly or annually, ideal for SaaS products with predictable pricing. It uses Stripe Subscriptions to automate billing cycles, handle renewals, and manage customer lifecycle events like upgrades or cancellations.
Customers are billed based on actual consumption, such as per API call, storage used, or compute time. It employs Stripe's metered billing to track usage records, calculate variable charges, and generate invoices that reflect dynamic usage patterns for services like cloud infrastructure.
Combines a base subscription fee with additional charges for overage or usage beyond included limits, common in services with tiered plans. It uses Stripe's subscription features alongside usage records to manage both fixed and variable components, enabling flexible pricing strategies.
💬 Integration Tip
Always pin the Stripe API version to avoid breaking changes, and use webhooks as the source of truth for payment status updates rather than relying on client-side redirects.
Scored Apr 19, 2026
Comprehensive portfolio analysis using Alpaca MCP Server integration to fetch holdings and positions, then analyze asset allocation, risk metrics, individual stock positions, diversification, and generate rebalancing recommendations. Use when user requests portfolio review, position analysis, risk assessment, performance evaluation, or rebalancing suggestions for their brokerage account.
Manage Razorpay customers, orders, invoices, payment links, refunds, payouts, and payment operations via the Razorpay API. Use when users want to inspect or...
微信支付医保支付(移动医保支付2.0)接入解决方案,覆盖医保自费混合下单、订单查询、医保退款通知、医保收款回调全链路,提供选型/示例代码/业务速查/质量评估/排障五大能力。Use when user mentions "医保支付", "移动医保支付2.0", "医保自费混合", "医保电子凭证", "医保混合收款...
Track agent spending, set budgets and alerts, and prevent surprise bills. Use when the agent needs to log expenses, check remaining budget, set spending limi...
Greek-language OCR using Tesseract. Processes scanned invoices, receipts, and government documents. Local processing, no cloud APIs.
Greek financial statement generation — P&L, balance sheets, VAT summaries with EGLS integration. Completeness gates prevent partial outputs.