Live data from Hacker News

Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

finledger.com

201–210 of 257 posts

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#201
post #45
post #4

This sounds so futuristic which is awesome but at the same time banks like Tangerine, which otherwise I have nothing but praise for, don't even allow be to use a password more secure than a 4-6 digit numeric passcode. Obviously no 2FA. Sorry, that has little to do with the submission, I just had to vent about banks.

Tangerine recently launched 2FA but it is SMS based only.

I don't see that anywhere in the security settings. Not that I want SMS 2FA.

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#202

Earlier quoted context omitted.

Mint and Quicken are end user applications, Plaid is not. Plaid is an API provider to access financial information from multiple institutions.

Ok, but it's like the portion of Mint or Quicken that interfaces with financial institutions, and it enables end user applications, right? When I wrote "how is it different" I meant how is it different in the task it performs which (I assume) Mint and Quicken also perform.

Mint also did screen scraping, powered by Yodlee [1], if that’s what you mean. So, yes, same risks as Plaid.

They later moved off of Yodlee to Intuit APIs, post acquisition, although those also do screen scraping [2], and thus carry the same risks.

[1] https://news.ycombinator.com/item?id=1537825

[2] https://money.cnn.com/2010/12/02/pf/mint_leaves_yodlee/

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#203

The EU has been moving in this direction with PSD2 and it’s been pretty good. Downside is there’s no defacto standard for APIs and each bank's development skills vary widely.

It's true that the 6,000 banks in Europe have different standards, but the fact that the APIs exist and work and that the regulator is enforcing the use of real APIs (as opposed to screen scraping) is worth the effort to integrate each of the banks. I work at Nordigen and we integrated with 1,500+ banks in less than 8 months. Some APIs took hours to integrate, some took a few weeks, but the fact that it was possible…

Yeah. I used to work for a Hamburg based fintech that was one of the first to get its PSD2 license.

We still had to fall back to scraping at some points. Perhaps that’s different now.

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#204

Earlier quoted context omitted.

Are you sure you're not confusing things? Direct debit usually means just a permission to charge the given account for the specified amount. It's commonly used in Canada and doesn't involve sharing your password.

Wise (formerly TransferWise) has different meanings for "debit" and "direct debit". Their "debit" option works the way you think. You give only your bank card number, expiry date, and CVV. However, their "direct debit" option requires you to enter your bank debit card number and bank password into Wise's web form. It is not a redirect to the bank website. The URL says " https://wise.com/ ..." when you're asked to ent…

Are you in the US? I think Wise’s ways of adding funds vary depending on what’s available in terms of payment infrastructure in each country. In the UK where Wise is based, direct debits are very common for routine payments but do not require a card number. But for receiving money Wise UK’s closest equivalent right now is to authorise payment via open banking and your bank ( the newish UK specs for doing this are really good and online here: https://standards.openbanking.org.uk/ )

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#205

Earlier quoted context omitted.

It's true that the 6,000 banks in Europe have different standards, but the fact that the APIs exist and work and that the regulator is enforcing the use of real APIs (as opposed to screen scraping) is worth the effort to integrate each of the banks. I work at Nordigen and we integrated with 1,500+ banks in less than 8 months. Some APIs took hours to integrate, some took a few weeks, but the fact that it was possible…

Yeah. I used to work for a Hamburg based fintech that was one of the first to get its PSD2 license. We still had to fall back to scraping at some points. Perhaps that’s different now.

The great think about PSD2 is that it comes with a bunch of laws and regulators are generally good at making banks compliant. An API that's not working is a non-compliant API and banks get it. PSD2 came in to force in Sept, 2019 and 2 years later all the major retail banks in all EEA countries work have fully operational APIs.

One major limitation is that PSD2 only regulates access to payment accounts, but doesn't mandate access to credit cards, investment accounts, savings accounts etc. This is why screen scraping (to everyone's dismay) is still used - to "expand" what's possible with real bank APIs.

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#206

It's about time. When I learned that applications like YNAB (You Need A Budget) use services like Plaid to connect to my bank account, and that these services literally take my username and password and impersonate me to get my banking data, I was a little sketched out. I use YNAB every day, and having it connected to my bank account is incredibly useful, but if something goes wrong and Plaid loses my money somehow,…

I think the future is that banks/bank apps will do the budgeting stuff themselves. Most bank apps will now break down your monthly spending by categories. My bank app shows me my weekly and monthly spend compared to previous periods, how much I spent in each category, how much I spent at each business, how much I have spent this month so far compared to the same time last month and etc.

