As part of the next XMB version in development, I made changes to help with the new pricing structure of Google's reCAPTCHA service.

In our original implementation, the captcha was displayed as soon as anyone visits the registration page. This causes unwanted traffic between bots and the Google API.

Going forward, there will be an introduction page for registration. This means the reCAPTCHA gets pushed back to the 2nd page and won't be visited by bots quite so frequently.

There is also a future change regarding keys "to be migrated to a Google Cloud projected by the end of 2025." It is my next priority to learn how that affects us here.

What I've learned so far is that it's not just about the keys. I migrated one of the 2 keys used here and that transition is seamless.

After that, there are a bunch of steps for actually switching APIs from the "siteverify" to the "enterprise" version. Here's how that might go:

https://cloud.google.com/recaptcha/docs/using-features

The reCAPTCHA keys will have to be traded for Google Cloud API keys. Of course, there's a whole new way of doing things behind the scenes too:

https://cloud.google.com/recaptcha/docs/create-assessment-we...

Here is the old API reference:

https://developers.google.com/recaptcha/docs/display

So this looks like a need for more settings, a way to switch between the two API implementations, and a lot of testing after it's ready.

Also consider an alternative, https://www.cloudflare.com/application-services/products/tur...