# Mayar V2

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

- Skill: `mayarid/mayar-v2` (Agent Skill, multi-file: 17 files)
- Install (CLI): `npx skillmds@latest add mayarid/mayar-v2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mayarid/mayar-v2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: mayarid (https://skillmd.com/u/mayarid)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mayarid/mayar-v2

---


# 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
completion criteria for the current phase. Load
[references/cli-commands.md](references/cli-commands.md) before a live call.

### Phase 1 — Discover

Read [playbook/discover.md](playbook/discover.md). Stay in this phase until
RECON is complete and all user decisions are recorded.

### Phase 2 — Plan

After Discover is complete, read [playbook/plan.md](playbook/plan.md). Stay in
this phase until you record the schema or a CLI path. The user must also
approve the plan and the exact fulfillment operation.

### Phase 3 — Implement

After explicit approval, read [playbook/implement.md](playbook/implement.md).
Stay in this phase until all planned changes are complete and all project checks
pass.

### Phase 4 — Verify

After Implement is complete, read [playbook/verify.md](playbook/verify.md).
Complete the sandbox evidence, regression checks, and handoff before you close
the task.