payment-engineer
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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「payment-engineer」を使用しています。 Design the state flow for card payments with asynchronous callbacks.
期待される結果:
- Start in Pending, then move to Processing after validated channel submission.
- Accept verified callbacks for Success or Failed transitions.
- Use a separate Refunding transition before Refunded.
- Reject repeated transitions through an idempotency key and state validation.
「payment-engineer」を使用しています。 Create a checklist for a customer charged while the order remains unpaid.
期待される結果:
- Confirm the provider transaction and callback delivery status.
- Verify callback signature validation and idempotency records.
- Inspect callback retries and transaction state transitions.
- Reconcile the provider record before any manual correction.
「payment-engineer」を使用しています。 Summarize minimum controls for storing payment data.
期待される結果:
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.
リスク要因
⚙️ 外部コマンド (18)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/zl2023github-payment-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/zl2023github-payment-engineer?utm_source=security_passport_badge)HTMLバッジ
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
zl2023github. (2026). payment-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-payment-engineer/audits/4BibTeX形式の引用
@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}
}CITATION.cff
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"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Plan a payment platform
Create an architecture outline covering transaction intake, accounting, settlement, channel routing, availability, and consistency.
Review payment reliability
Check idempotency, state transitions, callbacks, distributed transactions, and fallback behavior before implementation.
Investigate transaction differences
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.
ベストプラクティス
- Provide business volume, payment methods, currencies, regions, and consistency requirements.
- Validate generated designs against current provider contracts, compliance obligations, and internal security standards.
- Test idempotency, callback retries, partial failures, reconciliation exceptions, and recovery procedures before release.
回避
- Do not use illustrative code directly in production without validation, error handling, tests, and security review.
- Do not treat distributed locks as the only protection against duplicate financial operations.
- Do not log credentials, signatures, full card data, or unmasked personal information.
よくある質問
Does this skill process real payments?
Which programming languages does it cover?
Which payment providers are discussed?
Can it help with reconciliation?
Does it guarantee PCI-DSS compliance?
What information improves the result?
開発者情報
作成者
zl2023githubライセンス
MIT
Skillstore リビジョン
r2
バージョンに関する注意
作者はバージョンを宣言していません。
参照
88a8e9a07f4c54ab105c1c41b6267c287146b07b
メンテナンスの新しさ
2026/7/26
利用状況
2 ダウンロード · 2 閲覧
ファイル構成
📄 SKILL.md