How do I install the Setup Chip skill?

Run npx skillmds@latest add afu-it/setup-chip in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Setup Chip safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Setup Chip?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Setup Chip free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Setup Chip?

afu-it (@afu-it) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Setup Chip by afu-it — Agent Skill

Name: Setup Chip
Author: afu-it

Setup Chip

Set up, build, debug, and explain CHIP Collect payment integrations using the official CHIP Collect API documentation. Use when working with CHIP Collect purchases, checkout URLs, payment links, direct post, FPX, DuitNow QR, cards, e-wallets, callbacks, webhooks, signature verification, clients, recurring tokens, subscriptions, pre-authorization, refunds, captures, releases, payment methods, statements, account balance, account turnover, API keys, Brand ID, or CHIP Collect endpoint schemas.

afu-it 8e8c9f4 4 files · 1.1 MB Updated Sep 17, 2026

File contents

CHIP Collect API

Use this skill for CHIP Collect payment integration work.

Source

Read references/chip-collect-docs.md before giving factual API guidance or writing integration code. It contains all downloaded CHIP Collect markdown pages plus embedded OpenAPI blocks from:

https://docs.chip-in.asia/chip-collect/overview/introduction

Read references/account-setup.md when user asks how to register, which API keys are needed, where credentials come from, or what dashboard setup is required.

Core Facts

Base URL: https://gate.chip-in.asia/api/v1/
Auth: Authorization: Bearer <secret key> for every request.
Credentials: API key and Brand ID come from CHIP Collect Developers pages in portal.
Amounts: money values are smallest currency units. Example: price: 100 equals RM 1.00.
Create checkout/payment link flow: POST /purchases/, then use response checkout_url.
Payment status options: success callback, GET /purchases/{id}/, or webhook events.
Test cards: 4444 3333 2222 1111 non-3DS, 5555 5555 5555 4444 3DS, CVC 123, expiry >= current month/year.
Callback signature: X-Signature is base64 RSA PKCS#1 v1.5 over SHA256 digest of raw request body.
Success callback public key: GET /public_key/; webhook public key: Webhook.public_key.

Lookup Map

Purchases: create, retrieve, cancel, capture, charge token, refund, release, resend invoice, mark paid.
Clients: create/list/retrieve/update/delete, recurring token list/retrieve/delete.
Webhooks: create/list/retrieve/update/delete.
Payment methods: GET /payment_methods/, usually with brand_id and currency.
Direct post: intro, card, FPX, DuitNow QR, e-wallet.
Online flows: payment link, pre-authorization, subscriptions, custom flow.
Account/reporting: balance, turnover, company statements.

Working Rules

Use exact endpoint paths and request fields from reference OpenAPI blocks.
Preserve trailing slashes on CHIP Collect endpoints as documented.
For code, keep secrets in env vars and never hard-code API keys or Brand IDs.
For webhooks/callbacks, require raw request body for signature verification.
If user asks for latest pricing, legal terms, supported methods, or production portal state, verify live docs first.

---name: setup-chipdescription: Set up, build, debug, and explain CHIP Collect payment integrations using the official CHIP Collect API documentation. Use when working with CHIP Collect purchases, checkout URLs, payment links, direct post, FPX, DuitNow QR, cards, e-wallets, callbacks, webhooks, signature verification, clients, recurring tokens, subscriptions, pre-authorization, refunds, captures, releases, payment methods, statements, account balance, account turnover, API keys, Brand ID, or CHIP Collect endpoint schemas.---# CHIP Collect APIUse this skill for CHIP Collect payment integration work.## SourceRead `references/chip-collect-docs.md` before giving factual API guidance or writing integration code. It contains all downloaded CHIP Collect markdown pages plus embedded OpenAPI blocks from:`https://docs.chip-in.asia/chip-collect/overview/introduction`Read `references/account-setup.md` when user asks how to register, which API keys are needed, where credentials come from, or what dashboard setup is required.## Core Facts- Base URL: `https://gate.chip-in.asia/api/v1/`- Auth: `Authorization: Bearer <secret key>` for every request.- Credentials: API key and Brand ID come from CHIP Collect Developers pages in portal.- Amounts: money values are smallest currency units. Example: `price: 100` equals `RM 1.00`.- Create checkout/payment link flow: `POST /purchases/`, then use response `checkout_url`.- Payment status options: success callback, `GET /purchases/{id}/`, or webhook events.- Test cards: `4444 3333 2222 1111` non-3DS, `5555 5555 5555 4444` 3DS, CVC `123`, expiry >= current month/year.- Callback signature: `X-Signature` is base64 RSA PKCS#1 v1.5 over SHA256 digest of raw request body.- Success callback public key: `GET /public_key/`; webhook public key: `Webhook.public_key`.## Lookup Map- Purchases: create, retrieve, cancel, capture, charge token, refund, release, resend invoice, mark paid.- Clients: create/list/retrieve/update/delete, recurring token list/retrieve/delete.- Webhooks: create/list/retrieve/update/delete.- Payment methods: `GET /payment_methods/`, usually with `brand_id` and `currency`.- Direct post: intro, card, FPX, DuitNow QR, e-wallet.- Online flows: payment link, pre-authorization, subscriptions, custom flow.- Account/reporting: balance, turnover, company statements.## Working Rules- Use exact endpoint paths and request fields from reference OpenAPI blocks.- Preserve trailing slashes on CHIP Collect endpoints as documented.- For code, keep secrets in env vars and never hard-code API keys or Brand IDs.- For webhooks/callbacks, require raw request body for signature verification.- If user asks for latest pricing, legal terms, supported methods, or production portal state, verify live docs first.

Frequently asked questions