Payments & Dunning
Last reviewed: 16 November 2026
This page explains how BillHive collects money and what happens when a payment fails.
Payment methods
| Method | Recurring? | Typical customer |
|---|---|---|
| Card | Yes, when saved for repeat charges | B2C |
| UPI | One-off | B2C |
| UPI Autopay | Yes, through a mandate | B2C in India |
| eNACH | Yes, through a bank mandate | B2B and high-value B2C in India |
| Net Banking, Wallet | One-off | B2C |
| Cash, Cheque, Wire Transfer | Recorded by hand | B2B |
Saved methods are on the customer page. See Payment Methods.
Mandates
A mandate is the customer’s standing permission for you to debit them. In India, UPI Autopay and eNACH mandates have a maximum amount. If an upgrade would push the debit above that limit, BillHive asks the customer to approve a new or raised mandate before it bills the upgrade. The change-mandate wait currently works with Cashfree only. See An upgrade on a mandate.
Payment gateways
| Gateway | Status |
|---|---|
| Cashfree | Available, with self-serve onboarding in the portal |
| Razorpay | Integration page available; self-serve onboarding is coming next |
See Gateway Onboarding.
How a payment is collected
An offline payment (cash, cheque, bank transfer) is recorded by an admin against the invoice. See Recording Offline Payments.
Payment reconciliation
Reconciliation means checking that every rupee the gateway settled matches a payment in BillHive, and every invoice marked Paid has a real payment.
In BillHive:
- Every payment is a transaction on the customer (Customers > Transactions).
- A payment is applied to invoices; any excess is an unapplied payment you can apply later. See Unapplied Payments.
- Settlement reports from the gateway are not imported. Match them against the Transactions list by gateway reference.
Failed payments
A payment can fail because of:
| Kind | Examples | Retried? |
|---|---|---|
| Soft decline | Insufficient funds, network error, limit exceeded | Yes |
| Hard decline | Card expired or stolen, account closed, fraud suspected | No immediate retry; the customer is asked to update the method |
Unknown reasons are treated as soft declines.
Dunning
Dunning is the process of recovering a failed payment: retrying, reminding the customer, and finally acting on the subscription. The subscription shows In Dunning while it runs.
Default schedule (configurable in Settings > Dunning):
If the payment succeeds at any point, by retry or by the customer paying through the link, dunning stops and the subscription goes back to Active.
| Effect | |
|---|---|
| Billing | No new charges for the failed invoice; retries charge the same invoice |
| Invoice | Stays unpaid, then Overdue; written off at the end |
| Subscription | In Dunning; can be cancelled immediately only |
| Notifications | Payment Failed, Payment Reminder, Urgent Notice, Account Restricted, Account Suspended, Final Notice, Cancelled (Non-Payment), Win-Back |
Example. A ₹2,360 renewal debit fails on 1 May with insufficient funds. Three quick retries fail. The customer gets the Payment Failed email, tops up their account, and the day-3 retry succeeds. Dunning ends; the subscription is Active.
Pausing dunning, skipping a retry and manual overrides are planned. See Dunning, Configure Dunning and Pending Features.
Beyond dunning: collection
For invoices dunning didn’t recover, BillHive has Promise to Pay, Write-off and Debt Collection Agencies.
Refunds
See Refunds.