title: reCAPTCHA V3: how to deal with expired token after idle?
body: <p>For Google reCAPTCHA V2 it was clear what to do when the token gets expired because of idle: the customer has a change to click on the reCaptcha checkbox again. 
  For Google reCAPTCHA V3 it is different as it is unclear when the token gets expired because of idle.</p>
  
  <p>For reCAPTCHA V3 it is suggested by Google:</p>
  
  <p><a href="https://developers.google.com/recaptcha/docs/v3" rel="noreferrer">https://developers.google.com/recaptcha/docs/v3</a></p>
  
  <ol>
  <li><p>Load the JavaScript api with your sitekey</p></li>
  <li><p>Call grecaptcha.execute on an action <strong>or when the page loads</strong> // we choose when the page loads, OK?</p></li>
  <li>Send the token to your backend <strong>with the request to verify</strong> // upon button click</li>
  </ol>
  
  <p>OK. If the button was clicked several minutes later than the page was loaded, the V3 token we send to backend is already expired. 
  What's the proper way to deal in this situation?  Should we silently auto-update the token by sending calls to Google every minute?
  What's the best approach for this case? I didn't find any suggestions from Google.</p>