CiviCRM Community Forums (archive)

I'm working with an anti-corruption NGO in Indonesia, and encouraging them to adopt CiviCRM and CiviContribute to expand their supporter base and to do a more efficient job of handling donations.

Two things that are very important to this organization are 1.) ensuring that they don't take money from someone who is clearly corrupt (under ongoing investigation, prior conviction, etc.) and 2.) to enforce a strict donation limit (maximum) per donor per year.

I recognize that this is perhaps a one-off instance, since most people want to use CiviContribute to get as much money as possible, but does anyone have any suggestions on how to implement a "black list" of prohibited donors and/or to enforce donation caps?

@Erik Hommel - Thanks for the reply.

For the first problem, I was thinking it would make the most sense to develop a "blacklist" of prohibited donors, and flag anyone that registers under that name for admin review before a user account is created. However, I have no idea of how to actually implement something like this on CiviCRM.

For the second issue, it would be relatively easy to use radio buttons on a web form to restrict the maximum a person could pay for an annual membership, but we also want to have an option for one-time donations. The challenge lies in comparing these two types of donations, and in rejecting donations above the allowable annual limit (the NGO worries that accepting too much money from one individual might create a conflict of interest, or affect their perception as an impartial fighter of corruption). Would it be possible to add a validation rule that basically checks whether donations year-to-date (for example) are below a certain threshold? How would one go about doing so?