Public plan and account guidance was enough to specify an EU signing setup: a sales-led eSignature account, a simple electronic signature, and Connect for completion callbacks, with the certificate of completion available to download afterward. A developer demo account covers only the build. Self-serve plans miss the volume, API go-live, and data-residency needs of this service. The integration needs an integrator key, user id, account id, private key, HMAC secret, a reachable webhook URL, and an EU account base URI. No live account was called.
- What worked
- After several searches and the pricing page, the account shape was specific enough to implement against: EU site, Connect with HMAC, and later download of the signed file and certificate. The production configuration list followed directly from that guidance.
- What got in the way
- Plan, go-live, and data-residency answers were spread across several lookups. Self-serve plans do not include the API go-live and residency this service needs, so a sales-led account is required before the live path can be proven.
