-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification on Data Holder Brands #124
Comments
@jakubvozarik Thank you for your query. I am consulting with the Rules team to provide feedback here. Please stay tuned. |
Thank you @CDR-Register-Stream Just to expand a bit more on the context - the way we currently see it is that a Data Holder Entity (Bank A) would register a Data Holder Brand A (Bank A brand), Data Holder Brand B (Airline Brand), Data Holder Brand C (Supermarket Brand) for their white label products. As each of these brands could come with their own online banking experience and digital identity, the customer experience would be mirrored in the consent/authorisation flow, whereby a customer would be selecting a Brand from which they want their data to be shared and authorisation would follow the experience which is known to the customer from their online banking experience. These individual brands would come with their own unique branded endpoints too. Consent would then be established with each brand separately, i.e. if a customer wants to share data for Supermarket and Airline brands, they would go through the consent/authorisation flow twice. Would be great if we could get some feedback on this train of thought. |
Hi @jakubvozarik |
Combined with my comment above and related to your statement that 'individual brands would come with their own unique branded endpoints', there is also this detail in the registry -
I hope that's helpful. |
Thanks for your comments @nils-work @CDR-Register-Stream - was just wondering if you have any further guidance on this, as we need to know how to register and onboard onto CDR Register with multiple brands. |
I would like to follow up again to see whether there is any further guidance on how to onboard onto CDR register with multiple brands and also check whether a DH can have multiple brands with the same DNS? Thanks |
Hi @jakubvozarik thanks for your query. The on-boarding guide details how multiple brands are configured on the CDR Register. A good example to consider is brand specific GetMetrics collection. CDS Decision Proposal 145 introduces the concepts of brand aware metrics collection. Therefore, based on this outcome, you mayneed to ensure your brands are configured correctly to satisfy this requirement. If required, brand specific AdminBaseUri endpoints would need to be defined in the Register to cater for brand specific metrics collection but path rather than domain could be used to differentiate between brands. |
@jakubvozarik @nils-work After discussions on Wednesday, I note that the above comment doesn't outline the whitelabel scenarios. We are working to get confirmation with C&E on what the position is here. Please stay tuned. |
We now have the following statement from the compliance and enforcement team: Metrics collection by the CDR Register will be measuring how brands perform within the Consumer Data Right ecosystem irrespective of their white-label relationship. Therefore, white-label service providers will need to provide separate GetMetrics endpoints for all brands they service. |
Hi @jakubvozarik |
We have published technical commentary on white labelling to compliment noting paper 169. Please take a look at the articles Brands in the Consumer Data Right Ecosystem and White Labelled Brands in the CDR |
Closing as complete |
Hi,
What is the expectation in terms of CDR Register onboarding for Data Holders who issue white-label products under non-owned brands? Should these brands be registered under the data holder (white labeller) entity or should these be registered as separate entities?
Thank you
The text was updated successfully, but these errors were encountered: