

Vault is designed in a “Resource Oriented” manner. This means all operations

are performed on an object in the Vault database



Vault has an append only database design for the majority of objects, meaning

that the vast majority of updates will actually create a new record version and

the API will point to this new version



All of the objects in Vault follow a CRUD model for operations.



The Kernel , which is the mandatory component of Vault is responsible for a range of key activities



Customer and Internal Account Management.



Storage of Products as Smart Contracts.



Managing and executing the schedules of financial products.



Using Flags and Restrictions to modify account behaviour



Cross Product pricing and other cross product functionality using Supervisor Contracts.



Managing the Calendar Service.



Running an audit service to capture incoming API requests



The Kernel is made up of five key APIs



The Core API which is used for most account management and product management activities, this will typically integrate with the various channels of the bank and other bank systems



The Postings API is the single point of contact for all payments integrations into Vault.



The Data Loader API is used to migrate data from legacy systems onto Vault.



The Audit API provides a comprehensive audit system monitoring incoming API calls and their results



And finally the Access API facilities the management of employee roles and permissions on the Vault system.