bagisto-payment-method-development
Use when creating or changing a Bagisto payment method — a payment class, the payment methods config, the checkout redirect and callback flow, or integrating a gateway such as Stripe or PayPal. Trigger phrases include "payment", "payment method", "payment gateway", "Stripe", "PayPal", "Razorpay", "checkout payment", "redirect", "webhook".
Works with
--- name: bagisto-payment-method-development description: Use when creating or changing a Bagisto payment method — a payment class, the payment methods config, the checkout redirect and callback flow, or integrating a gateway such as Stripe or PayPal. Trigger phrases include "payment", "payment method", "payment gateway", "Stripe", "PayPal", "Razorpay", "checkout payment", "redirect", "webhook". license: MIT --- # Payment Method Development ## Overview Creating custom payment methods in Bagisto allows you to integrate any payment gateway or processor with your store. Whether you need local payment methods, cryptocurrency payments, or specialized payment flows, custom payment methods provide the flexibility your business requires. For our tutorial, we'll create a **Custom Stripe Payment** method that demonstrates all the essential concepts you need to build any type of payment solution. ## When to Apply Activate this skill when: - Creating new payment methods - Integrating payment gateways (Stripe, PayPal, Razorpay, etc.) - Adding payment options to checkout - Modifying existing payment configurations - Creating admin configuration for payment methods ## Bagisto Payment Architecture Bagisto's payment system is built around a flexible method-based architecture that separates configuration from business logic. ### Core Components | Component | Purpose | Location | |-----------|---------|----------| | **Payment Methods Configuration** | Defines payment method properties | `Config/payment-methods.php` | | **Payment Classes** | Contains payment processing logic | `Payment/ClassName.php` | | **System Configuration** | Admin interface forms | `Config/system.php` | | **Service Provider** | Registers payment method | `Providers/ServiceProvider.php` | ### Key Features - **Flexible Payment Processing**: Support for redirects, APIs, webhooks, or custom flows. - **Configuration Management**: Admin-friendly settings interface. - **Multi-channel Support**: Different settings per sales channel. - **Security Ready**: Built-in CSRF protection and secure handling. - **Extensible Architecture**: Easy integration with third-party gateways. ## Reference files — load only what the current task needs | File | Load when | |---|---| | [implementation.md](implementation.md) | Building a payment method — the step-by-step guide | | [payment-api.md](payment-api.md) | The base payment class and the methods to override | | [reference.md](reference.md) | Built-in methods, best practices, a complex integration example, package layout, testing, pitfalls | **REQUIRED SUB-SKILL:** Use bagisto-change-verification before calling any change done.
More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

