Payment Network Compliance Assessment
Assess payment network compliance for "$ARGUMENTS". Evaluate Nacha ACH Operating Rules, card network requirements, and state money transmitter licensing obligations.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-payment-network","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-payment-network","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-payment-network","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run
/compliance-regulatory-landscape <project>first, or use--skip-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
references/assessment-template.mdfor output structure - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and control framework context
- Read
Nacha ACH Operating Rules:
- Assess authorization requirements (consumer and corporate, written/electronic/oral)
- Evaluate ACH processing procedures (origination, file formatting, settlement timelines)
- Review return handling procedures (return reason codes, timeframes, re-initiation rules)
- Assess risk management requirements (exposure limits, monitoring, ACH audit)
- Evaluate Nacha Third-Party Sender (TPS) registration and obligations if applicable
- Review WEB debit authorization and fraud detection requirements
- Assess compliance with Supplementary Fraud Detection Standards for WEB debits
Visa Core Rules and Product Rules:
- Assess compliance with Visa Core Rules and Visa Product and Service Rules for card programs
- Evaluate BIN sponsorship arrangement and registered agent/third-party agent status
- Review cardholder agreement and disclosure requirements
- Assess dispute resolution and chargeback management procedures
- Evaluate Visa Operating Regulations for program-specific requirements (prepaid, credit, debit)
- Review PCI DSS compliance requirements as mandated by Visa
Mastercard Standards and Rules:
- Assess compliance with Mastercard Standards (formerly Mastercard Rules)
- Evaluate registration requirements (Service Provider, Payment Facilitator, Staged Digital Wallet Operator)
- Review Mastercard Identity Check and Strong Customer Authentication requirements
- Assess chargeback and dispute management compliance
- Evaluate Mastercard program-specific requirements for applicable products
State money transmitter licensing:
- Determine which states require money transmitter licenses (MTL) based on business model
- Assess applicability of exemptions (bank exemption, agent of the payee, licensed entity agent)
- Review current licensing status across all required states
- Evaluate NMLS (Nationwide Multistate Licensing System) registration and filings
- Assess bonding, net worth, and permissible investment requirements per state
- Review state examination and reporting obligations (call reports, audited financials)
- Evaluate Uniform Money Services Act adoption in applicable states
Federal registration requirements:
- Assess Money Services Business (MSB) registration with FinCEN
- Evaluate biennial renewal and update filing compliance
- Review state-level MSB registration requirements where applicable
- Assess compliance with MSB-specific BSA/AML program requirements
Write the artifact to
.singularskills/compliance/<project>/01-assess/payment-network.mdfollowing the assessment template structure with:- ACH Compliance — Nacha rule adherence, authorization, returns, and risk management
- Visa Compliance — Core Rules adherence, registration, and program requirements
- Mastercard Compliance — Standards adherence, registration, and program requirements
- State Licensing — MTL coverage map, exemption analysis, and gap identification
- Federal Registration — FinCEN MSB status and BSA/AML program
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The payment network assessment written to .singularskills/compliance/<project>/01-assess/payment-network.md. Present a summary to the user highlighting:
- ACH rule compliance status and key gaps
- Card network registration and compliance status
- State licensing coverage and gaps (number of states licensed vs. required)
- Top 3 gaps requiring remediation
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-payment-network","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-payment-network
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.