Both variants mean the callback inputs were mutated natively (on failure
the client error was recorded into the callback inputs), so the app may
proceed to next() in either case and let the server decide. Only
bridge-level failures (no active callback, invalid arguments, missing native
module) reject the promise with RecaptchaError.
Outcome of an active Journey reCAPTCHA Enterprise verification.