Agent skill · Code Review & Quality

malaysia-payment-gateway

Build, debug, review, and explain Malaysia payment gateway integrations. Use when implementing checkout, payment links, hosted payment pages, redirects, callbacks, webhooks, HMAC/signature verification, idempotent settlement, paid-access unlocking, refunds, reconciliation, sandbox/live setup, or provider switching for Malaysian gateways such as CHIP Collect, Curlec/Razorpay, Xendit Malaysia, Bayarcash, BCL Pay, toyyibPay, Billplz, FPX, DuitNow QR, cards, or e-wallets.

afu-itgithub.com/afu-itGitHub ↗
codex
Install
npx skills add afu-it/malaysia-payment-gateway --skill malaysia-payment-gateway --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 4 KB
Bundled scripts: none
Path: malaysia-payment-gateway/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 67

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Malaysia Payment Gateway Use this skill to add production-grade payment collection to an app, not only to make a checkout button. Treat payment as a state machine: local intent first, gateway session second, verified server-side settlement last. ## Quick Start 1. Identify provider, product, currency, amount unit, and environment. 2. Read [references/integration-checklist.md](references/integration-checklist.md). 3. If provider-specific guidance is needed, read [references/provider-patterns.md](references/provider-patterns.md). 4. Before marking complete, check [references/security-settlement.md](references/security-settlement.md). ## Implementation Workflow ### 1. Map Existing App Find: - Auth/session helper. - Database access layer. - Existing order, invoice, subscription, entitlement, or payment tables. - Server route pattern. - Environment/secret handling. - Test style and deployment target. Do not start with provider API calls before local payment records and settlement rules are clear. ### 2. Create Local Payment Intent Create or reuse a `payments` table with at least: - `id` - `user_id` or customer id - `product` or order id - `amount_original` - `discount_amount` - `amount

What's inside
Steps it walks through
  1. Quick Start
  2. Implementation Workflow
  3. 1. Map Existing App
  4. 2. Create Local Payment Intent
  5. 3. Create Checkout Server-Side
  6. 4. Verify Callback/Webhook
  7. 5. Settle Idempotently
  8. Provider Choice
  9. Completion Criteria
Ships with 4 files
  • agents/openai.yaml
  • references/integration-checklist.md
  • references/provider-patterns.md
  • references/security-settlement.md
More from malaysia-payment-gateway
All skills →
About this skill
What does the malaysia-payment-gateway skill do?

Build, debug, review, and explain Malaysia payment gateway integrations. Use when implementing checkout, payment links, hosted payment pages, redirects, callbacks, webhooks, HMAC/signature verification, idempotent settlement, paid-access unlocking, refunds, reconciliation, sandbox/live setup, or provider switching for Malaysian gateways such as CHIP Collect, Curlec/Razorpay, Xendit Malaysia, Bayarcash, BCL Pay, toyyibPay, Billplz, FPX, DuitNow QR, cards, or e-wallets.

How do I install it?

Run `npx skills add afu-it/malaysia-payment-gateway --skill malaysia-payment-gateway --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From afu-it/malaysia-payment-gateway, a repository with 67 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going