Free demo · No signup
Watch AI parse: Apple Pay QUICPay at Starbucks (Tokyo)
Real Japan samples — Rakuten Card, Sumitomo Mitsui Card, PayPay and every issuer that sends usage alerts. The demo runs itself: every alert becomes a structured transaction, exactly like Dibba does with your own notifications.
Apple Pay notification
Amount: ¥678
Card: 楽天カード（QUICPay）
running automatically
Pre-parsed samples from the production parser. In the app this happens live, on every notification — in about a second.
How it works in other countries: 🇦🇪 UAE · 🇸🇦 Saudi Arabia · 🇺🇸 US · 🇬🇧 UK · 🇩🇪 Germany · 🇫🇷 France · 🇪🇸 Spain · 🇮🇹 Italy · 🇵🇹 Portugal · 🇸🇪 Sweden · 🇳🇴 Norway · 🇫🇮 Finland · 🇮🇳 India · 🇹🇭 Thailand · 🇰🇷 Korea · 🇨🇳 China · 🇭🇰 Hong Kong · 🇦🇺 Australia · 🇳🇿 New Zealand
Any bank, any language
No integration list. If your bank sends alerts — English, Arabic, Chinese, anything — the AI reads them.
No bank login, ever
Only the notifications you choose to forward are parsed. No credentials, no account access.
Fully automatic
Every purchase lands in your feed and updates your budgets the moment it happens.
Parsing is always free · 2-minute setup
How it works
How the AI parses Japan banking SMS
Banks in Japan — Rakuten Card, Sumitomo Mitsui Card, PayPay and every issuer that sends usage alerts — already describe every transaction in the alerts they send. A message like “Purchase from 031-246***-001 AED 110.32 by Card Ending with 6904” contains everything an expense tracker needs; it’s simply not structured. Dibba’s parser turns that prose into data.
From notification to structured transaction
When a banking SMS or Apple Pay notification is forwarded to Dibba, the AI extracts the merchant, amount, currency, date, card and account, classifies the transaction type — purchase, ATM withdrawal, transfer, credit — and assigns a spending category. The result powers your feed, budgets, limits and savings goals in real time.
Why notifications beat bank logins
Aggregator-based apps ask for your bank credentials and support a fixed list of institutions. Notification parsing needs neither: it works with any bank in any country that sends transaction alerts, including regional banks no aggregator covers — and your login never leaves your bank. That’s the entire design: nothing to breach, because nothing is shared.
Frequently asked questions
What is a bank SMS parser?+−
A tool that reads the transaction alerts your bank already sends — SMS or Apple Pay notifications — and turns them into structured data: merchant, amount, currency, category, card and date. Dibba does this automatically for every alert, so your expense tracking runs itself.
Does Dibba read all my messages?+−
No. Dibba never has access to your inbox. You set up a one-time forwarding rule for your bank's sender only, and just those notifications reach Dibba. Everything else on your phone stays on your phone.
Which banks are supported?+−
Any bank that sends transaction alerts — there's no integration list, because there's no integration. If your bank texts you about purchases, in any language or format, the AI can parse it. That includes regional banks no aggregator supports.
Do I need to connect my bank account?+−
Never. No bank login, no credentials, no account access. The parser works purely on the notification text you choose to forward — that's what makes it safe.
Is the parsing free?+−
Yes — AI transaction parsing from banking SMS and Apple Pay is always free in Dibba, along with Live Activity, daily reports, a 7-day feed and one savings goal. Premium adds the Voice AI Agent, unlimited history and more.