UPI Payment UX and Ops

Design and review user and operations messaging, flows, and support templates for UPI payments, mandates, refunds, disputes, and incident communication.

This skill appears coherent and safe as a content/ops guidance tool. Before using it in production: (1) verify all regulatory and provider-specific behavior (RBI, NPCI, PSPs) as the docs themselves advise, (2) run generated copy through your legal/compliance and localization reviews, (3) test messaging and playbooks in staging with real webhook/provider behavior to confirm state semantics, and (4) treat this as authoring guidance only — it does not execute payments or replace integration/runbook code. If you expect the skill to integrate with payment APIs or access production data, choose a different integration-specific skill and provide only the minimal credentials required for that purpose.

Type: OpenClaw Skill Name: upi-payment-ux-ops Version: 1.0.2 The skill bundle is a collection of documentation, templates, and instructions for designing UPI (Unified Payments Interface) user experiences and operational playbooks. It contains no executable code, shell commands, or data exfiltration logic. The instructions in SKILL.md and supporting files (examples.md, reference.md) are strictly aligned with the stated purpose of generating UI copy and support macros, and they include legitimate links to official regulatory bodies like the RBI (rbi.org.in).