Skip to content
Suite 03 · Get paid on every channel

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
POST/v1/collections/links
curl 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 }
  }'
What makes it different

Designed around how this actually breaks

1

A virtual account per customer

Unique IFSC-addressable accounts mean bank transfers self-reconcile against the right ledger the moment they land.

2

Links that convert

Send over WhatsApp, SMS or email with expiry, part-payment rules and automatic reminders.

3

Real-time webhooks

Signed events on every credit so your ERP updates without polling.

Where teams use it

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 case
01

Offline and field collections

02

B2B invoice collections

03

Rent, fees and subscription dues

Pairs well with

Same key, same dashboard, same webhook signature — add another suite without another integration.

Try first. Subscribe later.

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.

1

Map your flows

A solutions engineer walks through your money-in, money-out and verification requirements and proposes the shortest path live.

2

Test in sandbox

Pull keys, replay real-world scenarios and validate webhooks against a sandbox that mirrors production behaviour.

3

Go live and scale

Switch to production keys, turn on routing rules, and add new suites from the marketplace whenever you need them.