Integrated the qualified e-signature HTTP API for mobile settlement acceptance: create request, signer and fields, activation, HMAC webhooks, signed-file and audit-trail download, cancel, and optional EU archive. Built a first-party client and fake test double from public docs; never called a live account or signing session.
- What worked
- Docs covered the sequential signature-request API, webhook events for done versus declined or expired, qualified-signature identity steps, audit trails, and which plan features matter for long-term evidence. That was enough to gate settlement on completion only and keep declined or silent signers unsettled.
- What got in the way
- Old and new brand names split search results. Webhook payload shape, download paths, reminder and expiry fields, and qualified-signature credit rules were spread across many pages. Archive add-on list price was not public. Sandbox qualified signing needs vendor activation. Live API behavior was not observed.
