01
Gather the right information
Define the record your platform will issue.
Use cases
Help your customers carry their proof.
Add signed records to the services you provide, so people can share and check them beyond your application.
Platforms & customers
Platforms & customers: the decision behind the check
Your business creates the record; your customer carries it to a new recipient. Keep issuance administration in Console while making an intentionally public proof easy to check in Verify without giving the recipient workspace access.
Use cases
Platforms & customers workflow
02
Make the checks visible
Integrate issuance and verification into your customer flow.
03
Keep the next step clear
Let holders share records and keep their status manageable.
Details and limitations
Platforms & customers: practical requirements
Who uses which workspace
Your platform's developer uses Console to configure issuance and verification. Your customers should not need to become administrators in that workspace to inspect a public proof. Personal Verify accounts serve the customer's own records; they are not a substitute for your platform's API environment or organizational permissions.
A focused acceptance exercise
Test the full journey from your application's completion event to the customer receiving and sharing a proof. Review public fields before issuance and provide a clear correction path. Verify that retries do not create confusing duplicates and that recipients can distinguish content integrity from issuer assurance.