Collection Suite
Static and dynamic QR, shareable payment links, virtual accounts and UPI collect requests — every inbound rupee arrives tagged to the right customer and invoice.
Capabilities
6 endpoints and counting
- QR (Static & Dynamic)
- Payment Links
- Virtual Accounts
- UPI Collect
- Auto Reconciliation
- Partial Payments
/v1/collections/linkscurl https://api.rupeeco.in/v1/collections/links \
-H "Authorization: Bearer $RUPEECO_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount": 499000,
"reference": "INV-2026-0455",
"channels": ["upi", "card", "netbanking"],
"notify": { "sms": true, "whatsapp": true }
}'Designed around how this actually breaks
A virtual account per customer
Unique IFSC-addressable accounts mean bank transfers self-reconcile against the right ledger the moment they land.
Links that convert
Send over WhatsApp, SMS or email with expiry, part-payment rules and automatic reminders.
Real-time webhooks
Signed events on every credit so your ERP updates without polling.
Common collection suite use cases
Every deployment starts with a call about your flows. Bring your edge cases — routing rules, approval chains, reconciliation formats — and we will map them before you write a line of code.
Discuss your use caseOffline and field collections
B2B invoice collections
Rent, fees and subscription dues
Pairs well with
Same key, same dashboard, same webhook signature — add another suite without another integration.
Start with sandbox keys. Talk commercials when you are ready.
Test the full API surface before you sign anything. When you are ready to go live, we price on the volume you actually process.
Map your flows
A solutions engineer walks through your money-in, money-out and verification requirements and proposes the shortest path live.
Test in sandbox
Pull keys, replay real-world scenarios and validate webhooks against a sandbox that mirrors production behaviour.
Go live and scale
Switch to production keys, turn on routing rules, and add new suites from the marketplace whenever you need them.
