You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking an use case -
User A and B have a joint account J with a bank who is the DP.
DC requests a some data type with user A who is willing to take some service with DC. A shares his CM-id to DC.
suggested flow 1 - (user B is not knowing this at the time of taking service)
A gives the consent to DC and DP via his DC.
DP cant share the data unless B also provides the consent.
DP fwds the consent request to CM of user B if account is linked else flow ends here and data cant be shared.
user B shares his consent.
DP is ready to share the data if consent given.
suggested flow 2 - (user B also knows about the service being taken)
user A shares his and user Bs cm-id to the DC.
DC sends the consent request to both users.
both users give/deny consent.
DP shares data based on consent from both users.
issues in this approach -
user will have to make decision before hand on which DP will be selected.
The dp selected may or may not require a multi consent for the request.
suggested flow 3 - (cm takes the reasonability of fwd the request to other user)
user A shared his cm-id to DC.
DC places a request to cm.
user A selects the DP and account (which requires multi consent)
user A gives consent.
DP response back to CM that "consent insufficient" . May or may not give the other user who is required to give the consent.
CM of A fwd the consent request to cm of B. cm-id of B is captured by cm of A or returned by the DP.
There can be cases where the DP needs the consent from multiple parties to execute the request. like in case of a joint account of user A and B.
The text was updated successfully, but these errors were encountered: