The entire form element is destroyed and recreated for each step
The entire <form> element is removed from the DOM and a brand new <form> is created for each step. The new form gets the same id attribute as the original.
Some WordPress plugins (like certain Marketo integrations) and payment flows completely replace the form element. This is the hardest pattern for fingerprint stability because the DOM element reference is gone.
The SDK caches fingerprints by form_id string (not element reference). If the new form gets the same id, the cache should still apply. However, the SDK also needs to detect the new form element via MutationObserver and re-attach listeners.