CB Verify for Family Plan

We want to implement CB Verify via Stripe, but limit the verification to the FamilyPlan primary subscriber only, and exclude the users 'invited' by the primary subscriber. 
Is this do-able?

CB ID Verify protects pages not specific site features. So you'd need an isolated page for buying that plan and no other way to access it then protect that page for this to work.

How could we 'protect' the page. I am assuming no menu for the article and direct link to it via index.php. Am I correct, or is there another way?
I am also wondering if someone could type in the protected url manually and bypass security that way.

Once a member successfully completes identity verification, does CB ID Verify store the verified status in a CB field or another persistent user value that we can use elsewhere in Community Builder/Joomla?
 

I can only think of 2 ways of doing that.

You'd have to hide the plan from the subscriptions tab, hide it from registration, then create a Joomla menu item to the plan followed by protecting that menu item. It's not exactly ideal nor the intended purpose of CB ID Verify to verify individual site features.

OR

Create a Joomla article with the explicit purpose of collecting id verification. Set CB ID Verify to verify that article. Next using CB Query Field use the following to get their latest verify state into a field.

Name: cb_idverified
Type: Query
Now in your plan condition that the field has a value of 1, which would be a authorized state. This would hide the plan until they've verified their identity. That approach likely makes the most sense.

when state = 1, does that remain the member's effective verified state permanently unless verification is revoked, and what values represent failed, pending, expired or cancelled verification?

Yes, 1 is the authorized state unless revoked or expired. Expiration date is stored in that table as well. Feel free to adjust the query however necessary. The states a verification can be in are as follows.

0 = cancelled / revoked
1 = authorized
2 = pending
3 = initialized / requested