Increase Banks Supported #54
Replies: 6 comments 17 replies
-
|
What provider (Plaid, GoCardless, etc.) supports Australian Banks? Tempted to close this as a "not something Sure does" since the support actually comes from a 3rd party provider also. What do others think? Feels like maybe this should just be a documentation issue where we tell people what the best way to get their bank data is, since the code in this repo doesn't actually implement it. |
Beta Was this translation helpful? Give feedback.
-
I had a chance to speak with 4 different Australian bank providers (Basiq, Adatree, Illion and Salt Edge), while exploring additional integrations for Lunch Flow. The pricing for the open banking license is in the thousands of dollars a month, and there aren't any free personal tiers AFAIK, so it'd only make sense to offer this integration once there's a large enough user interest to justify the cost.
It would be helpful to keep the issue to track interest, which would motivate 3rd party providers to offer this integration if there's enough interest. You can see Lunch Money's institiution requests board as an example. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing your experience, Amr. This is a larger topic that we need to approach holistically. It's not just about Australian Banks, but: what Bank works using what method is a document/guide/supporting code-path we need to write that helps guide people down the path of least misery. |
Beta Was this translation helpful? Give feedback.
-
|
What's the best way to build a comprehensive mapping table of Bank <> Data Provider by Country that we could source from existing / prior users of Maybe? Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Should we start a Wiki page with the myriad providers and the "best of our knowledge" place to get stuff imported? |
Beta Was this translation helpful? Give feedback.
-
I am not sure, we can ask them. I do know that SimpleFin uses MX under the hood.
@MichaelDeBoey had a good suggestion on updating the Open Banking Tracker, rather than maintaining our own version, which I agree with. He confirmed the maintainers are open to PRs, and I reached out to the providers I use to confirm it's ok to share the data publicly in this format, and will keep you posted. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Update: Gocardless responded, they are OK with the data being shared. I'm thinking rather than submitting a one time PR with the updated coverage, to commit a script that anyone can plug in their GC credentials and run, that way, it's easier to maintain. Just need to now find the time 😀 |
Beta Was this translation helpful? Give feedback.
-
|
I think we should do (at least) 2 PRs:
|
Beta Was this translation helpful? Give feedback.
-
|
hi, I just deploy Maybe locally but the CSV from my bank is not supported AS-IS, Could we support more bank through the import csv ? is there a best approach to add such import ? (I can at least work on my bank data importing (UBS-Switzerland)) |
Beta Was this translation helpful? Give feedback.
-
|
Would Sure consider implementing bLink by SIX to support the majority of Swiss Banks? How could I help to get bLink integrated to Sure? |
Beta Was this translation helpful? Give feedback.
-
|
Of course! We're an open source project so all you have to do is follow the steps others have done for Enable Banking (mostly @alessiocappa via #382) or SimpleFIN (mostly @luckyPipewrench via many many PRs like #254) or Lunch Flow (mostly @sokie via #259) - for instance. Sophtron is also a PR that's open right now for it (see #596). They all rely on a |
Beta Was this translation helpful? Give feedback.
-
|
@74k1 how would you go about adding bLink to Sure? As far as I understand, it's not available for individuals, and companies have to pay a hefty amount both as initial investment and as monthly installments. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah.. unfortunately it's what I've come to understand as well with my short back and forth with them. 🥲 If anyone with enough power is reading this, please consider supporting open source projects. |
Beta Was this translation helpful? Give feedback.
-
|
ha, sounds like I'm not the only one pestering them about it! 😆 There's dozens of us! |
Beta Was this translation helpful? Give feedback.
-
|
Supporting every bank "as is" sounds like a nightmare given the number of banks in existence and the changes they make to things. What I can imagine is writing an LLM-based prompt that does the mapping for you and confirms the correctness. Want to work on that approach? |
Beta Was this translation helpful? Give feedback.
-
|
I developed my own little tool sure-sync to go about it. This is by far the most automation I could do. sure-syncPrivacy-first, Docker-based local ingestion pipeline for syncing OFX transaction files into the Sure (
The current release includes a web dashboard for live status, processing statistics, and account mapping management. 
Key Workflow:
Features
Components
Deployment ModesStandalone Mode (worker):Runs only the ingestion worker without the UI.
docker pull ghcr.io/shrestha-bishal/sure-sync-worker:latestFull Stack Mode (worker + web):Runs both worker and web dashboard via Docker Compose.
docker pull ghcr.io/shrestha-bishal/sure-syncor docker pull ghcr.io/shrestha-bishal/sure-sync-worker:latest
docker pull ghcr.io/shrestha-bishal/sure-sync-web:latest |
Beta Was this translation helpful? Give feedback.
-
|
What does this actually solve? It is just bloat and an attack surface. I haven't had issue with NAB/Macquarie/Commbank and ANZ csv exports + a quick script. You still have to manually generate the exports, so this isn't really saving time. |
Beta Was this translation helpful? Give feedback.
-
That's a fair point, and if you're only importing transactions from one or two accounts, I can see why this might feel like unnecessary complexity. It can definitely feel like bloat if you're comparing it to a quick script, and in your case that’s valid. On the “attack surface” concern, it’s a fully local service that only processes user-provided OFX files. It doesn’t access banks, doesn’t store credentials, and doesn’t introduce external network exposure to financial systems. So the surface area is essentially the same class of risk as a local script; it’s just packaged as a service with persistence and a UI. The web UI is entirely optional and can be run as a separate Docker image providing easy visibility into processing status, statistics, and account mappings. The backend worker is a lightweight, independent service that handles all core functionality which is distributed as its own Docker image and can be run as a standalone process. It’s not trying to compete with a 20-line script, it’s packaging a full workflow (deduplication, mapping, tracking, archiving, monitoring) for people who don't want to maintain that layer themselves. If you already have a script that handles everything cleanly, then you're not the target user. For me, the pain point was scale. I manage transactions across around 10 accounts, and manually tracking imports, account mappings, processed files, and duplicates with simple CSV exports + a quick script quickly became tedious. I’ve spent hours tracking down duplicate transactions that broke summaries and required cleanup. In addition, I had to keep reliable state on what had already been imported upto which date for which account. Sure Sync was built primarily to solve my own problem first, so it reflects that workflow. I export the files, drop them into a folder, and everything else is handled consistently. The goal isn't to automate bank exports, most banks don't provide suitable APIs anyway. I also looked into CDR providers, but didn't want to rely on paid services just to access my own data. The focus is everything after export: standardised processing, deduplication, state tracking, and auditability. If you already have a script that handles all of that and you're happy maintaining it, then Sure Sync won't add much value. In that case, you're essentially already operating at the same level of automation. From my side, working with multiple accounts means even small repetitive steps compound over time, and maintaining a custom script for all of that becomes its own ongoing responsibility. Sure Sync packages that into a consistent, opinionated workflow so I don't have to manage that layer myself something like Setup and forget architecture. But for users managing multiple accounts who want a reusable, Docker-based solution without maintaining custom code, it has been a significant time saver, it has consistently saved me hours in practice. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I developed my own little tool sure-sync to go about it. This is by far the most automation I could do.
sure-sync
Privacy-first, Docker-based local ingestion pipeline for syncing OFX transaction files into the Sure (
Maybe) Finance.Sure Syncis a Docker-based, localised automation service that simplifies importing bank transactions into theMaybeSurefinance platform. It is ideal for users whose banks do not provide public APIs, offering a secure, file-driven workflow for financial data while keeping all sensitive credentials, configuration, and data local.The current release includes a web dashboard for live status, processing statistics, and account mapping management.
Key Workflow:
a user-defined YAML configuration (<v2.0.0)dashboard.MaybeSure automatically.Features
YAML (<v2.0.0)dashboard.envComponents
Sure Syncis designed with a modular architecture where the ingestion worker and web dashboard can run independently.Deployment Modes
Standalone Mode (worker):
Runs only the ingestion worker without the UI.
Full Stack Mode (worker + web):
Runs both worker and web dashboard via Docker Compose.
or
Beta Was this translation helpful? Give feedback.
All reactions