What “supported” means
Supported means Glass Money knows the bank or card issuer sender domains, can fetch likely alert mail with read-only inbox access, and has extraction/reconciliation paths for turning those alerts into transaction rows. It does not mean every account at that bank emails every transaction by default.
Some issuers have curated exact sender addresses from known alert history. Others are fetched through official-domain sweeps until enough real alert senders are verified. Domain sweeps are deliberately filtered downstream so promotional and security mail does not become transactions.
Coverage matrix
Start with the accounts you use: HDFC card and RuPay UPI spending, ICICI account and card activity, or Kotak 811 alongside your salary bank. Each page explains the available alert evidence and what may be missing. Issuers without a dedicated page still appear in the matrix when sender domains are registered.
| Bank or card issuer | Current coverage | Important note |
|---|---|---|
| HDFC Bank | Curated alert and statement senders | Savings, card, and statement sender addresses are narrowed from known alert history. |
| State Bank of India | Official-domain sweep | Savings/CBS and legacy alert domains are fetched broadly; formats vary by product. |
| SBI Card | Curated alert and statement senders | Card subsidiary with exact sender coverage; separate from SBI savings/CBS domains. |
| ICICI Bank | Curated alert, card, statement, and FASTag senders | Includes ICICI Bank and icici.bank.in sender variants. |
| Axis Bank | Curated alert and statement senders | Includes Axis account, card, and statement sender patterns. |
| Kotak Mahindra Bank | Official-domain sweep | Used until enough production alert senders are curated safely. |
| Punjab National Bank | Official-domain sweep | No curated production sender sample yet; extraction rejects non-transaction mail. |
| Bank of Baroda | Official-domain sweep | Covers current and legacy Bank of Baroda domains while alert samples are curated. |
| Yes Bank | Official-domain sweep | Includes Yes Bank legacy and RBI .bank.in alert domains. |
| IDFC FIRST Bank | Curated documented and observed senders | Includes transaction-alert, noreply, and statement sender variants. |
| IndusInd Bank | Curated alert and statement senders | Transaction-alert and credit-card statement senders narrowed from known alert history. |
| American Express India | Card-only domain sweep | No curated production sender sample yet; promotional mail is filtered downstream. |
| OneCard | Card-only domain sweep | Transactional alert sender not yet observed; domain fetch keeps formats discoverable. |
| HSBC India | Official-domain sweep | Includes hsbc.co.in and RBI hsbc.bank.in domains while alert senders are curated. |
| AU Small Finance Bank | Curated alert and statement senders | Account and credit-card alert senders narrowed; marketing subdomains excluded. |
| SBM Bank India | Curated alert and statement senders | Known alert and statement addresses; extraction still rejects non-transaction mail. |
| Federal Bank (incl. Scapia cards) | Curated Scapia card senders | Scapia card alerts on Federal Bank domains; broader Federal account formats vary. |
How coverage and reconciliation are measured
Bank support and an individual user's coverage are different claims. The matrix above records which sender-discovery strategy is active. In private beta, users declare the accounts they want included; an account is current only when it has a recent successful source, and the full view remains incomplete while any included account is stale, missing, or explicitly incomplete.
Reconciliation is tested with anonymized fixtures for overlapping alerts and statement rows, transfers between owned accounts, repeated imports, missing alert periods, and sender-format changes. We do not publish a production accuracy percentage until there is a sufficiently large, representative, consent-safe denominator. Coverage state and source provenance remain private-beta capabilities, not a guarantee of complete public-beta history.
Prerequisites
- The bank or card issuer must send transaction alerts to the inbox you connect.
- The alert must contain enough transaction detail: amount, direction, date or time, and a merchant or reference hint.
- SMS-only accounts need email alerts enabled or manual entries; SMS import is not available yet.
- Compare imported activity against your own bank records. Statement upload is not available in the current public beta.
Troubleshooting
Search your inbox for a missing amount first. If the alert is not there, enable email alerts in the bank app or net-banking portal. If the alert exists but came from a new sender or template, share a redacted example with support so we can add the format. If the transaction only exists in your bank records, add it manually and check for an existing entry first.