Skip to content

Go-live checklist

  • The token is created on your server and is short-lived; no fixed token in the HTML or URL.
  • domain points to the right environment.
  • auth-mode and authorization-type are correct (defaults: transaction-token, cookie).
  • The page is served over HTTPS.
  • If you use the module build, the chunks/ folder is deployed.
  • complete and error are handled; users get a clear path on retryable errors.
  • The verification decision is based on the response your server gets for the transactionId, not on the result in the browser.
  • include-images="false" (default) unless you need the media.
  • If you upload to your own service, validation-mode="host" and the captured → upload → nextStep() / retryStep() flow are in place.
  • If you serve the models yourself, assets-base is correct and cached.
  • debug is off.
  • Tested on iOS Safari and Android Chrome.

When reporting a problem, include the detail of the error event and the browser console logs (debug="true" in a development environment).