

Customer entity in Vault provides basic fields (for example Customer first and last name) and external

identifier to be stored in Vault. TM recommends not to store Customer PII in the Vault and banks

should be using your Customer Record System outside of Vault as your golden source of Customer

Data and use the external Identifier to link the Customer Entity in Vault with your external golden

source of customer data



A customer in Vault can hold zero, one or more accounts. Customers can be associated with other

accounts through the use of an Account Object’s ‘Stakeholder’s’ field which provides the ability to

associate multiple customers to a single account, for example Joint Savings Accounts



All accounts on Vault are backed by one Smart Contract. An account captures monetary value that a

customer holds along with a collection of metadata such as Opening date , Stakeholders , Instance

Parameter Values , Linked Payment Devices and Account Details field, this allows for unstructured data

in a key:string value format



Not all parts of an account’s data structure can be updated in a synchronous fashion, this is because

some updates to the account entity will require code to be run in the Smart Contract. We model this

using the Account Updates Endpoint to make such changes to the account data. A single account may

have no account updates made, for example if it’s a new account. However there is no limit to the

number of account updates on a single account.

Notes :

We can create products like Current Accounts in any version of Vault as capability is version agnostic