Validation by a second user of an action taken on a “ static data entity” (e.g. Bank) by a first user.
Provides functionality to generate endorsement events when a User performs an action on an endorsable entity.
Manages endorsement events while they await approval by a User.
Examples of static data entities for which endorsement can be setup:
Bank User Role
Endorsement activation depends on a configuration file setup:
Either all entities or no entities require endorsement Setup is done on the level of
Actions that trigger the creation of an endorsement event are:
Creation of an entity
Update to an entity
Activation of an entity
Suspension of an entity
Deletion of an entity
For each endorsement audit records, capturing the modifications made by the User, are created.
The default behaviour for endorsement is to hide the modified details from the user until endorsement is done successfully.
Each instance of an endorse-able entity has an
Pending endorsement for
Modification Pending endorsement for
Deletion Pending endorsement for
Creation Pending endorsement for
Suspension Pending endorsement for
No Endorsement outstanding
Only a single active endorsement event can be pending against an entity.
The processing of some transactions must be split in two steps.
This typically applies to Transactions that are received before the day they are executed.
Some validations are performed the day the Transaction is received, to make sure it is valid.
Extra validations are performed the day the Transaction is executed, for instance, to make sure the account still exists, or funds are available.
Based on the Exchange Timings computed by the router, and on the type of Transaction, the system determines if the Transaction must be held or not.