payment-integration

Name: payment-integration
Availability: InStock
Author: Tien

Manage multi-provider payment workflows with webhook deduplication and order synchronization.

Updated Feb 25, 2025

Search Tags:#automation #cross-platform #payment #webhooks #order management #refund handling

Ready to run

npx skills add https://github.com/VuNguyenVietTien/task-scheduler --skill payment-integration-vunguyenviettien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: payment-integration
Source: https://github.com/VuNguyenVietTien/task-scheduler/tree/main/.opencode/skills/payment-integration
Command: npx skills add https://github.com/VuNguyenVietTien/task-scheduler --skill payment-integration-vunguyenviettien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires drizzle-orm, crypto, fetch, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill centralizes management of various payment gateways, webhooks, and order workflows, enabling seamless integration across multiple platforms.

Core Features & Use Cases

Multi-Platform Support: Integrates SePay, Polar, Stripe, Paddle, and Creem.io for comprehensive payment management.
Webhook Deduplication & Idempotency: Ensures safe processing of duplicate notifications across different providers.
Order & Refund Handling: Automates order creation, status updates, and refunds with cross-provider synchronization.
Use Case: For SaaS or marketplace platforms, automate the entire payment, subscription, and licensing lifecycle with minimal manual intervention.

Quick Start

Run the webhook server to listen for payment notifications from all integrated platforms and process them automatically to update orders, licenses, and revenue data.

Frequently Asked Questions about payment-integration

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

FAQPage Schema

How do I handle multi-platform payment webhooks and prevent duplicate processing?▼

Payment webhook handling relies on event deduplication and idempotency to safely filter duplicate notifications across providers like Stripe, Paddle, and SePay. This prevents duplicate order updates and billing errors automatically.

What is the best way to automate order and refund handling across multiple payment gateways?▼

Automating order and refund handling across multiple payment gateways requires a centralized workflow that coordinates cross-provider synchronization. This automatically updates order statuses, processes refunds, and manages subscriptions with minimal manual intervention.

Does this payment integration support Stripe, Paddle, and Creem.io for SaaS platforms?▼

Yes, this payment integration supports Stripe, Paddle, Creem.io, SePay, and Polar for SaaS and marketplace platforms. It provides comprehensive payment management, subscription automation, and licensing lifecycle coordination across these specific gateways.

How do I coordinate cross-platform payment synchronization using drizzle-orm?▼

Cross-platform payment synchronization using drizzle-orm coordinates event processing, order updates, and refund handling across multiple gateways. It ensures production reliability by automating workflows and managing data consistency across different payment providers.

Why do duplicate webhook notifications cause payment processing errors and how to fix it?▼

Duplicate webhook notifications cause payment processing errors by triggering repeated order updates or billing actions. Implementing webhook deduplication and idempotency mechanisms ensures safe processing of duplicate notifications, preventing these duplicate execution errors.

Can I use cross-platform automation for marketplace payment workflows and licensing?▼

Yes, you can use cross-platform automation for marketplace payment workflows and licensing. It automates the entire payment, subscription, and licensing lifecycle across integrated gateways, coordinating revenue data updates with minimal manual intervention.