| name | mena-payments |
| description | Use this skill when integrating, comparing, testing, or reviewing Arab/MENA payment gateways, checkout flows, payment links, refunds, captures, webhooks, sandbox credentials, and gateway selection across Egypt, GCC, Levant, and North Africa. |
MENA Payments
When To Use
Use this skill for payments work in Arab/MENA contexts, especially when the prompt includes: payment, checkout, gateway, refund, capture, webhook, KNET, mada, Meeza.
When Not To Use
- Do not process live payments or refunds.
- Do not invent endpoint URLs, credentials, or webhook signatures.
Required Inputs
- Country or market.
- Target vendor, if already selected.
- Desired flow: select, confirm, separate, return.
- Sandbox vs production state.
- Whether live customer, payment, tax, identity, bank, or payroll data is involved.
Default Workflow
- Read
sources.yml to see available vendors and confidence.
- If a vendor is named, read only
vendors/<vendor-id>.md for that vendor.
- If choosing vendors, compare only vendors in this skill's registry: amazon-payment-services, amazon-payment-services-payfort, easykash, fawrypay, geidea, hyperpay, kashier, moyasar, myfatoorah, paylink, paymob, paysky, ....
- Load
references/integration-checklist.md only for implementation, review, or launch-readiness work.
- Use
scripts/list-vendors.mjs for a deterministic vendor list when needed.
- Answer with source-backed facts, explicit unknowns, and validation steps.
Decision Tree
- Named vendor: read that vendor file, then answer narrowly.
- Vendor selection: filter by country, docs access, maturity, and source quality before recommending.
- Implementation: include auth, sandbox, webhook/callback, retries, idempotency, logging, and error handling only where source-backed.
- Missing docs: say
Needs vendor access or Unknown from public docs.
Files To Read
- Routing and process:
SKILL.md.
- Vendor facts:
vendors/*.md.
- Source map:
sources.yml.
- Implementation review:
references/integration-checklist.md.
- Example response style:
examples/source-backed-answer.md.
Safety Rules
- Use sandbox first and keep live keys out of source control.
- Require explicit approval before live payment, refund, payout, capture, or void operations.
- Verify webhook authenticity only from vendor docs; otherwise say it needs vendor confirmation.
- Store gateway transaction IDs and make retry behavior idempotent.
Validation Checklist
- Vendor facts map back to
source_urls.
- Unknowns are labeled instead of guessed.
- Sandbox and production are separated.
- Secrets are not printed or committed.
- High-risk live actions require explicit human approval.
- Evals in
evals/prompts.yml still cover the changed workflow.
Done Criteria
- The answer names the files read or source-backed references used.
- The implementation plan includes tests and rollback/verification steps.
- No unsupported regional, API, compliance, pricing, or endpoint claims are included.
