Setup Chip logo

Setup Chip

Community
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.

Overview

Publisherafu-it
Repositorymalaysia-payment-gateway
Skill namesetup-chip
Stars
74
Forks
11
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by afu-it on GitHub. Read the source before you install it.

Installation

Install the Setup Chip AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/afu-it/malaysia-payment-gateway/tree/main/setup-chip
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/afu-it/malaysia-payment-gateway.git /tmp/malaysia-payment-gateway
mkdir -p .claude/skills
cp -r /tmp/malaysia-payment-gateway/setup-chip .claude/skills/setup-chip
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup Chip in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Setup Chip on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Setup Chip is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Setup Chip AI skill do?

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.

Why use Setup Chip on TypingMind?

Because you install it once and use it with any model. Setup Chip is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Setup Chip in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/afu-it/malaysia-payment-gateway/tree/main/setup-chip. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Setup Chip?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Setup Chip?

As many as you like. As long as a model supports skills, you can use Setup Chip with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Setup Chip AI skill free?

It is published on GitHub by afu-it. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