Go-live checklist
- The token is created on your server and is short-lived; no fixed token in the HTML or URL.
domainpoints to the right environment.auth-modeandauthorization-typeare correct (defaults:transaction-token,cookie).- The page is served over HTTPS.
- If you use the module build, the
chunks/folder is deployed. completeanderrorare handled; users get a clear path onretryableerrors.- 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 thecaptured→ upload →nextStep()/retryStep()flow are in place. - If you serve the models yourself,
assets-baseis correct and cached. debugis off.- Tested on iOS Safari and Android Chrome.
Support
Section titled “Support”When reporting a problem, include the detail of the error event and the browser console logs (debug="true" in a development environment).