The current development parser bundle contains 32 message templates across eight institutions. Templates cover a mix of card purchases, account debits/credits, transfers, ATM withdrawals, deposits, remittance credits, dates, masked identifiers, and available balances. The exact formats vary by institution.
This is development coverage, not a production compatibility promise. The bundle is still marked illustrative and must be validated against consented, redacted real alerts before release.

​
Institution and wallet catalog

Salli also includes visual profiles for institutions or wallets such as Amana, Cargills Bank, CDB, DFCC, FriMi, Genie, eZ Cash, mCash, Pan Asia, Seylan, Standard Chartered, Union Bank, and others. A logo in the account picker does not automatically mean that bank’s SMS formats are in the current parser bundle.

​
What “supported” means

A message is usable only when:
  1. the sender passes the normal or explicitly trusted-test sender policy;
  2. the message does not match a safety filter;
  3. one bank template matches within its execution budget;
  4. required amount and direction fields validate;
  5. the value passes sanity limits; and
  6. the event is not a duplicate.

​
Unsupported format from a known sender

The newest 50 recognized-bank messages with unsupported formats may be held encrypted outside the ledger. They never change balances or metrics. You can dismiss, ignore, or export them for a consented parser-improvement workflow.

​
Test senders

Beta testers can add exact SMS/MMS phone numbers under trusted test senders. Salli still requires a valid supported bank format and continues to block OTP, promotional, declined, and malformed content. Android does not expose RCS/Chat messages through this path.