razorpay-monitor_skill

This skill autonomously monitor Razorpay payments for Indian merchants, delivering daily reports, anomaly alerts, and weekly revenue summaries via WhatsApp or

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill razorpay-monitor

_meta.json284 B
SKILL.md5.6 KB

Overview

This skill provides autonomous Razorpay payment monitoring for Indian merchants. It tracks daily settlements, detects failed payments and anomalies, and delivers alerts and summaries via WhatsApp or Telegram. Configure with your Razorpay key and secret to receive daily, real-time, and weekly reports without logging into the dashboard.

How this skill works

The skill connects to the Razorpay REST API using HTTP Basic Auth with key ID and secret from environment variables. It polls payments, refunds, settlements, orders, and disputes on scheduled intervals and on-demand commands. Based on configurable thresholds it formats concise alerts and summaries (emoji + bold style) and sends them over WhatsApp or Telegram.

When to use it

Get an automated daily revenue and settlement report each morning at 8:00 AM IST.
Receive real-time alerts for spikes in payment failures, large transactions, disputes, and payment droughts during business hours.
Run ad-hoc commands like “revenue today”, “failed payments”, or “settlement status”.
Monitor weekly performance with a concise Monday summary and week-over-week comparisons.
Automate dispute reminders when responses are overdue.

Best practices

Store Razorpay credentials only in environment variables; never log the key secret.
Mask customer contact details and never display full card numbers; follow privacy rules by default.
Tune thresholds (large payment amount, failure spike count, polling window) to match your business volume.
Verify cron times are set to IST and adjust server timezone or cron offsets as needed.
Test with Razorpay test keys before switching to live keys in production.

Example use cases

Daily 8:00 AM IST report showing yesterday’s revenue, success rate, refunds, and settlement status sent to merchant WhatsApp group.
Immediate alert when three or more payments fail within 30 minutes, prompting engineering or payment-link checks.
Weekly Monday summary comparing revenue to the previous week and highlighting best-performing day.
On-demand command “failed payments” to retrieve the last 10 failed transactions and failure reasons.
Dispute reminder sent daily for disputes older than 5 days until action is taken.

FAQ

Set RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET in environment variables; the skill uses HTTP Basic Auth to call Razorpay endpoints.

Can I change alert thresholds and business hours?

Yes. Configure environment vars like RAZORPAY_LARGE_PAYMENT_THRESHOLD, RAZORPAY_ALERT_FAILURE_WINDOW_MINUTES, and failure spike count to match your needs.