upi-payment-integration

What This Skill Does

The upi-payment-integration skill is a comprehensive toolkit designed to assist developers in building, auditing, and troubleshooting UPI-based payment flows. It provides architectural patterns and implementation guidance for integrating various UPI modalities, including Collect requests, Intent payments, static/dynamic QR codes, and Recurring Autopay mandates. This skill emphasizes the transition from basic API connectivity to production-grade reliability by focusing on idempotency, asynchronous transaction lifecycles, and RBI-compliant data handling.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anugotta/upi-payment-integration Ensure you have verified your environment setup, including secret manager access for API credentials and a validated webhook endpoint for asynchronous communication with your chosen Payment Service Provider (PSP).

Use Cases

• Production-Grade Implementation: Designing transaction state machines that handle PENDING, SUCCESS, and FAILED states while ensuring webhook events are recorded before processing.
• Reconciliation Workflows: Building automated scripts to compare your internal database records against settlement reports provided by PSPs, helping to identify and resolve 'ghost' transactions or payment mismatches.
• Edge Case Management: Debugging recurring payment mandate failures, handling gateway timeout scenarios where the user might have paid but the server received no signal, and managing idempotency keys to prevent duplicate billing.
• Compliance Audits: Aligning your payment flows with current RBI circulars regarding user authentication, consent management for mandates, and data storage requirements.

Example Prompts

1. "I'm seeing high timeout rates on UPI Intent payments for my checkout flow. Can you help me design a robust retry mechanism and status reconciliation loop?"
2. "How do I safely implement idempotent webhook handlers for UPI Collect requests so that I don't process the same transaction twice?"
3. "Explain the steps required to transition a static QR implementation to a dynamic QR system while maintaining compliance with current NPCI guidelines."

Tips & Limitations

• Asynchronous Mindset: Always treat your internal database as the source of truth, updated primarily via webhooks and validated through periodic reconciliation polling.
• Security: Never transmit raw payment credentials or private keys in the chat interface. Always verify implementation against the latest official NPCI/PSP documentation as these regulations evolve frequently.
• Responsibility: This skill provides architectural and implementation advice; it does not process funds or provide legal advice. Always perform rigorous testing in a sandbox environment and consult your organization's legal/compliance department before deploying to production.