{"id":26,"date":"2026-08-01T09:00:00","date_gmt":"2026-08-01T06:00:00","guid":{"rendered":"https:\/\/wlthy.io\/portfolio-tracker\/?p=26"},"modified":"2026-08-01T20:49:34","modified_gmt":"2026-08-01T17:49:34","slug":"when-your-bank-wont-connect-wlthy-snap-is-now-on-the-chrome-web-store","status":"publish","type":"post","link":"https:\/\/wlthy.io\/portfolio-tracker\/when-your-bank-wont-connect-wlthy-snap-is-now-on-the-chrome-web-store\/","title":{"rendered":"When Your Bank Won’t Connect: wlthy Snap Is Now on the Chrome Web\u00a0Store"},"content":{"rendered":"\n

Every net worth tracker<\/a> has the same blind spot, and nobody likes to talk about it.<\/p>\n\n\n\n

Aggregators cover the big retail banks well. Then you hold an account at a private bank in Geneva, a regional bank in Anatolia, a broker with no public API, and the connection simply isn’t there. It never will be. Those institutions have no incentive to build one, and the aggregators have no incentive to chase them.<\/p>\n\n\n\n

So you do what everyone does. You open a spreadsheet, you type the balance in by hand, and three months later the number is stale.<\/p>\n\n\n\n

Today we’re shipping the answer we’ve been testing since June. wlthy Snap<\/strong><\/a> is live on the Chrome Web Store.<\/p>\n\n\n\n

What\u00a0it\u00a0does:<\/h2>\n\n\n\n

You’re already logged into the account page. That’s the part people forget \u2014 the hard problem isn’t access, it’s transfer.<\/p>\n\n\n\n

Click the wlthy Snap icon and it takes a picture of the page you’re looking at. An editor opens. You drag to crop the part you want \u2014 the balances \u2014 and black out anything private: your name, address, account numbers, the message from your advisor. Then you send it.<\/p>\n\n\n\n

wlthy’s AI reads the balances and holdings from that image and stages them for review. Nothing lands in your ledger until you open wlthy and confirm it. It’s the same review-and-reconcile flow that already handles broker statements and bank exports \u2014 the AI document import<\/a> pipeline we’ve been running since launch.<\/p>\n\n\n\n

A\u00a0picture,\u00a0not\u00a0your\u00a0page’s\u00a0code:<\/h2>\n\n\n\n

This is the part we care most about, and it’s a deliberate design choice rather than a technical shortcut. It’s the same principle behind our\u00a0privacy-focused wealth tracker<\/a>:\u00a0you\u00a0decide\u00a0what\u00a0we\u00a0see.<\/p>\n\n\n\n

Snap does not read the bank site’s code. It has no content scripts, no access to the page’s DOM, no ability to see cookies or credentials. It cannot run on any site until you click the icon, and it holds permission for exactly one thing on exactly one domain: sending your image to your own wlthy account.<\/p>\n\n\n\n

Scrapers work the other way around. They need deep access to a page to pull structured data out of it, and they break the moment a bank redesigns a table. Snap reads pixels you chose to send. Bank UI changes never break it, and the crop-and-redact step means the parts you didn’t choose never leave your browser at all.<\/p>\n\n\n\n

Read-only, like\u00a0everything\u00a0else\u00a0we\u00a0ship:<\/h2>\n\n\n\n

Snap can stage an import. That’s the entire scope of what it can do.<\/p>\n\n\n\n

It cannot move money, it cannot change a setting, it cannot create an asset on its own. It authenticates with a dedicated Snap token that authorises exactly one thing \u2014 sending a capture for review \u2014 and grants no read access to your ledger. Every call it makes shows up in your audit log. Revoke the token in Settings and the extension stops working on the next capture. If you want the full picture of how we handle this, it’s on our security page<\/a>.<\/p>\n\n\n\n

How\u00a0to\u00a0set\u00a0it\u00a0up:<\/h2>\n\n\n\n

Install from the Chrome Web Store<\/a>, then open Settings \u2192 wlthy Snap<\/strong> in your account and create a Snap token. Paste it into the extension once and you’re connected.<\/p>\n\n\n\n

After that: open the account page, click the icon, crop, hide, send. The review link takes you straight to the staged import.<\/p>\n\n\n\n

And here’s what changed since our beta: Snap now works on every paid plan<\/strong>, not just Black. When we started testing it, the extension happened to share plumbing with our Black-tier agent tokens, so it inherited that limit. That was an accident of engineering, not a pricing decision \u2014 so we fixed it. Whatever plan<\/a> you’re on, if you’re paying, you can use Snap.<\/p>\n\n\n\n

Where this fits:<\/h2>\n\n\n\n

Four months ago we opened the MCP endpoint<\/a> so agents could read your ledger. Last month ChatGPT users got one-click install. Both of those made wlthy easier to ask<\/em>.<\/p>\n\n\n\n

Snap solves the opposite half. It makes wlthy easier to fill<\/em> \u2014 specifically for the accounts that no integration will ever reach, which is often where the largest positions sit. If you’ve read our take on why aggregators miss so much<\/a>, this is the practical answer to it.<\/p>\n\n\n\n

We’re watching how people use it before deciding what comes next. The obvious candidate is a re-sync flow: capture the same page next quarter and have wlthy diff it against what’s already there, the way statement re-imports already work.<\/p>\n\n\n\n

If your bank won’t connect, this is the bridge. It’s included with your plan, it takes two minutes to set up, and you decide what leaves your browser.<\/p>\n\n\n\n

Install wlthy Snap \u2192<\/strong><\/a><\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Private banks, regional banks and brokers without an API will never connect to an aggregator. wlthy Snap captures them from your browser instead.<\/p>\n","protected":false},"author":1,"featured_media":27,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-26","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wlthy"],"_links":{"self":[{"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/posts\/26","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/comments?post=26"}],"version-history":[{"count":2,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/posts\/26\/revisions"}],"predecessor-version":[{"id":32,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/posts\/26\/revisions\/32"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/media\/27"}],"wp:attachment":[{"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/media?parent=26"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/categories?post=26"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wlthy.io\/portfolio-tracker\/wp-json\/wp\/v2\/tags?post=26"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}