In the EU we have a law (guideline) that banks need to implement PSD2.

https://www.dnb.nl/en/innovations-in-payments-and-banking/fi...

There are several companies who have build PSD2 api's and have contracts with all banks. For example in the Netherlands: https://bizcuit.nl/wat-is-psd2/

You could also register with a bank itself to connect to their PSD2 API. However I don't know the costs to obtain a license.

This^ Banks (based on their products/license) have to provide PSD2 APIs by law. Last time I checked (~3y ago) the quality of the implementations differed a lot so these aggregators made kinda sense to deal with the APIs details. Just think about the different MFA implementations banks are using. Another one for Germany is finapi.io

The API is named OpenBank, all SEPA area banks MUST have them, BUT unfortunately EU do not mandate public access to the API, only "approved institutions can use the API and some of course get approved and re-sell the API access at high prices to citizens...

We do have a law, but last I checked then in Estonia there was no way for a private person to do API based payments without later needing to log in to the website and signing the transactions manually with an ID card (i.e a smart card). Sad.

Most of these PSD2 aggregators have "Contact us" pricing. Last time I looked into it I couldn't find a provider accessible to retail customers who are only looking to access their own data.

They have to implement APIs but do they have to have reasonable costs and criteria for access? I doubt it.

> do they have to have reasonable [...] criteria for access?

Unfortunately, PSD2 is built on the model that only (expensively) certified middlemen are supposed to directly make use of the APIs provided by banks (definitively not for direct access by actual bank customers), so no, they don't…

Thx, I will add the details. In the mean time. If you need to contact me. Check out: www.wasigh.nl!

Much better! If you make the links in the About page clickable, I think people would really like that ;-)

I worked for Colours. A fullservice Internet Agency in Den Bosch. They have a fairly strict "no re-hiring policy". They don't want to encourage people to quit by hiring them back as contractor immediately. Which I can understand.

I've had contact with Jacques before. I will surely contact him again. Tnx

dank je!

The same suggestion was made to me on twitter. I will surely have a look!

tnx, my VPS is kind of crashing ...

yep sorry. trying to figure things out ...

Sitecore is based in Copenhagen. You may have a shot there: http://www.sitecore.net/Company/Job-Opportunities/Denmark.as...

I disagree. At the company where I work we have the exact same proces for making a website and making a mobile app. Depending on type of customer we use a waterfall or an agile approach.

Fair enough, that you mention the loose points. From your article I got the impression that you think app development can be only be done as a waterfall project because of the toolset. And the point I was trying to make in my post is that my experience tells me otherwise.

Maybe my text was not clear on this. I will check it again.

To answer your questions: a RESTful API to be used by my app only and not to be consumed by the rest of the world is not such a big deal. Using the mock-up as input I'll create a working prototype in xcode in 2-5 days. After that I'll send it to the customer as soon as possible. The visual designer will design the app. I will implement the design.

As software engineers we are hired by our clients because we have knowledge and skills that they don't have. It is our job to educate them on the important parts. Always have, always will be. I understand your frustration, but it is nothing new. Or maybe it's just me getting old :-)

What would you like to know?

iPone development can be "lean" and "agile", but can iPone development be "waterfall"?