One of the pain points we heard many times over when designing RIVO is that Applicants and Banks need to log in to so very many systems to complete an application.  

What if they only had to log in to one, and it had all the necessary connections to complete the application - a one stop shop ? 

To help overcome that issue, RIVO is built on an API-first strategy  - it is designed to work with APIs from day one. 

A good example of this is the LEI field you enter for the Beneficiary, or for any new party.  We do not maintain a database of all those LEI codes.  Instead we have an API to the repository and retrieve the details via the API. 

Other APIs will be added in as the product matures. We may even call  upon you to vote which ones are needed most in the Knowledge Centre Forums.