I’m considering using the Griffin app but I’ve seen mixed feedback on performance, security, and customer support. I’d really appreciate detailed reviews from current or past users, including what you like, what frustrates you, and whether you’d still recommend it today, so I can decide if it’s worth installing and trusting with my data.
Used Griffin for about 7 months for personal stuff and a side LLC. Mixed bag. Here is the blunt version.
What worked for me
-
Onboarding
– Sign up was fast, like 10–15 minutes.
– KYC was smooth, no weird document rejections.
– Got account details same day. -
App performance
– On wifi, app felt fine.
– On 4G, app lagged a lot and sometimes froze on login.
– Had 3 logouts during transfers, had to restart the app. No money lost, just annoying.
– Face ID worked about 80% of the time. Rest of the time it kicked me back to PIN. -
Security stuff
– Strong MFA, device binding, and alerts for every login and transaction.
– You get push + email for new payees and larger transfers.
– Card controls helpful: freeze card, limit types of transactions, block foreign.
– No fraud issues while I used it.
– One false positive block on an online payment. Support cleared it in about 40 minutes. -
Features
Good:
– Clean transaction list, merchant names made sense.
– Instant notifications on card use.
– Virtual card option helped for online subscriptions.
Weak:
– Limited budgeting or analytics. If you want spending insights, you need another app.
– Search in transaction history was slow and sometimes missed obvious matches.
– No web app when I used it, app only. That annoyed me for bookkeeping. -
Customer support
This is where reviews split, and my experience kind of matches that.
– In‑app chat response during daytime: usually 5–15 minutes.
– Evening and weekends: I waited up to 2 hours.
– Answers were short and on point, but sometimes support used canned responses before reading the full question.
– Got one bug escalated and fixed in about a week, they followed up after deployment, which was nice. -
Reliability and outages
– Saw 2 noticeable outages in 7 months.
• One where card transactions failed for around 30–40 minutes.
• One where in‑app transfers did not complete, but showed as “pending” for half a day.
– Status page was not always updated fast, so I ended up checking Reddit and X for info. -
Data and privacy feel
Noticed:
– Clear consent screens for data sharing with third parties.
– Easy to disable some data sharing in settings.
– No spam emails beyond the usual product update stuff.
I did not read every legal doc line by line, but nothing felt shady. -
When it works well
– Daily payments, salary, small transfers.
– People who like push alerts for every movement.
– Early‑stage business owners who need simple banking, not full ERP integration. -
When it gets frustrating
– If you move high volume or time‑critical payments, small outages turn into stress.
– If you expect instant human support 24/7, you will be disappointed.
– If you want deep features like multi‑currency, advanced rules, or rich reports, it feels thin. -
My bottom line
I switched to a more boring bank for the business account, kept Griffin only for a personal “play” account and subscriptions.
If you go ahead, my advice:
– Start with small balances for the first 1–2 months.
– Set low card limits until you trust the fraud systems.
– Test support with a non‑urgent ticket and see how it feels for you.
– Keep a backup account for critical payments.
If your main concern is security, it felt solid.
If your main concern is stability and top‑tier support, you might want a backup plan.
Used Griffin for ~1 year for a small consulting thing + personal. Mostly echoing parts of @cacadordeestrelas, but my experience tilted a bit different:
Performance
On Android, the app was noticeably heavier for me. Cold start took 5–8 seconds, sometimes more if on mobile data. I actually didn’t have many freezes during transfers, but I had random “Can’t reach Griffin” errors on the dashboard a few times a week. Not catastrophic, just… janky.
Security & trust vibe
Security feels solid:
- Login alerts every time, transaction alerts are almost too noisy.
- Device binding is strict. Switched phones, and the re‑onboarding was mildly painful but reassuring.
- Had one suspicious login attempt flagged that turned out to be me using a VPN. Took about 20 mins with support to confirm.
Where I disagree a bit with @cacadordeestrelas: the consent / privacy stuff felt long and slightly confusing. Not shady, just written by lawyers for other lawyers. I had to dig around to be sure they weren’t reselling marketing data. They do let you toggle a few sharing settings, but it is not super obvious where.
Features & workflow
Pros for me:
- Virtual cards were the killer feature. I used separate virtuals for each SaaS and killed one after a vendor kept trying to re‑bill.
- Merchant data was cleaner than with my legacy bank, fewer “PAYMENT 3849234” type lines.
Cons:
- No desktop access was a real pain for bookkeeping. Exporting statements from the phone, then sending them to my laptop, got old fast.
- No real “business tooling.” If you want stuff like multi‑user access, approval flows, proper invoice matching, you’re out of luck. I had to hack it with spreadsheets.
- Search in transactions is genuinely bad. I’d type “Adobe” and get half the matches, then by amount and suddenly it appears.
Customer support
Here is where I got more frustrated than @cacadordeestrelas.
- In‑app chat during business hours: decent, but you feel the copy‑paste responses. You have to push a bit to get nuanced answers.
- Outside hours: I had one card issue that sat for ~3 hours without a human. For a banking app, that’s too long for my taste.
- On the upside, once I got a real person, they were competent, not “script‑only” robots.
Reliability
I didn’t hit big outages often, but the small stuff piled up:
- Pending transfers that eventually went through, but left me unsure whether to resend.
- “Balance unavailable” for a few minutes at random times.
It never lost my money, but it did increase my blood pressure.
Who it suits / who it does not
Works fine if:
- You’re doing light personal use, side gigs, subscriptions, small transfers.
- You care about modern controls like virtual cards and card freezing, and you can tolerate some app rough edges.
Gets annoying if:
- You run time‑critical payments, payroll, or anything where a 30‑minute hiccup is unacceptable.
- You live in spreadsheets and want desktop web access and solid exports.
- You expect truly quick 24/7 human support.
My outcome
I ended up:
- Moving the business side to a “boring” bank with solid web access and better exports.
- Keeping Griffin as a sandbox account for online subs and random online purchases, because the virtual cards and alerts are very handy.
If you try it: keep another account for anything mission critical, run Griffin in parallel for a month or two, and see if the small annoyances feel tolerable or if they drive you nuts.
Griffin feels like a “solid idea, uneven execution” product right now, and both @jeff and @cacadordeestrelas captured that pretty well from different angles. I’ll focus on where my experience diverged and on the tradeoffs so you can decide if it fits your use case.
Where my experience was better
- Stability day to day: I did not hit as many visible errors as described. Short “dashboard unavailable” blips happened, but usually under a minute and rarely affected actual payments. For routine stuff like card payments and small transfers, Griffin behaved more predictably for me than their comments might make you think.
- Search & statements: Search is not great, agreed, but if you lean on exporting statements regularly instead of in‑app search, it becomes less of a pain. Once I set a monthly export habit, bookkeeping friction dropped a lot.
- Fraud controls: The aggressive alerts that @jeff found almost too noisy were a plus for me. For a newer app, I’d rather dismiss a few extra notifications than worry they are too relaxed.
Where I actually found it worse
- No web app: This is not a small nit. If you do anything even slightly “businessy,” app‑only access becomes genuinely tedious. For my contractor work, reconciling multiple invoices on a phone is slow and error prone.
- Support expectations: I agree with both of them that support is not 24/7‑grade. I would go further: you should assume “business‑hours focused, with lag outside that.” If you are coming from a traditional bank with phone support, Griffin will feel like a downgrade in urgency handling.
Pros of using the Griffin app
- Mobile‑first experience feels modern, not like an old bank with a skin.
- Strong card controls and virtual cards are great for online services and subscriptions.
- Security posture feels serious: MFA, device binding, and consistent alerts.
- Good for a “secondary” account: play money, subscriptions, small side‑gig income.
- Clearer merchant descriptions than many legacy banks, so you waste less time figuring out what a transaction was.
Cons of using the Griffin app
- App only, no desktop interface, which is a real negative for bookkeeping, exporting, and any heavier business workflow.
- Support is slow outside core hours and can be a bit template driven until you push for detail.
- Reliability is “good enough for casual use,” not “enterprise grade.” Short outages or pending transfers will occasionally spook you.
- Weak built‑in analytics and budgeting, so you probably need a separate tool if you care about insights.
- Transaction search is inconsistent if you rely on it heavily inside the app.
How I would position Griffin realistically
- Use Griffin as:
- A security‑focused card and account for online spending.
- A testbed for a side hustle before you scale.
- Do not use Griffin as:
- Your only account for payroll, rent deadlines, or high‑volume B2B payments.
- Your main hub if you live in spreadsheets and require web‑based workflows.
In relation to @jeff and @cacadordeestrelas as “competitors” in opinion: they are slightly more negative on reliability and slightly more frustrated with support than I am, but we all converge on one point. Griffin is fine as a modern, feature‑light app for noncritical money, and you should absolutely keep a second, more boring account around for anything mission critical.
If you do try it, treat the first couple of months as a live test: low balances, small payments, and deliberate checks of how support behaves when something mildly goes wrong. That experience will tell you more than any review thread.