Currently the system is very protective over beneficiary consent. This is primarily put in place to protect against bad actors using the system to "spam" other users of the system and determine who is on the system.
That is, if you want to find out if someone is on the system as a potential attack vector, you sign them up as a beneficiary and see that they are moving funds accordingly.
Thus, we do not provide an easy way to see this unless the beneficiary confirms and consent is provided explicitly.
While this is all good and nice, we do not have an easy way to see if beneficiaries are assigned on a product and how much of it is going to them. This issue ensures that publishers can see in their inventory management screen a simple list of any configured beneficiaries and how much they are receiving, primarily with the value of letting the publisher know they at least configured it right and it is in the system accordingly.
Currently the system is very protective over beneficiary consent. This is primarily put in place to protect against bad actors using the system to "spam" other users of the system and determine who is on the system.
That is, if you want to find out if someone is on the system as a potential attack vector, you sign them up as a beneficiary and see that they are moving funds accordingly.
Thus, we do not provide an easy way to see this unless the beneficiary confirms and consent is provided explicitly.
While this is all good and nice, we do not have an easy way to see if beneficiaries are assigned on a product and how much of it is going to them. This issue ensures that publishers can see in their inventory management screen a simple list of any configured beneficiaries and how much they are receiving, primarily with the value of letting the publisher know they at least configured it right and it is in the system accordingly.