Setup Boldpay

Community

afu-it

setup-boldpay

Set up, build, debug, review, and explain BOLD.Pay (by MACROKIOSK) payment integrations using official BOLD.Pay sources (the MACROKIOSK WooCommerce plugin source and product pages), hosted PaymentRequest redirect, MD5 AccessToken, CallbackURL browser return, NotificationURL server POST, QueryRequest status requery, PayID, CustIP, currency codes, error codes 400 to 500, BOLD.Pass portal API key and Domain/IP Restrictions, sandbox (UAT) vs live setup, and the WooCommerce plugin. Use when working with BOLD.Pay Malaysia, MACROKIOSK payments, boldpass.com, pay.etracker.cc, FPX online banking, cards, e-wallets, BNPL, OTC, carrier billing, WooCommerce or OpenCart BOLD.Pay setup, callback settlement, or production readiness.

Overview

Publisher	afu-it
Repository	`malaysia-payment-gateway`
Skill name	`setup-boldpay`
Stars	74
Forks	11
Bundled files	4
Links	Skill source Repository

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.
4 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 Boldpay AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/afu-it/malaysia-payment-gateway/tree/main/setup-boldpay
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.

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-boldpay .claude/skills/setup-boldpay

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Setup Boldpay 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 Boldpay 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 Boldpay 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.

BOLD.Pay Payment Gateway

Use this skill for BOLD.Pay (MACROKIOSK) payment integration work.

Source

Read references/boldpay-api.md before giving factual API guidance or writing integration code. BOLD.Pay has no public API reference; that file is distilled from the official MACROKIOSK WordPress.org plugin source (v1.7.1) and lists the endpoint catalogue, every request and response field, the AccessToken algorithm, requery, status and error codes, and what is not documented.

Read references/account-setup.md when the user asks how to register, where the username and API key live, Domain/IP Restrictions, WooCommerce plugin setup, sandbox access, channels, pricing or settlement.

Read references/source-map.md when choosing which source file backs a fact, or to see coverage and gaps.

Core Workflow

Identify environment: sandbox (uat.pay.etracker.cc) or live (pay.etracker.cc).
Identify surface: WooCommerce plugin (use it as is), OpenCart/EasyStore plugin, or custom integration that mirrors the plugin protocol.
Confirm portal setup: approved BOLD.Pass username, API key, and your domain and server IP in Domain/IP Restrictions.
Create a local pending payment first with expected amount (2 decimals, ringgit), a new unique PayID, the CustIP you will send, and the callback and notification URLs used.
Compute AccessToken server-side: UPPER(MD5(UPPER(Username + "4" + Amount + CustIP + PayID + CallbackURL + NotificationURL + ApiKey))).
Redirect the browser to PaymentRequest? with all fields (URLs and text URL-encoded).
On browser return or notification, recompute the token from stored values and compare (constant-time).
Call QueryRequest server-side and read the result from the redirect Location query string.
Check query TransactionID, OrderNumber, PayID match, then settle idempotently on query Status = SUCCESS.
Reply OK to the notification POST.

Core Facts

Live payment page: https://pay.etracker.cc/BoldPayApi/PaymentRequest.
Sandbox payment page: https://uat.pay.etracker.cc/BoldPayApi/PaymentRequest.
Status query: https://pay.etracker.cc/BoldPayApi/QueryRequest (sandbox host uat.pay.etracker.cc; plugin uses http:// there, HTTPS also answers).
Create payment is a browser GET redirect with a query string, not a JSON API.
Request fields: AccessToken, Username, CustIP, PymtMethod (4), Amount, Description, CustName, CustEmail, CustPhone, OrderNumber, PayID, CallbackURL, NotificationURL, ApiKey, Origin, CurrencyCode.
CurrencyCode: 1 MYR, 3 THB.
Amount is ringgit with exactly 2 decimals, not sen.
AccessToken is uppercase hex MD5 of the uppercased concatenation; URLs are raw (not encoded) inside the hash.
Response fields: AccessToken, TransactionID, OrderNumber, PayID, Status, Reason, PymtMethod, IssuingBank.
Status values: SUCCESS, PENDING, FAIL, REFUNDED, REVERSED; rejected requests return a numeric error code instead.
Channel codes: CC, DD (online banking), WA (e-wallet), BNPL, OTC.
QueryRequest params: AccessToken, APIKey, Username, PayID, CallBackUrl (note casing).
Notification is a server POST; reply body OK.
API key lives in BOLD.Pass > Admin Management > Business Setting > API Key.
No refund, recurring, instalment-field or payout API is published.

