Skill Abacatepay Integration

Organization

IAPro-Community

skill-abacatepay-integration

Integrate AbacatePay PIX/card billing, customers, QRCode PIX, billing webhooks, CPF/CNPJ validation, BRL SaaS checkout, payment receipts, refunds, cancellations, and entitlement sync for Brazilian SaaS products.

Overview

Publisher	IAPro-Community
Repository	`Orquestrador-Maestro`
Skill name	`skill-abacatepay-integration`
Stars	63
Forks	11
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by IAPro-Community on GitHub. Read the source before you install it.

Installation

Install the Skill Abacatepay Integration 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/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-abacatepay-integration
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-abacatepay-integration

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/IAPro-Community/Orquestrador-Maestro.git /tmp/Orquestrador-Maestro
mkdir -p .claude/skills
cp -r /tmp/Orquestrador-Maestro/codex/skills/skill-abacatepay-integration .claude/skills/skill-abacatepay-integration

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

Use it in TypingMind

Enable Skill Abacatepay Integration 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 Skill Abacatepay Integration 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 Skill Abacatepay Integration 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.

skill-abacatepay-integration

Workflow

Inspect the project backend boundary first: Netlify/Vercel function, Express route, server action, Edge Function, or other server-only layer.
Keep all AbacatePay calls behind that backend boundary. Browser code calls the project API, never AbacatePay directly with secrets.
Validate customer data before billing creation: email, cellphone with country code, CPF/CNPJ without punctuation, amount in cents, plan ID, and tenant/user identity.
Create billing with stable metadata: user_id, tenant_id, plan_id, internal correlation ID, and payment link token when present.
Persist provider IDs, normalized status, amount, currency, raw event reference, and support/debug timestamps.
Process webhooks idempotently, update entitlements from trusted backend evidence, and audit every access transition.
Verify with local webhook tooling or provider test events plus project build/typecheck.

Current API Shape (v2)

Use API v2 for new work. API v1 remains only for legacy integrations:

base URL: https://api.abacatepay.com/v2
hosted checkout: POST /checkouts/create
subscriptions: POST /subscriptions/create
transparent PIX/card/boleto checkout: POST /transparents/create
webhook management: POST /webhooks/create
auth header: Authorization: Bearer <abacatepay-api-key>
current checkout events: checkout.completed, checkout.refunded, checkout.disputed
current subscription events: subscription.completed, subscription.renewed, subscription.cancelled

The old v1 routes such as /v1/billing/create and events such as billing.paid are legacy-compatible references. Do not copy them into new integrations; if maintaining v1, isolate an adapter and plan migration to v2.

Guardrails

Keep ABACATEPAY_API_KEY and webhook secrets server-side.
Treat checkout redirect as advisory. Grant access only after trusted backend/webhook confirmation.
Deduplicate webhook processing by the v2 event ID and the provider checkout/subscription ID.
Do not log API keys, webhook secrets, full CPF/CNPJ, full phone numbers, or unnecessary PII.
Keep plan and entitlement rules in local product tables, not encoded only in AbacatePay objects.
Support retries and out-of-order delivery by re-reading local payment state before mutation.

Local Pattern

The example-saas project has a useful boundary pattern: frontend client calls a Netlify function, the function uses the server API key and service-role Supabase client, and the webhook updates users/plans after billing.paid.

Read {{USER_HOME}}/Documents/Code/example-saas/src/lib/abacatepay.ts only when implementing a similar client boundary or validating local conventions.

Validation

Confirm no ABACATEPAY_API_KEY or webhook secret appears in browser bundles or VITE_ variables.
Simulate or replay billing.paid and confirm idempotent entitlement update.
Check invalid CPF/CNPJ, invalid cellphone, duplicate webhook, expired billing, and failed provider response paths.
Run the project build/typecheck/lint when available.
Confirm the integration uses the v2 payload shape (apiVersion: 2) and does not assume the legacy billing.* event names.

Official References

https://docs.abacatepay.com/pages/reference/introduction
https://docs.abacatepay.com/pages/payment/create
https://docs.abacatepay.com/pages/webhooks
https://docs.abacatepay.com/pages/changelog

Related Skills

skill-saas-factory
skill-saas-core-limits
skill-supabase-rls
skill-security-hooks

Frequently asked questions

What does the Skill Abacatepay Integration AI skill do?

Why use Skill Abacatepay Integration on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/IAPro-Community/Orquestrador-Maestro/tree/v1/codex/skills/skill-abacatepay-integration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Abacatepay Integration?

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 Skill Abacatepay Integration?

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

Is the Skill Abacatepay Integration AI skill free?

Yes. It is published on GitHub by IAPro-Community under the Apache-2.0 license. 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

Command Development

anthropics

OrganizationPopular

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create…

Discord E2e

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

Openclaw Ghsa Maintainer

openclaw

OrganizationPopular

Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.

Openclaw Secret Scanning Maintainer

openclaw

OrganizationPopular

Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

skill-abacatepay-integration

Workflow

Current API Shape (v2)

Guardrails

Local Pattern

Validation

Official References

Related Skills

Frequently asked questions

Related AI Skills

Set up your own AI workspace now