pluggyai/pluggy-payments
skills/pluggy-payments/SKILL.md
Payment initiation with PIX, Boleto, and Smart Transfers. Use when implementing payment flows, PIX transfers, or preauthorized payments.
$ install --global
skillsauthnpx skillsauth add pluggyai/agent-skills pluggy-paymentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 30, 2026, 6:11 AM16.2s9 files scanned
SKILL.md
- name:
- pluggy-payments
- description:
- Payment initiation with PIX, Boleto, and Smart Transfers. Use when implementing payment flows, PIX transfers, or preauthorized payments.
- license:
- MIT
- author:
- pluggy
- version:
- 1.0.0
Pluggy Payments
Comprehensive guide for implementing payment initiation through Pluggy. Contains rules across 5 categories, prioritized by impact.
When to Apply
Reference these guidelines when:
- Initiating PIX payments
- Creating and managing Boletos
- Setting up Smart Transfers with preauthorization
- Managing payment intents lifecycle
- Handling scheduled payments (PIX Agendado)
- Implementing PIX Automático
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
| -------- | ------------------- | -------- | ------------ |
| 1 | PIX Integration | CRITICAL | pix- |
| 2 | Smart Transfers | HIGH | smart- |
| 3 | Payment Lifecycle | HIGH | payment- |
| 4 | Boleto Management | MEDIUM | boleto- |
| 5 | Scheduled Payments | MEDIUM | schedule- |
How to Use
Read individual rule files for detailed explanations and code examples:
rules/pix-initiation.md
rules/smart-preauthorization.md
rules/payment-lifecycle.md
Each rule file contains:
- Brief explanation of why it matters
- Incorrect code example with explanation
- Correct code example with explanation
- Additional context and references
- Pluggy-specific notes
Payment Flow Overview
1. Create Payment Request (with recipient details)
2. Create Payment Intent (for specific Item/account)
3. User authorizes in Connect Widget
4. Monitor payment status via webhook
5. Handle success/failure
Full Compiled Document
For the complete guide with all rules expanded: AGENTS.md
Related Skills
pluggyai/pluggy-open-finance
data-ai
VerifiedTrustedCommunity
Best practices for Open Finance data retrieval and management. Use when working with accounts, transactions, investments, loans, or identity data.
4SKILL.mdUpdated May 30, 2026
pluggyai/pluggy-integration
development
VerifiedTrustedCommunity
Core Pluggy integration patterns and best practices. Use when setting up Pluggy SDK, implementing Connect Widget, managing Items, or configuring webhooks.
4SKILL.mdUpdated May 30, 2026
pluggyai/pluggy-doctor
tools
VerifiedTrustedCommunity
Code-reviews Pluggy API integrations against Pluggy's official documentation (queried in real time via the Pluggy MCP, with a web fallback to docs.pluggy.ai when the MCP isn't connected) and returns a diagnostic report (✅/❌/⚠️) with file, line, and the code fix for each issue. Use WHENEVER the dev uploads integration files and asks to review, analyze, diagnose, or validate their Pluggy integration — or says things like "review my integration", "check my Pluggy code", "is this ready for production?", "Pluggy Doctor", "check my webhooks", "is my integration secure?", or the Portuguese variants "analisa minha integração", "revisa meu código da Pluggy", "tá tudo certo pra ir pra produção?", "checa meus webhooks", "minha integração tá segura?". Also trigger when the dev pastes/uploads code that clearly calls the Pluggy API (connect_token, GET /items, item/created webhooks, clientUserId, etc.) and wants to know if it's correct, even without saying "Pluggy Doctor". This skill is for REVIEWING existing code, not writing an integration from scratch.
4SKILL.mdUpdated May 30, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026