This documentation set is presented as a light-weight, practical alternative mechanism for maintaining a Customer Consent Register across multiple energy data users and providers.
Gaining Customer Consent
Overview of how consent could operate by Data Users.
The Solution exists fully behind the Data User’s UX and is called by API by that user. Consent information is shared from Data User to Central Register based on the status of consent with the end Customer. Note, the Central Register does no validate or varify the Data User’s consent, only holds it registration.
Previous consent records held by the Data User can also be added to the Consent Register using the same mechanism
Verify Consent Token
Process for Data Providers to verify registration key and identify the property/MPxN and data that the consent encompasses, identify the consumer data and return it to the Data User.
It is the responsibility of the Data Provider to ensure they have a verified commercial relationship with the Data User and map the duid to their platforms access mechanisms & audit systems.