Uk banks are doing this now. You can use open banking to show all your (uk) accounts in one place

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#207
post #92

Earlier quoted context omitted.

> YNAB (You Need A Budget) use services like Plaid to...take my username and password and impersonate me to get my banking data WHAT. THE. F. I'm a longtime, happy YNAB user. I had no idea this was going on until just now. I always just assumed there were secure APIs used to import my data. YNAB's Capital One "integration" stopped working a few years ago (possibly because they cracked down on screen scraping?) and I…

Hi! I work at Plaid. We’re strong advocates for API-based connectivity -- our goal is for 75% of our traffic to be committed to APIs by the end of the year. As part of that, we've actually converted our integration with Capital One to be 100% API-based and use OAuth for authentication. You can read more here: https://www.capitalone.com/about/newsroom/data-sharing-agree...

Is there a list of which institutions you support using APIs versus screen scrapers? I'm a happy user of YNAB and would like to have automated imports for any bank that can be read from securely.

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#208

It's about time. When I learned that applications like YNAB (You Need A Budget) use services like Plaid to connect to my bank account, and that these services literally take my username and password and impersonate me to get my banking data, I was a little sketched out. I use YNAB every day, and having it connected to my bank account is incredibly useful, but if something goes wrong and Plaid loses my money somehow,…

Hi! I work at Plaid wanted to share that the Consumer Financial Production Bureau addressed the fact that a financial institution cannot waive liability responsibilities in a recent Compliance Aid. FAQ 4 says that instititutions cannot rely on an agreement with the consumer that waives the liability protections under Regulation E if a consumer has shared their account information with a third party because those are…

That's for the USA. This news is about Canada.

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#209

It's about time. When I learned that applications like YNAB (You Need A Budget) use services like Plaid to connect to my bank account, and that these services literally take my username and password and impersonate me to get my banking data, I was a little sketched out. I use YNAB every day, and having it connected to my bank account is incredibly useful, but if something goes wrong and Plaid loses my money somehow,…

FWIW I use Schwab for banking and I was able to connect YNAB to Schwab without entering my password. It looks like Schwab supports read-only API access, and Plaid takes advantage of that to avoid needing your credentials. As an added plus, you can keep 2FA enabled. Schwab does 2FA through an app so it's a touch above SMS-based 2FA (although only a single app is supported, Symantic VIP Access, rather than generic supp…

If you trust python-vipaccess[0], you can use it to provision the token to load into your preferred TOTP app. It’s not a supported method but if you (or someone coming across this later) want to use another app it’s an option :) From WilsonHammer on Reddit[1]:

1) Install pip, a python package manager, using your OS package manager.

2) Install python-vipaccess by executing `pip install --user python-vipaccess`

3) Execute `vipaccess provision -p -t VSMT` - this will print out all the information needed. Note the Symantec ID (it looks like VSMT12345678). It is what goes in the "Credential ID" field when adding a new device on Schwab's website.

4) Save the `otpauth://...` data into data.txt.

4.5) (Optional) Modify the `issuer=Symantec` parameter to read `issuer=Charles%20Schwab` Also change `VIP%20Access:VSMT123456789` to your Schwab online banking username. These are purely aesthetic changes and will only make a difference in the label that shows up in the Google Auth app.

5) Install qrencode using your OS package manager.

6) Execute `qrencode.exe -o qr.png -s 15 7) Scan the QR image (qr.png) with your google auth app.

8) Go to Schwab -> Service -> Security Center -> Manage Two-Step Verification -> Add another Security Token and input the Symantec ID from step 3 (it looks like VSMT12345678) and the current rolling TOTP code from the Google Auth App. (If you use Authy you may have to type it manually)

[0] https://github.com/dlenski/python-vipaccess

[1] https://www.reddit.com/r/personalfinance/comments/hvvuwl/usi...

Re: Canada calls screen scraping ‘unsecure,’ sets Open Banking target for 2023

#210

Earlier quoted context omitted.

Hi! I work at Plaid. We’re strong advocates for API-based connectivity -- our goal is for 75% of our traffic to be committed to APIs by the end of the year. As part of that, we've actually converted our integration with Capital One to be 100% API-based and use OAuth for authentication. You can read more here: https://www.capitalone.com/about/newsroom/data-sharing-agree...

What you did was wrong and you all knew it. It seems to have paid off though, so congratulations. Nobody with half a brain would trust you.

Literally the only way for apps you want to use with your own financial details is to screen scrape.

Plaid better have good security!

But I don't see this as unethical in the slightest. In fact, I see it as a company doing the right thing by consumers in letting them get access to their own data.

Post reply on HN