docs.clickmax.io

clickmax-wallet-receivables

Use when the user asks if they are ready to sell/receive, about the Clickmax wallet ("Carteira"), bank/receiving account approval, balances, "a receber", receivables, statement/extrato, or withdrawals (saques).

First seen Jun 18, 2026

Installation

$ npx skills add https://docs.clickmax.io

Also in this package

Other skills from docs.clickmax.io · top by installs.

npx skills add https://docs.clickmax.io

Browse all from docs.clickmax.io

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Versionv12.1.3
LicenseMIT
CompatibilityRequer o MCP da Clickmax ativo e conectado. Os nomes de tool
More metadata
author
Bilhon Technologies LTDA
version
v12.1.3
tools
["sellers_status","wallet_statement","wallet_withdraws"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,452 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 85 installs

SKILL.md

As tools abaixo aparecem com os nomes que o MCP da Clickmax registra. Se o seu cliente de IA prefixar nomes de tool (mcp<servidor>, mcp<servidor>, ou outro), use o nome já prefixado que aparecer na sua lista de tools.

When this applies

Use this skill for seller financial readiness and wallet questions: whether the seller can sell and receive, bank/receiving-account approval, available/pending/"a receber"/anticipatable balances, the wallet statement (extrato), and withdrawal (saque) history.

Not this skill:

  • sales/subscription KPIs and revenue analysis -> clickmax-payments-dashboard-analysis
  • refund/transaction mutations -> clickmax-transaction-operations

Key assumptions

  • Clickmax processes payments natively; there is NO external gateway (Stripe, PayPal, Mercado Pago, etc.) to configure to receive sales — never suggest one
  • "ready to sell and receive" = sellerStatus: enabled AND bankAccountStatus: approved
  • balances and "a receber" come from the wallet statement, not the sales dashboard
  • raw bank account numbers, pix keys, ids, and transaction hashes are never surfaced to the user

Thought process

  1. If the user asks whether they can start selling/receiving, read seller status first.
  2. If they ask about money in the wallet (saldo, a receber, antecipável, extrato), read the statement.
  3. If they ask about cashouts, read withdrawals.

Execute guide

  • For "am I ready to sell/receive" or "are my bank details approved", use sellers_status and interpret:

- sellerStatus: enabled + bankAccountStatus: approved -> ready to sell and receive - pending / pending_correction -> still under review; explain the reason and point to completing or correcting data in the wallet ("Carteira") - reproved / blocked / disabled -> blocked; explain the reason and the wallet correction step

  • For balances and movement history (saldo disponível, a receber, em análise, antecipável, extrato), use wallet_statement; use page/perPage to browse.
  • For withdrawal/cashout history (saques), use wallet_withdraws.

Report

  • Lead with the direct answer: ready or not, and the single blocker if any.
  • Present money as amounts only; never expose bank account numbers, pix keys, ids, or hashes.
  • For balances, separate available vs pending ("a receber") vs anticipatable.

Warnings

  • Never recommend or imply an external payment gateway/checkout to receive sales; Clickmax handles checkout and payment natively.
  • A pending/reproved status is resolved in the Clickmax wallet/account setup, never by integrating a third party.

Anti-patterns

  • Suggesting Stripe or any external integrator for receiving sales.
  • Reading the sales dashboard to answer wallet balance / "a receber" questions.
  • Surfacing raw bank account, pix, ids, or transaction hashes.