Skip to content

Concepts

'Consent' as the name implies is a step in a sales experience for a customer where they review the services and goods that one is trying to puchase anew or update them.

Once the customer has decided to checkout and pay, thats when consent is typically requested. Consent is also a Object which contains information about the transaction customer intends to submit to us.

This Object has a lifecycle and it shown below

graph LR
  A[ Doesnt Exist] --> B[ Created ];
  B --> C[ Presented ];
  C --> D[ Accepted ];
  D --> D1{ Session Expired ?};
  D1 --> E[ Archived ];
  E --> E1{ Legal expiry? };
  E1 --> F[ Deleted ];

Currently the consent that is accepted is stored for the duration session is active (1 day) ater which it will be archived for storage for 7 years. During this archive period anyone can take a look at the archived consent for compliance reasons. After 7 years, the consent will no longer be archived and it will be removed.

It is important to get a final sign off from customers about the goods and services customers buys before accepting the order. The act of reviewing the transaction and agreeing to the terms of services is called 'consenting'.

API's

This API provides the capability to record consent's, the operations that you can do on this API are

  • Creation or Recording of a consent
  • Update the status of a consent ( PRESENTED / ACCEPTED )
  • Query a created consent
  • Query an archived consent