In banking, it is customary to do your own framework... (I have made my career with that).
That said, with the provision I understood your question and you really mean User Interfaces, not banking perse:
I am fond of TMS software. UniGUI might be an option and the other two are - bluntly - crapware.
In essense, what you need to evaluate is which software has the lesser points of failure.
That means it needs to process as much as possible serverside - with shadow servers in place and instant switching - and as less as possible clientside. That also means using as less cookies as possible. In banking, cookies are a risk. Possible exceptions are GUI state - off-line - and install state - on-line.
Good banking software has at least two factor authentication and a third one on install time.
In general, it is not the toolset you will be using, but the software design and test cycle you have in place. And do not store ANY unnecessary information clientside unless absolutely necessary. Cookies in any form, not just classic cookies, are evil by design in most cases: they handle a problem that is not there and about 90% of the time can be replaced with a serverside solution.
I would recommend TMS based solutions, since they are sound and properly maintained. Just make sure you use it correctly with the above explanation in mind.... Always buy a source license. You will need it at some point...
Also note that for banks the software infrastructure is often an eclectic mix of "services" written in many different languages varying from COBOL on old Tandem mainframes to Java, C#, C++, Pascal and Python. And more exotics like 4th generation AI languages... Do not focus on one single language. Make sure your software is bought from reliable suppliers and.... such software is expensive.. We payed in the region of 20.000 euro - yearly - for the Delphi compiler licenses alone, not to mention 100.000's for Oracle clusters and many millions in hardware to run that on... Banking software ain't cheap when done - approximately - right.
Now, suppose you buy TMS software. Make sure they KNOW you create banking applications and also make sure you have a service contract: again, that ain't cheap but it comes with your responsability and compliance to laws and regulations. Your software vendor might need to take insurance for your particular license because normal terms and conditions might be void in view of banking applications, regulations and the law! Hence the expense...
But note the last will not always be done in practise. Larger banks will usually do this, but smaller operations often do not cover their risks properly.
Recent
