SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Business · Backend / AGENT SKILL
decline-analysis
0
Model payment transaction lifecycles, including money movement, risk, reconciliation, and provider differences.
Use when work must model the complete transaction lifecycle and explicitly address money movement, tokenization, risk, reconciliation, funding, support, and provider differences.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# Decline Analysis ## Purpose Produce a reviewable decline analysis outcome that is grounded in repository evidence and explicit about uncertainty. ## When to Use Use for planning, design, implementation review, migration, troubleshooting, or documentation where the task must model the complete transaction lifecycle and explicitly address money movement, tokenization, risk, reconciliation, funding, support, and provider differences. ## Inputs - Goal, audience, scope, constraints, and success criteria. - Relevant source files, contracts, examples, logs, and decisions. - Known risks, assumptions, dependencies, and approval boundaries. ## Process 1. Restate the intended outcome and affected audiences. 2. Inventory exact current behavior and source-backed constraints. 3. Apply the relevant APT principles and identify missing evidence. 4. Compare viable options, including compatibility and operational effects. 5. Produce the required artifacts: lifecycle states, amount and currency rules, idempotency, provider mapping, token boundaries, settlement/funding flow, reconciliation, disputes, and support identifiers. 6. Review invented provider behavior, double processing, confused authorization and settlement, sensitive-data exposure, incomplete reversals, and weak reconciliation; separate blockers, recommendations, and open questions. ## Outputs A concise recommendation, evidence map, required changes, risks, validation plan, support/documentation impact, and approval status. ## Quality Bar The output is practical, source-backed, audience-aware, testable, reversible where possible, and does not state assumptions as facts. ## Domain Checklist - Treat **Decline Analysis** as an explicit decision with defined scope, evidence, owner, and validation. - Separate issuer, processor, validation, risk, and configuration causes and provide safe next actions. - State what is verified, what is assumed, and what requires specialist or human approval. ## Required Reading Read the canonical Payments principle hub, the closest enforceable standard, the applicable checklist, and exact target-repository evidence. ## References - [Payments principles](../../../principles/payments/README.md) - [Templates](../../../templates/README.md) - [Agents](../../../agents/README.md)
Skill folder
Files included alongside SKILL.md in the publisher’s repository.