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.你的智能体仍应展示其计划，并按安全策略请求必要确认。
Agent 可读资源
当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。
测试它
正在使用“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.
风险因素
分享与引用此报告
分享版本化评估报告、中性徽章、嵌入卡片和引用。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