A product head at an NBFC launches a virtual credit card tied to a UPI-linked credit line. The team maps its repayment schedule the usual way: a fixed due date, a flat instalment, the same logic as a personal loan. Three months in, delinquency tagging comes out wrong every few cycles, interest accrual doesn’t match the customer’s statement, and reconciling the app against the Loan Management System (LMS) eats hours every billing cycle. The product isn’t broken. The repayment plan underneath it was built for different credit, a mismatch Finezza sees often when NBFCs push revolving products onto term-loan infrastructure.
Key Takeaways
- Virtual credit cards draw down in many small transactions against a live limit, not one lump-sum disbursement like a term loan.
- Repayment runs on a revolving minimum amount due, recalculated each billing cycle, not a fixed Equated Monthly Instalment (EMI) schedule.
- Interest accrual depends on whether the prior cycle’s balance was cleared in full, not a rate fixed at sanction.
- Unpaid credit card dues and gross Non-Performing Assets (NPAs) in cards are both rising sharply in India, a segment virtual credit cards sit squarely inside.
- A repayment engine for virtual credit cards needs statement-cycle billing, configurable waterfalls, and NPA logic built around the minimum-due rule, not EMI.
The stress building in this segment makes that gap harder to ignore. Unpaid credit card dues rose 28.4% to Rs 6,742 crore in the twelve months to December 2024, per RBI data cited by the Fintech Association for Consumer Empowerment. Gross NPAs in credit cards climbed to 2.3% of total dues over the same period, up from 2.06% a year earlier. Active cards in India crossed roughly 111 million by mid-2025. A mismatched repayment engine stops being a back-office inconvenience once volumes and stress rise together, exposing any lender that can’t assess repayment capacity on a revolving product.
A Term Loan and a Virtual Credit Card Do Not Behave the Same Way
The differences start with how money moves into the account, and run through to how regulators expect it tracked.
One Disbursement Versus Many
A term loan draws down once, at sanction, against a fixed principal that amortises on a schedule set on day one. A virtual credit card has no single disbursement moment. Every transaction across a billing cycle is its own small drawdown against a live credit line, and the balance owed is the sum of many small drawdowns, not one amount. An LMS built for single or scheduled multi-disbursement term loans has to be re-architected, not just reconfigured, to treat each swipe as a drawdown against a revolving limit, a gap that shows the moment volumes scale.
A Fixed Instalment Versus a Revolving Minimum Due
Term loans repay through a fixed EMI set at sanction. Virtual credit cards repay through a Minimum Amount Due (MAD), recalculated every billing cycle. Issuers set it as the higher of full interest, fees and taxes, or 5% of total outstanding, plus any past-due or over-limit amount. RBI’s subsequent updates require the MAD to also include a fixed portion of principal, so cardholders can’t roll over the same balance indefinitely, though issuers vary in how they apply that share. An LMS that only generates a fixed EMI schedule can’t reproduce this without a separate module.
Interest That Depends on Last Cycle’s Behaviour
A term loan’s interest is set once, at disbursement, on a reducing or flat balance. A virtual credit card’s interest depends on what the customer did last cycle. Clear the full statement balance, and the next cycle stays interest-free. Miss it, even by paying only the minimum due, and interest reverts to accruing from each transaction’s original date, not the statement date. That’s a state machine, not a fixed rate, and a repayment engine built for term loans has no natural place to hold it.
A Credit Limit That Has to Refill Itself
When a borrower repays a term loan instalment, the outstanding book value simply falls. When a cardholder repays a virtual credit card balance, the available limit has to reopen in real time so the same credit line can be drawn on again. Term loan logic in most LMS platforms was never built to restore a limit; it was built to close a balance down permanently. Getting this wrong means a customer sees a restored limit in the app while the LMS still shows the old exposure, a mismatch collections teams chase manually.
What Changes Once Regulation Enters the Picture
Card accounts are classified as NPAs differently to term loans too. An account becomes an NPA if the minimum amount due goes unpaid for 90 days from the statement due date, regardless of any EMI schedule. Bureau reporting runs on a separate, shorter clock: under RBI’s 2026 amendments, issuers may only report an account as past due, or levy late fees, once more than three days of non-payment have passed. The two rules don’t overlap: one governs classification, the other reporting.
Term loan delinquency, by contrast, is tracked through Days Past Due (DPD) counted from a fixed instalment date. A lender running both products through one undifferentiated ageing logic risks missing the window to intervene before an NPA, and reporting wrong data to credit bureaus, in a segment regulators have already flagged.
Building a Repayment Engine That Matches How Virtual Credit Cards Work
A repayment engine for virtual credit cards needs statement-cycle billing instead of fixed EMI dates, a dynamic minimum-due calculation that mirrors the Reserve Bank’s formula, and day-wise interest logic that switches between interest-free and interest-bearing states. It also needs a configurable payment waterfall per product and bureau reporting that matches a card account’s own classification rules.
Finezza’s loan management system was built with configurable waterfall audits for this reason, and lists virtual credit cards and credit limit products alongside term loans as supported lines of business, with multi-disbursement handling built in. That distinction, one disbursement versus many, is where the mismatch starts.
FAQs
1. What makes a virtual credit card different from a term loan inside a Loan Management System (LMS)?
A term loan draws down once, against a fixed principal on a set schedule. A virtual credit card has no single disbursement moment. Every transaction in a billing cycle is its own small drawdown against a live credit line, so an LMS built for term loans needs re-architecting to treat each swipe as a revolving drawdown.
2. How is the Minimum Amount Due (MAD) calculated on a virtual credit card?
Issuers set the MAD as the higher of full interest, fees and taxes, or 5% of total outstanding, plus any past-due or over-limit amount. RBI’s updates require the MAD to also include a fixed portion of principal, so cardholders can’t roll over the same balance indefinitely, though the exact principal share can vary by issuer.
3. Why does interest on a virtual credit card depend on the previous billing cycle?
Clear the full statement balance, and the next cycle stays interest-free. Miss it, even by paying only the minimum due, and interest reverts to accruing from each transaction’s original date, not the statement date. That’s a state machine tied to last cycle’s behaviour, not a fixed rate set at disbursement like a term loan’s interest.
4. How does NPA classification differ between credit cards and term loans?
An account becomes an NPA if the minimum due goes unpaid for 90 days from the statement due date. Bureau reporting runs on a separate clock: under RBI’s 2026 amendments, issuers can only report an account as past due after three days of non-payment. Term loans track delinquency through Days Past Due (DPD) from a fixed instalment date.
5. Can a single LMS handle both term loans and virtual credit cards?
Only if it supports statement-cycle billing, a dynamic minimum-due calculation, and day-wise interest logic that switches between interest-free and interest-bearing states. It also needs a configurable payment waterfall per product, rather than one fixed sequence for every loan type. That kind of platform typically lists virtual credit cards alongside term loans as supported lines of business.
Conclusion
Forcing a virtual credit card through a repayment plan built for term loans isn’t just a monthly reconciliation headache. It’s misclassifying risk on a segment where NPAs are already rising faster than the rest of the unsecured book, right when regulators are watching closely. Getting the repayment engine right, statement-cycle billing, a dynamic MAD, stateful interest logic, and NPA rules that match the product, isn’t a nice-to-have. It’s the difference between a lending book regulators trust and one they flag.
If your LMS still runs virtual credit cards through a term-loan repayment plan, the mismatch usually traces back to disbursement logic, MAD calculation, interest-state tracking, or NPA classification. Finezza’s loan management system treats this as configurable, product-specific logic, not one fixed template. Book a demo to see how it handles revolving credit lines alongside term loans.
Leave a Reply