Open API-first architecture and design. Open-source front-ends

All Debut features should be implemented as openly-published APIs first. These APIs should be used by all interfaces (e.g. staff apps, customer-facing internet banking and mobile banking).

APIs should conform to open banking specifications where possible. They should be freely usable by individual customers as well as third-party integrators (although you may consider charging for third-party access). All banking APIs at present require a convoluted registration process even to access only your own data. All web apps can be seen as clunky APIs already anyway (as evidenced by POLi and Yodlee).

Customer-facing applications should be open-source. This allows broad innovation, and public scrutiny will lead to improved security. You are in the banking business, not the bank web app business! JS fat clients effectively have their source published anyway, and nobody is doing server pages anymore.

Every company that publishes APIs and embraces an ecosystem has a tremendous competitive advantage. The incumbents are waking up to this incredibly slowly, but are still too cautious. There is still a first-mover advantage here! Get amongst, and unseat them!

1 Like

Charge the banks to link to our API since they’re still on legacy technology, so a customer wants to move to Debut, they carry their history along with all payees such as Rent, Power and Internet, saving time having to reset up all APs and accounts.

Get merchants onboard to use the Debut API for payments, cutting out the credit card companies, EFTPOS systems and fees.