This example shows how the PV service might fit into your product access flow:
Your product interface
When a user tries to access a feature that requires parent verification, present a screen/modal to make them aware of this and the reasons why. Avoid legal jargon and tailor this messaging to be clearly understandable to the user.
If you don't already have it in your system, prompt the user to provide their parent's email address.
NOTE: It is possible that a child may enter an invalid email address. We recommend that you validate the email domain before submitting the email address to KWS.
When the email address is submitted, the KWS PV service flow is triggered, as described next.
The KWS PV service flow
If the parent has not previously been verified, or has opted out of having their email address stored in the ParentGraph, the verification process is as follows:
KWS sends an email to the parent, informing them that they need to complete some verification steps:
The ‘please let us know' link directs the parent to your customer support/FAQ URL, which you provide in your PV service settings.
If the parent needs help with the verification process, they can click FAQ in the footer of the email. This directs the parent to the KWS Parent Support site where they can:
Directly contact our dedicated KWS Parent Support Team.
View troubleshooting tips.
Find out more about SuperAwesome.
When the parent clicks I'm an Adult, a KWS webview opens, offering the parent a choice of verification methods. The available verification methods are determined by the child's location (which you pass to the KWS API), and the methods you choose to display when configuring your PV service settings.
This is an example of KWS' U.S. payment card verification interface:
If the parent verifies their identity successfully:
KWS sends a ‘successful verification' event back to your system via a webhook call.
KWS directs the parent to your redirect URL, if you provided one in your PV service settings. For example, you might specify an interface that allows the parent to control their child's activity on your product. If you did not provide a redirect URL, KWS displays a verification success message within the PV service web page:
A hash of the parent's email address is stored in the KWS ParentGraph. This enables KWS to determine whether the parent is pre-verified the next time they encounter the PV service (see Pre-verified parents below).
KWS sends a confirmation email to the parent, informing them that they have been successfully verified and added to the ParentGraph. In the case of payment-based verification methods, the email includes details about authorization, capture, and refunds, depending on the requirements in the child's country. For example:
If verification fails, KWS displays an error within the verification screen. The parent can re-enter their verification credentials:
‘Pre-verified' means the parent's hashed email address is included in the ParentGraph, and the parent has been previously verified by the KWS PV service using a verification method which is (or was, at the time of verification) enabled for the current product.
Pre-verified parents do not have to provide verification credentials, so there is zero friction in their identity verification flow. This also benefits your conversion rates, due to the network effect of the ParentGraph.
For pre-verified parents, the KWS flow is as follows:
KWS sends an email to the parent's email address informing them that they need to confirm their identity:
When the parent clicks I'm an Adult:
KWS directs them straight to your redirect URL, if you provided one in your PV service settings. For example, you might specify an interface that allows the parent to control their child's activity on your product. If you did not provide a redirect URL, KWS displays this verification success message within the PV service web page:
KWS sends the parent a confirmation email: