implement-payment-flow

Orchestrate end-to-end payment flows across PSP and rail adapters with ledger posting.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-payment-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-payment-flow
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/skills/implement-payment-flow
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill implement-payment-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end payment flows across PSP adapters, rail adapters, and the double-entry ledger to ensure consistent, auditable transactions.

Core Features & Use Cases

  • End-to-end orchestration across PSPs, rails, and ledger with deterministic sequencing from initiation to posting.
  • Modular, hexagonal architecture using ports and adapters for PSPs (Stripe, Adyen, PayPal) and rails (SEPA, ACH, SWIFT) with ledger integration.
  • Resilience, compliance, and multi-currency support enabling production-grade payments with auditing and reconciliation.

Quick Start

Configure your platform to instantiate PSP and rail adapters and run a sample payment flow to validate end-to-end processing.

Frequently Asked Questions about implement-payment-flow

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

FAQPage Schema
How do I orchestrate end-to-end payment flows across PSPs and banking rails?

End-to-end payment flow orchestration coordinates PSP adapters, rail adapters, and the double-entry ledger using deterministic sequencing from initiation to posting. It applies modular, hexagonal architecture with ports and adapters for seamless transaction processing across multiple payment providers and rails.

What is the best way to integrate SEPA, SWIFT, and ACH rails with a double-entry ledger?

Integrating SEPA, SWIFT, and ACH rails with a double-entry ledger is best handled through modular rail adapters using a port-based architecture. This ensures balanced transaction lines, event-driven ordering, and ledger posting while supporting multi-currency transactions and auditing across different payment networks.

Can I use a hexagonal architecture for multi-currency payment initiation and settlement?

Yes, hexagonal architecture supports multi-currency payment initiation and settlement by using modular ports and adapters for PSPs like Stripe, Adyen, and PayPal. This design enables production-grade payments with resilience, compliance checks, and auditing across different currencies and transfer types.

How does payment reconciliation work across different PSP adapters and internal transfers?

Payment reconciliation across PSP adapters and internal transfers works through deterministic sequencing and event-driven ordering that coordinates settlement with ledger posting. The architecture applies balanced transaction lines and compliance checks to ensure auditable, consistent reconciliation across all payment scenarios.

Do I need modular adapters to handle payment approval and compliance checks?

Yes, modular adapters are required to handle payment approval and compliance checks effectively. A port-based architecture allows independent PSP and rail adapters to enforce compliance while maintaining resilience, multi-currency support, and full auditing throughout the initiation, approval, and settlement process.