On the tech side I’d suggest revisiting ICRC-17 ICRC-17 - Elective KYC Service Standard - #11 by skilesare.
We used a form of this for something…maybe Yumi used it for the Gold sale? (@Dustin would likely remember) and it worked fairly well. It needs to be revisited and updated, but what it accomplishes is that the “methods” we determine are reduced to a simple call and interface. You can change methods and the function doesn’t care. If it gets “pass” back it moves on. This would be really helpful as a step for contributing to SNSs as well for DAOs that want to use a specific KYC process or vendor in their SNS process.
By putting this shim in place you can change your KYC process in two ways:
- Change the canisterId to point to a different process.
- Change the functional code on the canister and maintain the interface.
…thus creating a separation of concerns and letting the process group focus on process and the tech group focus on enabling the tech without complexity.