Design Reliable Payment Systems
Payment teams need consistent designs for transactions, channels, reconciliation, security, and failure handling. This skill provides structured guidance, examples, and review checklists.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "payment-engineer" from https://skillstore.io/skills/zl2023github-payment-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-payment-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "payment-engineer". Design the state flow for card payments with asynchronous callbacks.
Expected outcome:
Using "payment-engineer". Create a checklist for a customer charged while the order remains unpaid.
Expected outcome:
Using "payment-engineer". Summarize minimum controls for storing payment data.
Expected outcome:
Do not store card verification values or plaintext card data. Encrypt permitted data, protect keys with an HSM, use TLS, and mask logs.
All 20 static findings are false positives caused by Markdown fences, inline code formatting, or multilingual text. The skill is a documentation-only payment engineering guide with no executable commands, system reconnaissance, obfuscation, or prompt injection.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/zl2023github-payment-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zl2023github-payment-engineer?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/zl2023github-payment-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-payment-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/zl2023github-payment-engineer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>zl2023github. (2026). payment-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-payment-engineer/audits/4@techreport{zl2023github-zl2023github-payment-engineer-2026,
author = {zl2023github},
title = {payment-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-payment-engineer/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "payment-engineer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/zl2023github-payment-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-payment-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Create an architecture outline covering transaction intake, accounting, settlement, channel routing, availability, and consistency.
Check idempotency, state transitions, callbacks, distributed transactions, and fallback behavior before implementation.
Build a focused checklist for missing payments, duplicate charges, or reconciliation mismatches.
Outline a payment flow for [payment method]. Include request validation, idempotency, channel submission, callbacks, state transitions, and customer responses.
Design a channel adapter for [provider] using [language]. Cover payment, query, refund, callback verification, error mapping, and retry boundaries.
Create a reconciliation plan for [business]. Define matching keys, time windows, fees, refunds, currencies, exception categories, and operational resolution steps.
Review this payment architecture: [architecture details]. Identify consistency, security, capacity, observability, recovery, and compliance gaps. Prioritize recommendations by financial impact.
Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
2 downloads · 2 views
File structure
📄 SKILL.md
Diagnose and Improve Full-Stack Performance
Full-stack teams often lack a repeatable way to measure performance and locate bottlenecks. This skill provides testing workflows, diagnostic commands, optimization guidance, and report structures.
Build and Optimize Search Systems
Search teams need reliable guidance across indexing, ranking, semantic retrieval, and evaluation. This skill provides practical workflows and examples for building and improving search systems.
Build Reliable Business Intelligence Analysis
Business teams often lack consistent metrics and repeatable analysis workflows. This skill guides SQL, Python, dashboards, experiments, and automated reporting from requirements to delivery.
Evaluate Technology Choices with Clear Tradeoffs
Technology choices often hide tradeoffs across performance, cost, reliability, operations, and team readiness. This skill compares candidates, recommends an option, and defines proof-of-concept checks.
Generate Clear Software Architecture Documents
Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.
Build Reliable Data Pipelines and Warehouses
Data teams need dependable pipelines across fragmented platforms. This skill designs implementation-ready batch, streaming, modeling, orchestration, and quality workflows.
Build Reliable Backend APIs
by alirezarezvani
Backend projects often need consistent planning across APIs, databases, security, and deployment. This skill gives Claude, Codex, and Claude Code structured backend guidance with simple helper scripts and references.
Design Software Architectures with Senior Guidance
by davila7
Architecture choices are hard to compare across product, scale, security, and team constraints. This skill gives structured guidance, references, and helper scripts for clearer decisions.
Build WooCommerce Stores with Guided Workflows
by sickn33
WooCommerce builds require coordinated setup, payment, shipping, design, and testing work. This skill gives Claude, Codex, and Claude Code a phased workflow for store delivery.
Build Secure WordPress Plugins
by sickn33
WordPress plugins need secure architecture, hooks, admin pages, APIs, data handling, and tests. This skill guides a phased workflow from setup through review.
Build Credit Purchase and Balance Flows
by AayushBaniya2006
Credit features can fail when pricing, balances, and UI flows become inconsistent. This skill guides credit types, purchase flows, balance displays, and allocation helpers.
Review Code with Sentry Engineering Practices
by davila7
Pull requests can hide defects, security gaps, performance regressions, and weak tests. This skill applies a structured Sentry-inspired checklist and produces prioritized, actionable review feedback.