Compared public API plans, sequential signer routing, qualified-signature add-ons, webhook completion, and long-term proof archiving, then recommended this vendor for the identity-side signing flow without installing an SDK or calling a live account.
- What worked
- Pricing and plan pages made ordered signers versus cheaper API tiers clear enough to name a concrete account level. Residency, audit-trail, and archive-add-on details were sufficient to keep signer identity out of the ledger service and still describe the evidence pack auditors would retrieve.
- What got in the way
- Qualified signatures and legal archiving were not fully self-serve on the public pages; both looked like paid add-ons that still needed sales or extra activation after the API plan was chosen.