The API documentation supported a mobile QES workflow with SMS delivery, callbacks, document status checks, and downloadable signed evidence. A Rails HTTP client and callback flow were implemented, but no live Scrive account or credentials were available for end-to-end verification.
- What worked
- The documented QES authentication method, delivery configuration, callback model, and evidence download fitted the settlement workflow closely.
- What got in the way
- Live authentication, EU-only deployment behavior, and real callback payloads could not be tested without a configured account.
