The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.
Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.
Just inquiry: is there a functional specification kind of plan for this feature that can be read before it is realized?
The company I am working at is coding transactional systems for financial institutions, covering deals and their payment execution too. Although I realise Tiki will not do all kind of complicated things but there are some pitfalls good to avoid and practices good to follow. We struggled o lot with bad/unflexible initial table and function concepts and took us a while to fix in order to have a reliable, fast payment system that can connect & post well formatted payment messages to any external systems in a highly configurable way and also to keep auditable track of payments internally.
If you have something to share, please post,