Migration of v2 recaptcha to cloud

Hi ​@Atul_p, 

I have answered your questions inline, with some grouped together. Please see the reCAPTCHA Migration Overview and the rest of our documentation for more detail. 

a) But after migration if our usage goes above 10000 like 150000, then what, will we be charged or not

b) Will our siteverify api stop working and give error if more hits more than 10000 ? 

c) If it will give error, then how can we enable billing ? will it be enabled by default when we manually migrate or automatically migrate ? 

d) What if we do not enable billing and if our v2 checkbox/invisible migrated to cloud and usage more than 10000 ? 

e) What if we do not enable Enterprise in our case v2 checkbox/invisible migrated to cloud and usage more than 10000 ?

You will be only be charged if you have enabled billing. It is not enabled by default. You must manually add a billing account (credit card or invoicing) to the Google Cloud Project that holds your migrated keys. You can do this in the Google Cloud Console under "Billing". Please see Billing information for more detail.

If you do not enable billing on the Google Cloud project where your keys are migrated, reCAPTCHA will fail-open (they will return success:true with a default score of 0.9) once you exceed the 10,000 monthly free quota.

e) What if we do not enable Enterprise in our case v2 checkbox/invisible migrated to cloud and usage more than 10000 ?

I think there is some confusion on the language. There is no separate "non-enterprise" version of reCAPTCHA on GCP. The billing tiers apply to any usage once migrated to Cloud. If you are migrated and usage is >10,000, you must enable billing or your requests will fail-open, rather than offering protection.

f) Will enterprise api also be enabled by default when we manually migrate or automtically migrate ? 

Yes, the ability to use the reCAPTCHA Enterprise API is enabled on the project whether you use the self-migration tool, or are auto-migrated.  

g) We do not want to modify our code which has siteverfiy api , we want to use the old siteverfiy api as it is and also allow more than 10000 hits or like 150000 hits after migration , what all things we will need after auto/manual migration ? 

No code changes are required. You can continue to use SiteVerify, however the API will have the 10000 assessment quota applied. You will need to enable billing if you want to maintain protection.

h) when we migrate v2 classic keys , will these become v2 enterprise keys or will it be just v2 classic keys linked with a google cloud project ? what is the difference between both ?

There is no distinction: they are now managed in the Google Cloud Console instead of the Admin Console, and they are subject to reCAPTCHA’s Google Cloud Terms and billing policies. 

i) We assume that after migration our v2 sitekeys and secret keys will remain as it is. 

Yes, your site keys and secret keys remain the same after migration.

j) After migration ,how long we can continue to use v2 checkbox or v2 invisible keys (classic keys linked with cloud) with the same old siteverify api ? is there any timeline when google will stop supporting v2 and siteverify api ? Google has stated you can continue using siteverify indefinitely after migration. 

l) how long before it is mandatory to use the new CreateAssessmentApi for enterprise ? 

There is no announced sunset date for the SiteVerify API, though we encourage upgrading to the CreateAssessment API if you would like to leverage advanced features. 

k) Is CreateAssessmentApi same as Enterprise API ? Basically the email says to use CreateAssessmentApi , when to use it as we can see it needs code change ? 

The Enterprise API refers to the entire reCAPTCHA Enterprise API. Please see the reference. CreateAssessment is one method of the reCAPTCHA Enterprise API. You only need to use it if you want access to advanced features. Please see Use reCAPTCHA features after migration.  

You can continue using SiteVerify if you do not want to change your implementation.

Thank you, 

Emily

Thanks @emilymb. The answers helped. I do have few other small queries.

We have 7-8 keys. In terms of cost effectiveness for billing as we would like to keep the billing minimum-

1 - Is the 10 K limit at project level ? meaning 10K free allowed for for one project separately

or 

2 - Is it for billing account (one credit card) where one billing account can be mapped for 2-3 different projects ?

3 -Basically if its at project level (irrespective of one billing account or 7 different billing accounts), then can we create 7 different projects for 7 keys with same / different billing accounts and have 10K quota for each project and key ? Basically trying to understand what’s allowed and what will save the cost for us.

4- Like if 7 keys, 7 different projects, 7 billing accounts - what happens here ? only 10 K or 70K quota

5 - If 7 keys, 7 different projects, 1 billing account , what happens here ? only 10 K or 70K quota