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.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "payment-engineer". Design the state flow for card payments with asynchronous callbacks.
Resultado esperado:
- 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.
Usando "payment-engineer". Create a checklist for a customer charged while the order remains unpaid.
Resultado esperado:
- 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.
Usando "payment-engineer". Summarize minimum controls for storing payment data.
Resultado esperado:
Do not store card verification values or plaintext card data. Encrypt permitted data, protect keys with an HSM, use TLS, and mask logs.
Auditoría de seguridad
SeguroAll 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.
Factores de riesgo
⚙️ Comandos externos (18)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/zl2023github-payment-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/zl2023github-payment-engineer?utm_source=security_passport_badge)Insignia 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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita APA
zl2023github. (2026). payment-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-payment-engineer/audits/4Cita BibTeX
@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"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
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.
Prueba estos prompts
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.
Mejores prácticas
- 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.
Evitar
- 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.
Preguntas frecuentes
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?
Detalles del desarrollador
Autor
zl2023githubLicencia
MIT
Revisión de Skillstore
r2
Aviso de versión
El autor no declaró una versión.
Repositorio
https://github.com/zl2023github/software-engineer-skills/tree/main/software-engineering/payment-engineerRef.
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Actualidad del mantenimiento
26/7/2026
Uso
2 descargas · 2 vistas
Estructura de archivos
📄 SKILL.md