Critical Rules

The response AccessToken is the request token echoed back. It does not sign Status and it was visible in the browser URL. Never settle from callback fields alone; always settle from QueryRequest.
Recompute the token from stored expected values (amount, CustIP, URLs), never from values in the callback.
Keep TLS verification on for QueryRequest (the plugin turns it off; do not copy that).
The API key appears in the payment URL by design. Lock it down with Domain/IP Restrictions and rotate it if leaked.
Generate a fresh PayID per attempt; reuse returns 416.
Send CustPhone as digits only.
Use one stable CustIP per payment and store it; the token breaks if it changes between request and callback.
Make settlement idempotent: browser return and notification both arrive for the same payment.
Never move a paid order back on a late PENDING or FAIL.
Do not quote fees, limits, or settlement times; they are per merchant agreement.

Completion Criteria

A BOLD.Pay integration is done only when:

The token is built server-side and matches the documented order; a known-good sandbox payment succeeds.
Local pending record stores PayID, amount, currency code, CustIP, callback and notification URLs.
Callback and notification handlers recompute and compare the token in constant time.
Every state change is confirmed by QueryRequest, with TransactionID, OrderNumber, PayID matched.
Duplicate return plus notification settle once.
Error-code returns (no AccessToken) leave the order unpaid and are logged.
Tests cover bad token, wrong amount, query mismatch, FAIL, PENDING, REFUNDED, duplicate notification and SUCCESS.
Deployment docs list BOLDPAY_USERNAME, BOLDPAY_API_KEY, BOLDPAY_ENV, callback and notification URLs, server IP, and the Domain/IP Restrictions step.

Loophole Review Loop

When asked whether a BOLD.Pay strategy is "100% confident", run this loop until no factual gaps remain:

List trust boundaries: browser redirect URL, BOLD.Pay hosted page, callback return, notification receiver, QueryRequest call, database, fulfilment job, BOLD.Pass portal settings.
Check bypasses: forged callback with a copied token, Status=SUCCESS without query, query skipped on FAIL, amount changed in the URL, reused PayID, changed callback URL breaking in-flight tokens, sandbox/live mix, TLS off on query, leaked API key, duplicate notification, late PENDING after SUCCESS, refund done in portal not reflected locally.
Add fixes: stored-value token recompute, mandatory QueryRequest, strict field matching, unique PayID, per-payment stored URLs and IP, idempotent settlement, Domain/IP Restrictions, TLS on, refund/reversal handling.
Re-read references/boldpay-api.md sections relevant to any gap.
State remaining uncertainty: no public API guide, Origin value for custom integrations, PymtMethod meaning, notification retry policy, sandbox credentials, limits, refund process. Tell the user to confirm these with MACROKIOSK.

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 Boldpay AI skill do?

Why use Setup Boldpay on TypingMind?

Because you install it once and use it with any model. Setup Boldpay 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 Boldpay in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/afu-it/malaysia-payment-gateway/tree/main/setup-boldpay. 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 Boldpay?

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 Boldpay?

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

Is the Setup Boldpay 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

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

BOLD.Pay Payment Gateway

Source

Core Workflow

Core Facts

Critical Rules

Completion Criteria

Loophole Review Loop

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now