payment-development

Implement standardized payment adapters for Taiwan providers with unified interfaces.

6|3|Updated Apr 8, 2022
One-click install
npx skills add https://github.com/Rytass/Utils --skill payment-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payment-development
Source: https://github.com/Rytass/Utils/tree/main/.claude/skills/payment-development
Command: npx skills add https://github.com/Rytass/Utils --skill payment-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured blueprint for building standardized payment adapters, unifying core interfaces and lifecycle patterns to accelerate integration with Taiwan-based payment providers.

Core Features & Use Cases

  • Standardized Gateway, Order, and BindCard interfaces to support multiple providers with a single implementation model.
  • Guided adapter scaffolding that covers TypeScript typings, event-driven lifecycle, and provider-specific configuration.
  • Use Case: When a new provider needs to be integrated, follow this skill to quickly scaffold an adapter that adheres to the shared contracts and security practices.

Quick Start

Install and reference the base package, then scaffold a new adapter following the CREATE-ADAPTER.md guidance to implement the gateway, order, and optional bind-card components.

Frequently Asked Questions about payment-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a payment adapter for Taiwan providers using TypeScript?

To build a payment adapter, follow the guided scaffolding to implement standardized gateway, order, and optional card-binding interfaces. It enforces TypeScript base typings, event-driven lifecycle, and provider-specific configuration for secure, maintainable integration.

What is a unified payment gateway and how does it handle multiple channels?

A unified payment gateway provides a single API to route transactions across multiple channels. It standardizes order and bind-card interfaces so you can integrate new Taiwan providers without rewriting core logic.

How do I scaffold a new event-driven payment adapter?

Scaffold a new adapter by referencing the base package and following the CREATE-ADAPTER guidance. Implement gateway, order, and bind-card components while adhering to event-driven lifecycle and base typings.

Can I use this to integrate multiple Taiwan payment providers with a single implementation?

Yes, this provides standardized gateway, order, and bind-card interfaces to support multiple Taiwan providers with a single implementation model. It ensures scalable integration across different channels.

What's the best way to standardize payment integration architecture across different gateways?

The best way is to use a unified API with standardized gateway, order, and bind-card interfaces. This enforces adherence to base typings and event-driven lifecycle, ensuring secure, maintainable adapters across providers.

Do I need TypeScript to use this payment adapter scaffolding?

Yes, TypeScript is required. The adapter implementation requires adherence to base typings and event-driven lifecycle patterns to ensure secure, maintainable adapters across Taiwan providers.