After your end user accepts or declines a clickwrap, the SDK creates an event in ClickTerm and returns a Signature. The event remains unverified until your backend sends this Signature to ClickTerm’s verification endpoint. Verification confirms the Signature hasn’t been forged or tampered with and marks the event as verified. For accepted events, a Certificate of Acceptance is generated.Why it matters: Verification ensures the Signature hasn’t been forged or tampered with, providing proof of consent, security, and legal validity for clickwrap agreements.
Never expose your App Key in client-side code. The App Key is used
only for backend verification calls. The client SDK uses only the App ID.
Store the App Key safely — it won’t display again after creation, but can be
regenerated. Regenerating the key requires updating your backend configuration.
Requests to /clickwrap/verifyare counted toward billing. Implement rate
limiting or a Captcha check before this step to prevent abuse from end users.
Until verification is performed, the Clickwrap Event will be visible on the ClickTerm Dashboard but will remain in an Unverified state.
If a user declines the agreement, the event is still verified but no Certificate of Acceptance is generated. It is up to your application to decide how to handle this (e.g., blocking the user journey, restricting features, or allowing continued access).