Native component

This mode is not built. It is deliberately held back until a specific screen needs it, because the iframe embed covers most of the benefit at a fraction of the cost and complexity.

The difference is narrow: an embed puts our page inside your layout, and a native component puts our signing surface inside your React tree. Visually they are close. The native version wins only when the signing surface has to be genuinely indistinguishable from the rest of your product — shared design system, shared state, no frame boundary.

If you have a screen where the embed is visibly not good enough, say so, because that is exactly the signal this is waiting for.

Start with the iframe embed. It reports the same progress events a native component would, so moving later would change how the signing surface is rendered without changing how your product reacts to it.