FAQs & Troubleshooting

Yes. You need an active Razorpay account and API keys. There are two types of API keys:

• Test Mode (rzp_test_*): Free, no KYC needed, for development.
• Live Mode (rzp_live_*): Requires completed KYC, for production.

Generate keys from

Start with test mode for safe development.

View

Currently, the node uses a polling approach to monitor payment events. You can set up automated workflows using the Cron node to check for new payments at regular intervals: Polling Workflow:
Cron (every 5 min) → Fetch Payments (last 5 min) → IF (new payments exist) → Process payments Implementation Steps:

1. Add Cron node (set interval: every 2-5 minutes).
2. Add Razorpay node (Fetch All Payments operation).
3. Use date filters: from = last check time, to = now.
4. Add IF node to check if results exist.
5. Process new payments in subsequent nodes.

This approach provides near real-time monitoring (2-5 minute delay) and works reliably for most use cases.

Critical: Razorpay requires amounts in paise (smallest currency unit).

Conversion:

• ₹1 = 100 paise
• ₹100 = 10,000 paise
• ₹1,500 = 150,000 paise

Example: To create a ₹500 Payment Link, use amount: 50000.

Use count (max 100) and skip parameters:

Example - Fetch 300 Payments:

• Page 1: count: 100, skip: 0
• Page 2: count: 100, skip: 100
• Page 3: count: 100, skip: 200

Implementation:

1. Use Loop Over Items or Split in Batches node.
2. Increment skip by 100 each iteration.
3. Add Wait node (1-2 sec) between pages to avoid rate limits.

Troubleshooting Steps:

1. Verify Installation.
   bash

   copy

   npm list @razorpay/n8n-nodes-razorpay

2. Restart n8n:
   bash

   copy

   pm2 restart n8n  # or systemctl restart n8n

3. Enable Community Nodes:
   • Settings → Community Nodes → Toggle ON
4. Clear Browser Cache.
5. Check Version: Minimum n8n v1.104.2
   bash

   copy

   n8n --version

Common Causes:

• Incorrect Key id or Secret (typos, spaces).
• Keys regenerated in Dashboard (old keys invalid).
• Wrong environment (test keys with live data or vice versa).

Fix:

1. Verify keys in Razorpay Dashboard → Account & Settings → API Keys.
2. In n8n, go to Settings → Credentials.
3. Edit your Razorpay credentials and update both Key and Secret.
4. Ensure no leading/trailing spaces.
5. Test connection.

Still failing? Generate new keys and try again.

Common Causes:

• Missing required fields (amount, currency for Payment Links).
• Wrong amount format (rupees instead of paise).
• Invalid field values.

Fix:

1. Check the error message for the specific field name.
2. Verify required parameters:
   • Create Payment Link: amount (paise), currency required.
   • Amount must be an integer in paise: ₹100 = 10000.
3. Check

   Operations Reference

   for required fields.

Example: For ₹1,500 Payment Link, use amount: 150000, not 1500.

Common Causes:

• Incorrect id format or value.
• Resource in a different environment (test vs live).
• Resource from a different Razorpay account.

Fix:

1. Verify id format:
   • Payment: pay_*.
   • Order: order_*.
   • Refund: rfnd_*.
   • Payment Link: plink_*.
2. Ensure API keys match resource environment (test/live).
3. Copy id directly from Dashboard or previous workflow output.

Common Causes:

• Too many API calls in a short period.
• Polling interval too short.
• Multiple workflows hitting the same endpoints.

Fix:

1. Add Wait node (1-2 seconds) between operations.
2. Use Split in Batches for bulk operations.
3. Increase polling interval (5-10 minutes instead of 1 minute).
4. Use pagination: Fetch max 100 items per request.
5. Contact Razorpay support for higher limits if needed.

Common Mistakes:

• Entering amount in rupees instead of paise.
• Not rounding decimal values.
• Currency mismatch.

Examples:

• ₹1 → 100 paise
• ₹100 → 10,000 paise
• ₹1,250.75 → 125,075 paise (rounded to 125,075)

Common Causes:

• Fetching too much data without pagination.
• Network connectivity issues.
• API is experiencing high load.

Fix:

1. Use Pagination:
   • Fetch max 100 items per request.
   • Use count and skip parameters.
2. Increase Timeout: Adjust workflow timeout in n8n settings.
3. Check Network: Verify connectivity to api.razorpay.com.
4. Add Retry Logic: Use Error Trigger node to catch and retry failures.