Plaid in Canada
blog.plaid.com
blog.plaid.com
Immediately after checking the link I was “ohhhh” and a little surprised that I was surprised.
Real-time transactions, for one, are not really real-time. There are many things that get in the way of making these real-time and the issues go all the way to the terminal where you swipe your card. Identity is also sketchy. Many people still share bank accounts. It is an unwritten rule that an account !== a person.
I'd be curious to know how they pull this information. There are some APIs available, but we are careful to hand out access. If they're screen scraping, then, well... god help them.
I definitely share your concern about how the data gets pulled by Plaid, but as far as I can tell most major banks that have mobile applications have demonstrated that they are at least _marginally_ capable of developing high-availability REST APIs that are reliable enough for purposes like this. I wouldn't be surprised if Plaid somehow managed to get them to agree to using the "mobile app" APIs for their application.
It just seems to me, likely another poster pointed out, is that they would have to partner with every single bank they want to deal with in order to send the right credentialing steps in order to access their internal systems, provided those systems even exist, OR, they would need to have access to a mythical overarching API that inherits to all systems (which doesn't exist). So somewhere in their platform there is a `Step 2) A miracle occurs`, and I just have a hard time believing that they can just gloss over noticing that before giving at least a motivation for the miracle. I mean if my money were at stake and I wanted to pay for the service (and my business' money would be at stake too!) I'd want at least a little bit of a guarantee that the service works as advertised and is totally above board.
Correct! We have three environments you can send API traffic into - sandbox, development, and production.
Sandbox + development are 100% free to use, development just requires a quick request through the dashboard after signing up for API keys. (https://dashboard.plaid.com/signup)
Sandbox- gives access to sandbox data to test the integration. Development - add up to 100 live bank accounts Production - add as many live accounts with paid account
I went looking for a Go library for your API and the plaid one says it's not maintained/supported anymore. Is there a replacement (third party or not) for it?
we currently don't have an updated official go library for our API, but shoot me an email (charley@plaid.com) and can shoot over some recs for third party libraries
You have to give out your main login credentials used to access your bank.
If anything happens to these downstream processors, the bank provides no support as you gave away your main login credentials.
My "Big 5" Canadian Bank won't provide read-only login credentials so using these type of services is a complete no-go from my end.
I LOVE that I get an email every time my credit card is used. But my debit doesn't have that option.
FWIW, I'm thinking more into personal spending atm.
Also when I travel, it saves my butt all the time. Its how I detected a hotel totally screwing up the accomodation bill. Also gives me insight into exchange rate so I don't fool myself on prices.
Email contains vendor name, date, and price in Canadian dollars.
It will even give you a notification when your card is run at a restaurant that includes a suggested tip - generally before the server comes back with the check to sign.
You can just set the threshold to $1 though.