payment-assistant

Name: payment-assistant
Availability: InStock
Author: npc-live

Parse and process QR-based C2C and PIX payment requests via a unified API client.

168|13|Updated Mar 20, 2026

Search Tags:#automation #workflow #security #payment #pix #qr-code #c2c

Ready to run

npx skills add https://github.com/npc-live/clawfirm --skill payment-assistant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: payment-assistant
Source: https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/payment-assistant
Command: npx skills add https://github.com/npc-live/clawfirm --skill payment-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines end-to-end QR-based payments by decoding QR codes and guiding users through a secure, automated workflow that handles C2C and PIX payments, amount selection, and status polling.

Core Features & Use Cases

Automatic QR type detection (C2C or PIX) and routing to the proper API endpoints
End-to-end payment flow: decode QR → parse → set amount (if allowed) → confirm → poll for result
Robust recovery and safety: local state persistence, explicit user confirmation, and duplicate-payment protection

Quick Start

Run payment_skill.py and feed it a QR code image or text to start the end-to-end pay flow.

Frequently Asked Questions about payment-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate QR-based PIX and C2C payment processing?▼

Automate QR-based PIX and C2C payments by decoding the QR code text or image to automatically route, parse, and confirm transactions through a unified API client. The workflow detects the QR type, enforces PIX amount rules, and polls for the final payment status.

How does QR type detection work for PIX and C2C payment workflows?▼

QR type detection works by parsing the decoded QR code data to identify whether it is a PIX or C2C payment, then routing the request to the proper API endpoints. This mechanism ensures the correct validation rules and amount flows are applied for each transaction type.

Can I process changeable-amount QR codes or do payments require preset amounts?▼

You can process both preset-amount and changeable-amount QR codes. The workflow parses the QR data, allows you to set the amount if the flow permits, and enforces specific PIX amount rules before confirming the payment.

What is the best way to prevent duplicate QR payments in an automated workflow?▼

Prevent duplicate QR payments by using local state persistence and explicit user confirmation before finalizing any transaction. The workflow guards against duplicate payments by managing state across the decode, parse, and confirm stages of the process.

How do I recover an interrupted PIX or C2C payment?▼

Recover interrupted PIX or C2C payments through the workflow's local state management and robust error handling. The system persists the payment state during the decode and confirm stages, allowing you to resume or safely retry without duplicating the transaction.

Do I need an OpenAPI-driven transport to handle QR payment status polling?▼

You need an OpenAPI-driven transport to manage the QR payment workflow, including status polling. It provides the structured communication layer required to drive decode, parse, confirm, and status polling operations while maintaining local state.