payments-integration

Design production payment integrations with idempotent settlement and provider verification.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/miracleonyenma/skills --skill payments-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: payments-integration
Source: https://github.com/miracleonyenma/skills/tree/main/payments-integration
Command: npx skills add https://github.com/miracleonyenma/skills --skill payments-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you build reliable payment flows that do not break under redirects, webhook retries, provider differences, or settlement races. It is designed to prevent the common production mistakes of trusting callback URLs, double-crediting transactions, or losing reconciliation state across multiple payment rails.

Core Features & Use Cases

  • Multi-provider checkout orchestration: Unified handling for 100Pay, Paystack, Flutterwave, and wallet-based rails in one payment architecture.
  • Idempotent settlement and verification: Supports callback-as-signal patterns, provider verification, webhook deduplication, and exactly-once domain side effects.
  • Production scenarios: Wallet top-ups, number rental deposits, rental extensions, VTU airtime/data purchases, and subscription checkout flows in Next.js and Express apps.

Quick Start

Use this Skill to design or debug a payment flow, then map the provider, reference, verification, webhook, and settlement steps to your app so the transaction resolves exactly once.

Frequently Asked Questions about payments-integration

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

FAQPage Schema
How do I prevent double-crediting transactions during webhook settlement?

Prevent double-crediting during webhook settlement by creating idempotent pending transactions and applying race-safe settlement logic. Treat callbacks as signals, verify the final state server-side, and deduplicate webhooks before updating wallet ledgers.

What is the best way to handle payment verification across multiple providers like Paystack and Flutterwave?

Handle multi-provider verification by using a unified checkout orchestration architecture that applies provider-specific signature verification and server-authoritative references. This ensures transaction states resolve exactly once across different rails.

How do I design a Next.js checkout flow for wallet top-ups that survives redirect failures?

Design checkout flows for wallet top-ups by initiating server-authoritative references, handling callback redirects as signals, and verifying the actual transaction state. This prevents losing reconciliation state if redirects fail or webhooks retry.

Does this payment integration approach support subscription checkout and rental deposits?

Yes, this payment integration approach supports subscription checkout, rental deposits, and extensions. It coordinates checkout initiation, verification, and webhook settlement to ensure exactly-once domain side effects for these specific production scenarios.

Why do I need server-authoritative references for callback handling?

Server-authoritative references are needed for callback handling to prevent trusting callback URLs directly. By verifying the provider server-side and using idempotent transactions, you avoid settlement bugs and double-processing from forged or retried requests.