Mayar Skills: Mayar payments for your app
Mayar Skills
The mayar-v2 skill walks an agent through adding Mayar payments: payment links, invoices, subscriptions, QRIS and webhooks
- 14 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The agent creates invoices, subscriptions and QRIS payments and registers webhooks in the Mayar account, and a production API key reaches real money
- A webhook handling mistake can cause duplicate fulfillment or a missed payment
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/mayar-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent creates invoices, subscriptions and QRIS payments and registers webhooks in the Mayar account, and a production API key reaches real money
- A webhook handling mistake can cause duplicate fulfillment or a missed payment
This is third-party code. Review the repository files before installing.
What it does
Mayar is a payment service for Indonesia: QRIS, virtual accounts, e-wallets and cards. The repository holds one skill, mayar-v2 (version 2.3.0), and ready prompts for installation and typical tasks. The skill works in three modes. BUILD adds payments to an application in four phases: project recon and questions, a plan with a data schema and approval, implementation, verification. The agent picks the payment type (one-time, invoice, subscription, credits, license, QRIS, installment) and the checkout kind: a Mayar page, an embedded overlay or your own form. Next.js, TanStack Start and Vite React have separate stack notes. OPS manages the account from the terminal through `npx -y mayar@latest`: balance, invoices, transactions, products, customers, webhooks and license checks. LEARN answers questions about Mayar from the documentation and changes nothing.
Who it is for. Developers and digital product owners in Indonesia who accept payments through Mayar and want an agent to wire them up.
Good fit when
- A site selling an ebook needs payment with a download link issued after the charge
- A membership for closed content has to renew by invoice every period
- A cash register needs a dynamic QRIS for an exact amount straight from the terminal
- A payment webhook fires twice and fulfillment is duplicated
- The buyer should stay on your site and pay in a window over the page
Not a fit when
- Payments are taken in Russia or through another gateway: the skill knows only Mayar and does not compare providers
- The project needs confirmed payment for a dynamic QRIS: the documentation has no webhook for that code, so reconciliation is manual
- The app runs only in a browser without a server, such as a Vite SPA: API keys cannot live on the client
Example request
Add Mayar payments to the site to sell a course: pay with one invoice, and open the lessons after payment.Limitations
You need a Mayar API key (web.mayar.id for production, web.mayar.io for the sandbox), access to the documentation and Node.js 18 or newer for the CLI commands. Mayar has no official SDK, and the sample code uses fetch.
The documentation defines no transaction ID in webhooks, so the skill rejects unverified requests by default. A dynamic QRIS has no identifier or webhook, and payments are reconciled in the dashboard. The installment model is newer than the skill, so the agent asks more questions. The README command with the --skill, --global and --yes flags installs only mayar-v2.
How to disable. Delete the mayar-v2 folder from the agent's skills directory (the skill documentation lists the path for each client) and revoke the API key in the Mayar dashboard. Payment code the agent already wrote has to be removed from the project separately.
FAQ
How do I install mayar-v2 in Claude Code?
Run npx skills add mayarid/skills --skill mayar-v2 --global --yes, or paste the prompts/install-claude-code.md prompt into the agent. Then check that Claude Code sees the skill and say: "Add Mayar payments to this website".
How do BUILD, OPS and LEARN differ?
BUILD writes integration code in four phases. OPS runs live CLI commands against your account. LEARN reads the documentation and answers questions without running or changing anything.
Which payment types does the skill support?
One-time payments, itemized invoices, subscriptions, credits, software licenses, dynamic QRIS and installments. The repository has a ready prompt for each, which is pasted into the agent unedited.
Does the skill work in Cursor and Codex?
Yes, Cursor and Codex have separate prompts, plus Hermes Agent, OpenClaw and other clients. Install paths into the skills directory are listed for OpenCode, Gemini CLI and GitHub Copilot.
How do the three checkout types differ?
Hosted sends the buyer to a Mayar page. Embedded opens the same page in an overlay on your site. Native renders payment methods in your own interface, using paymentMethod in the invoice. The agent recommends hosted by default.
Discussion
No questions or reviews yet.
Related
SkillsThe Minara skill gives an agent the crypto market in plain language: wallet, token swaps, Hyperliquid perps, limit orders and market analytics
A skill that connects an agent to EasyPay: Stripe products and invoices, SBP and T-Bank payout links, crypto and Mercury in natural language
Skill that finds paid APIs in the TadaPay directory by protocol and network and returns the endpoint and request format. Your client pays.
Official WeChat Pay skill: Claude Code and Cursor choose a product, write payment code, review the integration and troubleshoot errors
A Stripe command line and MCP server: the agent pays with credentials from a Link wallet only after you approve
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Mayar Skills: Mayar payments for your app (this card) | yes | 14 | ||
| Stripe AI | yes | OAuth | 2,059 | the Stripe MCP server and plugins, while this is Indonesian Mayar with QRIS and virtual accounts |
| YooKassa Skill | no | 0 | a skill for the Russian YooKassa, while this covers Indonesian payments |
README in short
Quick installation goes through the skills utility, six clients have install prompts, and the manual route is copying the mayar-v2 folder. Sample requests are grouped by BUILD, OPS and LEARN, and known gaps in the Mayar documentation are listed separately. The validate.mjs script checks the skill structure. The license is MIT.
README badge
Original SKILL.md
--- name: mayar-v2 description: > Use this skill when the user wants to integrate Mayar payments or billing into an application—hosted, embedded, or native checkout, payment links, invoices, memberships, subscriptions, credit wallets, licenses, QRIS, or webhooks—or operate their Mayar account from the terminal, including balance, products, customers, transactions, invoices, and webhook administration—or ask what Mayar is, what it does, which payment methods it accepts, or how its features, account setup, and business verification work. compatibility: Requires network access to Mayar documentation and API. CLI commands require Node.js 18+ and npx. metadata: version: "2.3.0" --- # Mayar Select one branch from the user request: - **BUILD** — Add a Mayar integration to an application. This branch includes the UI, server, persistent data, and fulfillment. - **OPS** — Manage or test a Mayar account from the terminal. - **LEARN** — Answer a question about Mayar itself. This branch reads documentation and changes nothing. A **live call** is an agent command against the Mayar account. Use `npx -y mayar@latest` for every live call. Application code uses the HTTP API. Read [references/cli-commands.md](references/cli-commands.md) for CLI syntax. If a BUILD documentation fetch or HTTP probe fails, take that CLI path and continue the phase. ## LEARN Read [references/product-knowledge.md](references/product-knowledge.md). Follow only that file. Do not load the BUILD playbook. Do not run CLI commands. Do not change any file. ## OPS Read [references/cli-commands.md](references/cli-commands.md). Follow the OPS procedure in that file. Do not load the BUILD playbook. ## BUILD: strict phase gates Complete one phase at a time. Do not read the next phase file until you meet the