First-party sources come first
The same evidence rule applies across cards, bank accounts, deposits and digital banking. We prioritize bank or issuer product pages, fee schedules, key-fact or terms documents, official FAQs and official change notices. For credit cards specifically, Most Important Terms & Conditions and Key Fact Statements are treated as important controlling sources where applicable.
Different banking products need different evidence
A credit card may require rewards, fee, lounge and MITC documents; an account may require a schedule of charges, balance rules and account terms; a premium banking programme may require relationship-value criteria, programme fee treatment, bundled-card rules and downgrade terms; a deposit may require a dated interest-rate table and premature-closure terms; digital banking may require bank-published limits, registration and security documentation. We do not force every product into a credit-card data shape.
Product pages are not enough by themselves
Third-party summaries are not used to overwrite conflicting first-party terms. For cards with changing lounge, reward, forex or application rules, we also check the issuer's current FAQs, membership kits, fee schedules and change notices. When first-party pages disagree, the more specific and newer controlling document takes priority and the conflict is held for editorial review.
One card can require several issuer documents
Where fees, reward earn, lounge rules and forex pricing are split across different first-party documents, the card page can expose a primary source plus additional issuer evidence. We do not imply that one marketing page proves every term.
We separate facts from interpretation
Annual fee, reward rate, lounge access and forex markup are recorded as terms. Whether that combination is useful depends on the reader’s real spending and benefit usage.
Comparison pages must add decision value
Curated comparison URLs are not indexable merely because two products exist. Cards must expose multiple substantive differences across decision fields, while specialized banking-service pairs can also qualify through type-specific controls such as UPI limits, beneficiary cooling, settlement, ATM rules, DCC, merchant pricing or forex-card mechanics. Non-curated and future low-difference pairs remain non-indexable.
Incomplete pages stay out of the index
A tracked card, debit card or account can exist in the research database without becoming a public search-engine page. We publish only when first-party evidence supports a useful product-level decision.
Dates matter
Each published product displays a review date. Banking terms can change after that date, so the current bank or issuer agreement remains controlling.
Deposit tenure points are stored, not inferred
For fixed and recurring deposits, the engine can store comparable tenure anchors such as 12, 24 or 48 months when the first-party rate table explicitly supports them. We do not interpolate missing tenures or rank a bank from an unrelated promotional maximum. Effective dates remain attached to the stored schedule.
NRI deposits are three different decision states
The NRI Deposits hub keeps NRE, NRO and FCNR(B) term deposits separate. NRE and NRO are rupee deposits with different permitted funding, tax and repatriation treatment; FCNR(B) remains denominated in a permitted foreign currency. A shared bank label such as “NRI FD” never erases those differences.
FCNR(B) rates are currency-by-tenure data
Foreign-currency deposit rates are stored in a separate currency-rate table rather than in the ordinary INR tenure finder. A USD, GBP, EUR or AUD percentage is meaningful only with its currency, tenure, amount band and effective date attached. “No quote” stays blank rather than being filled by interpolation.
NRI senior-citizen additions are evidence-gated
Several bank rate pages publish one Domestic/NRO/NRE table beside a resident senior-citizen column while explicitly saying the senior addition does not apply to NRIs. NRE/NRO profiles therefore store the NRI-eligible general rate and leave the senior field empty instead of inheriting an unavailable resident benefit.
Temporary FCNR swap-window pricing is not evergreen
Where a bank links unusual long-tenure FCNR rates, lock-ins or penalties to a dated RBI swap facility or a named temporary scheme, the engine tags that pricing as special and keeps it out of ordinary FCNR rate anchors. When the window ends, historical evidence remains historical rather than silently becoming the normal product rate.
Non-callable NRI deposits are a separate liquidity class
A higher non-callable rate is never merged into the ordinary callable NRE/NRO ladder. Deposit Plus products keep their minimum amount, no-preclosure condition and separate effective-date schedule attached to the product so a reader can see that the extra yield is purchased by giving up liquidity.
NRI recurring deposits keep their account state
NRE and NRO recurring deposits are stored separately where the bank publishes different tenure, tax, funding or repatriation rules. Monthly instalment amount, permitted increments, grace/default rules and premature closure are compared independently from the headline rate.
Forward-cover deposits are not ordinary fixed deposits
When the economic return combines a term deposit with a forward contract, the engine labels the product as structured/forward-cover and excludes it from ordinary INR or FCNR rate rankings. The transaction-date forward premium, exchange-rate path and cancellation terms are part of the product and cannot be represented by one evergreen deposit percentage.
Conflicting first-party sources
Issuer websites can temporarily disagree with their own MITC, KFS, fee schedule or older rewards copy. We do not silently pick the most favorable number. Where the conflict affects a decision, the profile either uses the clearly newer controlling disclosure or surfaces the disagreement and tells the reader which application/KFS document should control.
Temporary offers and announced future changes
Where an issuer clearly labels a fee as a limited-period offer or announces a future-dated term change, we preserve that qualification instead of converting it into a permanent claim. This is especially important for lifetime-free offers, lounge rules and forex changes.
Zero balance is not one product type
The Basic & Zero-Balance hub separates full-KYC Basic Savings Bank Deposit Accounts, PMJDY/basic propositions, relaxed-KYC Small Accounts and commercial zero-balance or digital savings plans. A zero minimum balance alone does not prove zero opening funding, a free debit card, the same withdrawal allowance, the same ownership restrictions or the same eligibility. We store minimum-balance rules, initial funding and card cost as separate decision fields rather than collapsing them into one “zero balance” label. Products can appear in both the general savings hub and this decision hub through one canonical product profile rather than duplicate pages.
Small Accounts have statutory operating caps
Where a bank publishes a relaxed-KYC Small Account, we record the current balance, aggregate-credit and aggregate-withdrawal/transfer ceilings separately from ordinary BSBDA rules. These caps are operating restrictions while KYC remains incomplete; they are not recommendations, card limits or generic limits for every zero-balance account.
Minor and student accounts use age-state modelling
The Minor & Student hub distinguishes guardian-operated minors, self-operated minors and adult student schemes instead of treating “youth account” as one product type. We store the bank-published age threshold, guardian/consent rule, digital rights and student-status requirement because they can change who is legally or operationally able to use the account.
Child-specific card limits override generic card-family limits
A bank may use a familiar Visa Gold, Visa Platinum or other card family while publishing a much lower limit for the linked child account. In that case the relationship-specific child limit is controlling in youth comparisons. We do not copy an adult card limit into a minor account simply because the network/card family name matches.
Majority and student age-out are lifecycle events
Where first-party terms explain what happens at age 18 or at a student-scheme cutoff, we record re-KYC, fresh-signature requirements, debit restrictions, automatic conversion and the balance/fee rules that take over. A low-cost youth account is not presented as permanently low-cost if its economics change at the age boundary.
Discontinued youth products are not active comparators
If a bank explicitly marks a minor/student product as discontinued, legacy terms can remain useful historical evidence but the product is not published as a current comparison candidate. This prevents stale youth account pages from inflating apparent market coverage.
Youth accounts can be scheme-specific rather than general-purpose
A school-linked, government-supported or early-childhood account is not automatically comparable to a general minor savings account. We keep course status, school category, scheme exclusions, age band, guardian/card-holder identity and statutory-style transaction caps attached to the product so a narrow scheme such as NSIGSE or a child-under-12 savings plan is not presented as a universal youth account.
NRE and NRO are different account states
NRI research starts with the regulatory purpose of the account rather than the bank’s marketing tier. NRE is generally used for eligible overseas earnings/remittances and is repatriable, while NRO is used for Indian-source receipts and operates under a different tax and outward-remittance framework. A bank may sell both under one programme, but the engine keeps the account state explicit in the product summary, limits and relationship fields.
Repatriability and tax are controlling fields
Repatriability is not treated as a generic benefit score. NRE principal and interest and NRO outward remittance follow different RBI/FEMA rules, and NRO tax withholding can depend on current law, residential status, treaty eligibility and documents. We therefore avoid hard-coding stale tax percentages where a durable description is more accurate, while preserving the bank’s current first-party wording and review date.
Zero opening balance does not prove zero ongoing balance
NRI onboarding pages can say an account may be opened with zero balance while a separate tariff lists MAB, relationship value or non-maintenance charges. When first-party sources conflict, the engine exposes the disagreement and directs the reader to the live KFS/application terms instead of silently choosing the most attractive interpretation.
NRI debit-card geography belongs to the relationship
A card family can behave differently depending on whether it is linked to NRE or NRO. Where a bank explicitly names the variant, we preserve account-specific ATM/POS limits, international availability, fees and domestic-only restrictions in a verified relationship edge. Generic mentions such as “international debit card” or “domestic debit card” remain account attributes unless the exact variant is identifiable.
Residency status is a lifecycle event
NRI accounts are not permanent labels detached from residential status. Resident accounts may require redesignation to NRO when the holder becomes non-resident, and NRE/NRO accounts require appropriate redesignation when the holder returns and becomes resident. The engine treats this as an operating condition, not a footnote.
Tax-saving FDs use the 2026 tax-law numbering
For Tax Year 2026-27 onward, the Income-tax Act, 2025 applies. The Income Tax Department explains that deductions historically referenced as Section 80C are now referenced through Section 123 read with Schedule XV. Some bank product pages still use the legacy Section 80C label; the engine preserves that as source wording but maps the current legal numbering for 2026 onward.
The deposit amount can qualify; the interest is not tax-free
Section 123 retains the ₹1.5 lakh aggregate deduction framework for specified savings instruments for eligible individuals/HUFs, but the deduction is not available under the new concessional regime under Section 202. A qualifying tax-saving FD can support the deduction only within the applicable aggregate ceiling and regime; interest earned on the FD remains taxable and can be subject to TDS. Product research is general information, not individual tax advice.
A tax saver is not an ordinary callable five-year FD
The engine labels tax-saving deposits as a separate locked structure. Five-year lock-in, no-normal-preclosure, lien/loan restrictions, first-holder rules, death exceptions and bank-specific maturity/auto-renewal instructions stay attached to the product. A higher special-tenure rate such as a 444-day or 555-day offer is never substituted for the exact five-year tax-saver rate.
Government-backed savings are not bank FDs
SCSS, PPF, Sukanya Samriddhi, KVP and Floating Rate Savings Bonds can be serviced by banks, but their core rate and scheme rules are set by the Government of India or, for FRSB operational mechanics, the Government/RBI framework. The engine therefore publishes them under a separate Government Savings silo and does not let their yields enter the ordinary bank-FD rate finder.
One government rate table can create different contracts
A quarterly small-savings notification does not mean every scheme behaves the same after opening. SCSS and KVP can preserve the rate applicable to a newly opened account/certificate under their scheme mechanics, while PPF and Sukanya balances use rates reviewed by Government over time. FRSB is different again: its coupon resets every six months from the prevailing NSC rate plus 35 basis points.
Government scheme eligibility is a controlling term
A higher published yield is not a universal offer. SCSS uses age and retirement conditions; Sukanya is tied to an eligible resident girl child; PPF has account-holder and residency restrictions; KVP and FRSB use their own holder rules. Comparison pages surface those restrictions before yield.
Government backing does not mean instant liquidity
Each scheme keeps its own maturity, extension, premature-close, loan, collateral and withdrawal rules. SCSS has time-based preclosure deductions, PPF has prescribed loan/withdrawal windows, Sukanya has education/marriage/compassionate grounds, KVP has a normal 2-year-6-month lock before premature closure, and FRSB early redemption is age-restricted.
Tax treatment is stored separately from the headline rate
The engine does not use “tax saving” as a generic label. PPF and Sukanya have different exempt-interest/maturity treatment from taxable SCSS and FRSB interest, while KVP principal is not modeled as a Section 123 / Schedule XV qualifying deduction. Any qualifying deduction remains subject to the current aggregate ceiling, eligible taxpayer and tax-regime rules.
Formula-derived government rates are marked as derived
FRSB publishes a reset formula of prevailing NSC plus 35 basis points. When the current NSC rate is available from the Government small-savings notification, the engine can calculate the current half-year coupon and labels it as formula-derived. It does not claim that a bank independently published that calculated number.
Service-channel evidence does not create a bank-specific yield
A Bank of Baroda, SBI or other authorized page can prove that a customer may open or service a Government scheme through that institution. The canonical scheme profile keeps that verified service route while treating the Government notification/rule as controlling for scheme economics, which avoids duplicate pages that imply different bank versions of the same government rate.
One canonical Government scheme can have many verified service routes
The service matrix is an access layer, not a product-duplication engine. PPF opened at SBI, HDFC, ICICI, PNB or Bank of Baroda remains the same Government PPF scheme; bank evidence is used only to verify whether opening is branch-based or digital, what servicing is available and whether the bank documents transfer handling.
Digital availability is evidence-gated and conflicts stay visible
A bank listing a scheme does not prove online opening. We separately verify branch opening, digital opening, digital funding/viewing and inter-provider transfer. If current first-party pages disagree—for example one page says online opening is under development while another app page advertises it—the matrix marks a source conflict and tells the reader to verify the live channel.
Government rate history uses the notification period
SCSS, PPF, Sukanya and KVP are preserved quarter by quarter from Government/DEA evidence even when the rate is unchanged. A flat rate history is not collapsed away because repeated continuation notices are themselves evidence. FRSB remains outside that quarterly table because its coupon resets every six months under the NSC-plus-35-basis-point formula.
Digital account opening is a separate evidence layer
An account being digitally manageable does not prove it can be opened end-to-end online. The engine separately stores the opening channel, Aadhaar/PAN requirements, Video KYC/V-CIP, device/location conditions, funding step, new-to-bank restriction, fallback route and any limited-KYC state. The canonical page remains the underlying savings account; digital-account-opening is secondary discovery rather than a duplicate product URL.
Online application is not the same as end-to-end digital opening
The engine distinguishes a self-serve full-KYC journey from a digital lead/application that still requires bank-assisted verification. If the current bank page says a representative will contact the applicant after form submission, that route is labeled assisted rather than being upgraded to Video KYC from older marketing material.
Digital card mapping can be source-conflicted
A digital-account page can name a debit-card variant while the bank's current card catalogue says new issuance of that variant has stopped. In that situation the account keeps the documented card wording and the conflict is surfaced, but the relationship graph does not guarantee an obsolete physical-card endpoint until the replacement mapping is clear.
Zero balance does not mean zero opening funding
Initial funding is kept separate from ongoing AMB/AQB and from debit-card fees. An account can legitimately have zero minimum balance while asking for money during onboarding; that money can remain the customer’s usable balance rather than being a fee. Comparisons surface those concepts separately.
Minimum KYC and full Video KYC are not interchangeable
Where a bank documents an Aadhaar-OTP or minimum-KYC account before full V-CIP, the engine preserves the validity, balance and transaction restrictions until full KYC is completed. A completed Video-KYC account is not described using the restricted limits of the earlier minimum-KYC state, and a limited account is not described as fully unrestricted.
New-to-bank and location rules control digital eligibility
Some instant routes exclude existing or even former customers, and Video KYC commonly requires the applicant to be physically present in India with a camera-enabled device and Aadhaar-linked mobile. These are treated as controlling eligibility terms rather than buried UX details.
Digital channel availability is not one comparable feature
The engine separates mobile apps, Internet Banking and account-opening journeys. A bank can support all three while using different registration, transaction-right, beneficiary, device and transfer-limit controls in each channel.
Transfer limits keep their scope
A limit is stored with the rail and channel that produced it. A mobile IMPS daily cap is not reused as a NetBanking NEFT limit, a customer-configurable maximum is not described as a guaranteed per-transaction allowance, and temporary post-registration limits stay separate from steady-state limits.
Cooling periods are security states, not footnotes
New beneficiary, new device, password/profile change and first-use controls can temporarily block or reduce transfers. Where first-party bank pages disagree on the duration or amount, the conflict is surfaced and the live transaction screen/current terms control.
App capability is verified beyond payments
Digital-service profiles also track card controls, statements, deposits, cheque/service requests, lock/deregistration and recovery. A bank marketing hundreds of services is not given credit for a specific control unless the reviewed source actually documents it.
UPI system ceilings are not bank guarantees
The engine stores the limit with its scope: remitter bank/app, funding source, transaction direction and use case. NPCI/RBI can permit a higher ceiling for selected categories while a bank, issuer or customer-set risk control remains lower. The site therefore does not present one universal UPI daily limit.
UPI cooling is a temporary security state
Registration, device/SIM/mobile changes and PIN resets can reduce value or transaction count for 24 hours, 72 hours or another bank-defined period. These controls are displayed next to—but never merged into—the steady-state limit.
UPI Lite uses current system limits, not stale launch copy
The current RBI framework allows ₹1,000 per eligible UPI Lite transaction and ₹5,000 total stored balance. If a bank article still shows an older ₹500/₹2,000 launch-era figure, the conflict is preserved and the updated RBI/NPCI framework is treated as controlling unless the bank explicitly imposes a stricter current limit.
RuPay credit-card UPI is a separate funding rail
Linking a RuPay credit card to UPI does not turn the card into a bank-account P2P source. NPCI excludes P2P, P2PM, card-to-card and merchant cash-withdrawal flows; the usable amount is constrained by the lowest applicable issuer card limit, issuer UPI risk limit and customer-set card limit.
UPI AutoPay and delegated payments stay separate
A recurring UPI mandate has its own authorization, pause, revoke, modify and pre-debit lifecycle. UPI Circle/delegated access is also distinct from account ownership: a secondary user can receive delegated payment authority without becoming the owner of the primary user’s account. Under the current NPCI Full Delegation framework reviewed here, the primary can set a monthly delegation limit up to ₹15,000 with up to ₹5,000 per transaction; Partial Delegation instead lets the secondary initiate while the primary completes authorization with UPI PIN. Those system rules do not prove that every bank/app has launched UPI Circle, so bank-level support is published only when first-party evidence confirms participation.
Incoming UPI limits are not outgoing limits
Where a bank publishes a separate P2P-inward transaction-count or value rule, it is stored as an incoming control and is never used to raise the customer’s send-money allowance.
NEFT, RTGS and IMPS are separate rails
NEFT is an RBI-operated retail system settling in half-hourly batches, RTGS settles eligible transfers individually in real time with a ₹2 lakh minimum, and IMPS is an NPCI instant-payment system with a ₹5 lakh per-transaction system ceiling for ordinary channels. The engine stores those system mechanics before applying any bank limit.
Bank and channel limits can be lower than system capacity
RBI places no single-transaction floor or ceiling on NEFT and no upper ceiling on RTGS, but that does not make transfers unlimited for a customer. Mobile, Internet Banking, account scheme, customer-set third-party limits, segment status and temporary risk controls remain separate bank-level constraints.
Beneficiary cooling stays attached to the rail
A newly added beneficiary can be inactive for minutes or hours and can then remain subject to a lower first-day or multi-day amount cap. If the bank gives RTGS a stricter waiting period than NEFT/IMPS, that rule is retained rather than summarized as one generic beneficiary cooling period.
Transfer charges keep channel and account scope
A bank can waive online NEFT/RTGS for savings accounts while charging branch remittances or IMPS, and a premium/basic/salary/current account can have its own waiver. The engine therefore stores the tariff with its channel and account scope and surfaces first-party conflicts when two current bank pages disagree.
Fee ledgers keep scope and effective dates
A fee row is stored with its bank, product or relationship scope, service channel, amount or formula, effective-from state and first-party source. Standard Savings pricing does not overwrite Basic, Salary or Premium waivers, and an announced future tariff remains future-effective until its start date. A notice that announces a revision without the changed amount is treated as a refresh trigger rather than permission to guess.
Transaction-limit ledgers preserve scope and period
Each normalized limit row keeps the bank, product or customer segment, channel, rail/use case, limit type, rupee amount or count, period, temporary security state, effective state and first-party source. Per-transaction maxima are never silently promoted to daily limits, overall app ceilings do not raise lower UPI/IMPS/card limits, and system-level RBI/NPCI capacity is not presented as a bank guarantee. Current source conflicts remain independently scoped until reconciled.
Business banking entitlements are role and service specific
Corporate Internet Banking, maker-checker or multi-authorisation, bulk files, cash management, merchant acquiring, virtual accounts, APIs, ERP/host-to-host connectivity and trade modules are recorded separately. A current account or business-banking login is not treated as proof that every module is enabled. Corporate limits and pricing can be customer-, account-, role- or contract-specific, so unpublished universal ceilings and fee waivers are not inferred from retail banking or from another business product.
Merchant acceptance keeps rail, settlement and pricing scope
UPI QR, Bharat QR, card POS, Soundbox, payment links and online gateways are stored as separate acceptance capabilities. Real-time payment confirmation is not automatically real-time bank settlement; UPI settlement wording is not reused for cards; MDR, device rental and installation charges remain tied to the exact merchant product; and account-tier POS/Soundbox waivers stay attached to the qualifying account. Refund, void, chargeback, reconciliation, sub-merchant and integration controls are likewise published only when the merchant source supports them.
International debit-card evidence separates activation, forex and DCC
An international-capable debit card can still have international usage switched off, and domestic-only variants are never promoted to overseas-capable because another card at the same bank supports it. Overseas ATM fixed fees, foreign ATM-owner surcharges, network currency conversion, bank foreign-currency markup and Dynamic Currency Conversion are kept separate. Card-variant/customer limits remain distinct from overseas acquirer limits and RBI/FEMA permissible-use rules. When a current bank travel page conflicts with an effective-dated debit-card tariff, both sources stay visible and the dated tariff controls only where its effective wording is explicit. Credit-card or prepaid-forex fees never fill an ordinary debit-card evidence gap.
Forex prepaid cards separate load-time exchange from later card costs
A prepaid travel card is researched as a foreign-currency wallet product, not as an ordinary debit card. Currency-wallet count, purchase/KYC eligibility, load/reload rate and fee, same-wallet merchant use, overseas ATM fee, cross-currency conversion, wallet-to-wallet conversion, inactivity/expiry, encashment/refund, replacement/emergency support and FEMA/RBI purpose limits are stored separately. When two current first-party artifacts disagree—such as an issuance fee or live supported-currency set—the conflict stays visible and the site does not silently select the cheaper or broader claim.
Lounge access is an effective-dated card relationship
Domestic airport, international airport and railway lounge access are stored separately against the exact eligible card, not against the bank name. Visit quotas, spend or relationship-value qualification, qualification period versus access period, Priority Pass/network programme, voucher/card validation, primary/add-on/guest treatment and effective/discontinued state remain independent fields. A network benefit does not create an issuer entitlement when the bank is silent, and an old lounge promise stays historical after a current issuer source discontinues it.
Explicit product relationships
Products sharing a bank are not automatically treated as bundled or mutually eligible. A product-to-product relationship is published only when first-party bank evidence explicitly says one product is included, issued, recommended, required or available with the other. That relationship keeps its own evidence URL, review date and qualification wording so it can be revised independently of either product profile.
Generic debit-card access is not a named-card relationship
If a bank only says “ATM card”, “debit card” or “ATM-cum-Debit Card” without identifying the exact variant, the account page can record that card access and fee treatment but the relationship graph does not invent a named endpoint. We create an account-to-card edge only when first-party material identifies the specific card or a sufficiently exact scheme variant, such as PNB RuPay PMJDY.
Relationship, invite-only and secured cards
Some Indian cards are available only through a banking relationship, invitation or linked fixed deposit. We keep that eligibility context attached to the card instead of presenting relationship-linked fee treatment as a universal public offer. Where a card is secured, the deposit relationship and current minimum-deposit rule are treated as decision-relevant terms.
Card visuals
The site uses a neutral symbolic credit-card icon rather than reproducing physical card artwork. The icon is an interface cue only: it does not represent the card's real colour, network branding, material or design. Fees and benefits come from the cited first-party issuer evidence.
Material changes stay visible
When a confirmed change materially affects the decision—such as fees, reward rules, lounge access, forex pricing, eligibility or application status—we can publish it in the card's change history and the site-wide updates ledger. A routine recheck that finds no material change updates freshness without creating artificial changelog noise.
How verification is shown
Each published banking product links the first-party bank, issuer, regulator or payment-system material used for that profile. We label the evidence type where possible — product page, Key Fact Statement, MITC, fee schedule, reward terms, lounge terms or other issuer document — and show the term areas checked on the review date. A first-party-verified label means the profile was checked against those linked primary sources; it is not an endorsement by the bank, regulator or payment-system operator.
No approval predictions
We do not estimate individual approval odds or promise credit limits. Issuers apply their own underwriting and documentation policies.