DEMONSTRATION ONLY Fictional data only · all checks simulated · no real messages

THE SAMPHA VERIFY GUIDE

From first hello
to a clearer picture.

Gather your details, try the checks and see how a verification card comes together.

A working demo, with clear boundaries. Identity, DBS and all other checks are simulated. No real messages or payments. Use fictional details only. Demo reviewer accounts can access all demo applications; this is a shared sandbox.
01

Start on the web or by SMS

Choose Start verification and use trigger@sampha.example. Your sign-in code appears in the demo mailbox. To try SMS first, use the SMS simulator with +44 7700 900123 and the exact message SAMPHA VERIFY. Its short-lived link brings you back to the portal.

02

Gather your person and business details

Use the Trigger sample to fill Triggers Sweepers, Triggers Street Sweeping LTD and its fictional DEMO0001 company number. Sole traders can skip the company-register step. A business match does not establish authority to represent it.

03

Try the checks and upload the sample portrait

Complete the simulated phone challenge, then try the simulated identity and other checks. Switch a scenario to see what happens when more input is needed or a check fails. Download the provided fictional PNG and upload it; genuine ID, DBS certificates and arbitrary files are disabled.

Download Trigger’s demo portrait
04

Submit for a human review

Accept the demo declaration and submit. Sign out, then open the review desk and sign in as reviewer@sampha.example using its demo mailbox code. Request changes or approve the demo. A reviewer cannot approve their own application.

05

Preview and choose what to share

Return to your applicant account. Your card starts private. Review the selected fields and publication notice before making it public. Public cards are searchable by business name. Make the card private to immediately remove public access.

06

Connect a card to another tool

Read an opted-in card with GET /api/v1/public/cards/{publicId}. Private cards require a session or a separately granted service token. Tokens are limited to specific cards and can be revoked in the web admin interface.

const response = await fetch(
  '/api/v1/public/cards/YOUR_PUBLIC_CARD_ID'
);
const { data: card } = await response.json();
// Always display card.disclaimer and claim provenance.

COMING LATER

The same journey, in your conversation.

WhatsApp and Telegram signup, ChatGPT onboarding and card retrieval, and Slack/Telegram admin tools. The planned WhatsApp trigger is SAMPHA VERIFY; it is not connected in this POC. Sensitive steps will continue in the secure web portal.

Future MCP tools will give approved AI agents scoped access. Final review and publication decisions will initially stay in the web interface.