domain-payments
Skill1 starsChanged 8 days agoMITView on GitHub
Payments and e-wallet domain knowledge for Business Analysts - glossary, core processes (merchant onboarding, wallet and KYC levels, top-up, withdrawal, P2P, online/QR payment, refund and chargeback, settlement, reconciliation), business rules (wallet limits by KYC level, authorize/capture, callback as source of truth, idempotency, three-way reconciliation, fees), data model with status sets, integrations (banks, NAPAS/QR, card schemes, PSP, KYC, AML), regulatory touchpoints and a BA question checklist. Use together with any BA task whenever the context is e-wallet, payment gateway, payment service provider, QR payment, top-up, withdrawal, merchant acquiring, settlement or reconciliation - or the user mentions "ví điện tử", "cổng thanh toán", "thanh toán QR", "nạp tiền", "rút tiền", "đối soát", "chargeback", "merchant", "PSP", "trung gian thanh toán".
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-specSkill
- ba-diagramsSkill
- bpmn-modelingSkill
- decision-tableSkill
- domain-bankingSkill
- domain-ecommerceSkill
- domain-lendingSkill
- domain-logisticsSkill
- edge-case-finderSkill
- functional-decompositionSkill
- meeting-to-requirementsSkill
- requirements-linterSkill
- screen-specSkill
- user-story-writerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Never include real card numbers, wallet IDs, or customer data.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Domain Pack: Payments & E-wallet / Thanh toán và ví điện tử
This skill adds domain knowledge on top of the BA method skills (meeting-to-requirements, requirements-linter, functional-decomposition, user-story-writer, decision-table, edge-case-finder, api-spec, screen-spec, bpmn-modeling, ba-diagrams). It makes their output payments-correct. For bank-owned products (accounts, transfers, cards) also load domain-banking.
How to use the references
| Task | Read |
| Terminology | references/glossary.md |
| Decompose functions, draw processes | references/processes.md |
| Requirements, stories, AC, decision tables | references/business-rules.md + references/checklist.md |
| ERD, API payloads, status sets | references/data-model.md |
| Context/sequence diagrams, integration specs | references/integrations.md |
| Compliance, security | references/regulations.md |
| Goals, reports | references/kpis.md |
How to apply domain knowledge
- Identify the role first: wallet issuer, payment gateway/PSP, acquirer, merchant, or a bank channel. It changes almost every rule.
- Add the scenarios a payments BA never forgets: callback lost or late, timeout then pending, duplicate request, partial refund, refund after settlement, chargeback window, reconciliation mismatch, wallet limit by KYC level, negative balance prevention, concurrent debits.
- Money first, UI second: define ledger movements and statuses before screens.
- Ask, don't invent: limits, fees, settlement cycles and windows are business or partner decisions ->
[value - confirm]. - Flag regulatory touchpoints (licensing, identification level, AML, data protection, card data) and add "verify the current regulation with Compliance/Legal".
Guardrails
- Generic typical practice with a Vietnam focus; each provider differs. Present as typical, not as the client's truth.
references/regulations.mdhas a "last reviewed" date and lists topics to ask about, not legal conclusions.- Never include real card numbers, wallet IDs, or customer data; use masked values.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.