2 posts tagged with "pay-as-you-go"

Most products that embed signing have more than one flow that signs. A user accepts terms during onboarding, an account admin signs the first contract, a customer signs a mandate that moves money. When you move these flows off a seat or envelope tool, the signature level often came bundled with the plan: every flow got the same ceremony because the account had it. With IgniSign, the level is a choice you make per flow, and each signature bills at the level it used. The integrating developer's decision is which flow gets which level.

You create an IgniSign application once, then you get three environments: development, staging and production, each with its own API keys. The integrating developer’s decision is which of those environments you use for which work, and what that choice costs when a signature request runs. The answer is not “everything is free until production.” It depends on the environment and on what the request does.