Secure Identity Verification™
gopaperless.ke is asking for your MIMI.ke
A partner checks that the person at the keyboard holds the account's passkey, the way a card issuer's 3-D Secure window sits inside a shop's checkout. MIMI runs the prompt on its own origin; the partner's server owns the challenge.
- 01Width. One card, centred; full screen on a phone (max 440 px)
- 02Skeleton. Header (mark, wordmark, language) · body (centred, one action) · footer (Cancel, Help) (A · B · C)
- 03Typeface. Space Grotesk, every weight from the wordmark down (400 / 600 / 700)
- 04Action. One full-width pill per screen; its label carries the state (radius 999, py 14)
- 05Status. One line under the action; halo while a passkey prompt is open (aria-live polite)
- 06Way out. Cancel bottom left in danger-soft, Help bottom right (always both)
Header
Who runs the check: Tendaworld's mark, the MIMI™ wordmark, an ID CHECK label and the language.
| № | Element | Specification | Value |
|---|---|---|---|
| 01 | Frame | Column: header, body, footer. White card, fills the iframe | min-height 100% of the frame |
| 02 | Type | Space Grotesk; MIMI's type scale | font-sans |
| 03 | Framing | Only the partner's registered origins may frame it | frame-ancestors from the partner row |
| 04 | Language | lang param, then the flag picker; choice kept in the browser | en sw fr ar pt es de zh hi |
| 05 | Bar | Flex, space-between, gap 12 | px-6 py-4 (24 / 16 px) |
| 06 | Tendaworld mark | 28 × 28, links to tendaworld.com in a new tab | h-7 w-7 |
| 07 | Wordmark | MIMI™, bold, tracking-tight, ™ 9 px semibold | 19 px, gap 8 after the mark |
| 08 | Label | Lock 12 px + ID CHECK | 12 px semibold caps, tracking 0.14em, ink-3 |
| 09 | Language | Flag 21 × 14, 2 px radius, hairline ring; chevron 12 px; native select over it | pill, hover sunk fill |
Body
The check itself: one disc, the title, who is asking, one button, one hint.
| № | Element | Specification | Value |
|---|---|---|---|
| 01 | Block | Centred column | px-8 py-5 (32 / 20 px) |
| 02 | Disc | 84 × 84 circle, fingerprint 40 px stroke 1.6; halo while prompting | green-08 fill, green-deep icon |
| 03 | Disc, failed | Same disc in danger colours | danger-bg fill, danger icon |
| 04 | Disc, done | Check 40 px stroke 2.4 | green fill, on-green icon |
| 05 | Title | Secure Identity Verification™, never translated | 26 / 32 px bold, tracking-tight, mt 20 |
| 06 | Asker | {partner host} is asking for your MIMI.ke | 15 / 22 px, ink-2, max-width 340, mt 8 |
| 07 | Button | Full width pill: Verify it's MIMI.ke · Waiting for your passkey · Try again · Confirmed. Pressable only after a failure | 15 px bold, green fill, on-green text, py 14, mt 24 |
| 08 | Hint | One line: how to answer the prompt, or what went wrong | 13 / 18 px, min-height 36, mt 12, ink-3 or danger |
Colour tokens
Light theme, as the frame ships. Names are the frame's own; the values are what the page shows.
- green#00C853Button fill, done disc
- on-green#0B1120Button text, done icon
- green-08rgba(0,200,83,.10)Disc fill, halo
- green-deep#067A44Fingerprint
- ink#0B1120Wordmark, title
- ink-2rgba(11,17,32,.60)Asker line
- ink-3rgba(11,17,32,.42)Label, hint, Help
- hairlinergba(11,17,32,.10)Flag ring
- danger#DC2626Failed disc, error hint
- danger-bgrgba(220,38,38,.07)Failed disc, Cancel fill
- card#FFFFFFFrame background
Usage
How a relying party embeds the frame, end to end. Copy usage puts all of it on the clipboard as Markdown.
- 1 · Your server asks MIMI for options
HTTP Basic with your MIMI partner client id and secret. Name the account's subject: MIMI answers with exactly one passkey, the newest, which is the one SecurySign signs with. 404 no_passkey means they haven't made one: send them to MIMI's enrolment.
POST https://<partner>.mimi.ke/api/partner/passkey/options Authorization: Basic <client_id:secret> Content-Type: application/json { "subject": "<the person's sub>" } -> 200 { "options": {...}, "state": "<sealed>", "account": null } -> 404 { "error": "no_passkey" } {} (no subject) only when you don't know the account yet, such as an invite link: any MIMI passkey is offered, and /verify says whose it was. - 2 · Your page embeds the frame
Your page's origin must be one of the partner's registered origins; MIMI sets frame-ancestors to them.
<iframe title="Secure Identity Verification" src="https://<partner>.mimi.ke/passkey/frame?client_id=<client id>&lang=en" allow="publickey-credentials-get" style="width:100%;border:0"></iframe>
- 3 · Messages
Accept a message only from the frame's origin. Send the options once the frame says it's ready. After your server refuses an answer, send the next options with retry: "rejected" so the frame shows why and offers Try again.
frame -> page { type: "MIMI_PASSKEY_READY" } page -> frame { type: "MIMI_PASSKEY_REQUEST", options, retry?: "rejected" } frame -> page { type: "MIMI_PASSKEY_RESULT", response } frame -> page { type: "MIMI_PASSKEY_CANCEL" } - 4 · Your server verifies
Send the response and the state back. Use the state once.
POST https://<partner>.mimi.ke/api/partner/passkey/verify Authorization: Basic <client_id:secret> { "state": "<from /options>", "response": <MIMI_PASSKEY_RESULT.response> } -> 200 { "verified": true, "subject": "<sub>" } -> 400 { "verified": false }
Rules
What every embedding keeps, whoever builds it.
- 1One passkey per request: the options name the person's newest passkey, and Try again asks for the same one.
- 2Passkeys live at SecurySign (RP ID securysign.com). People holding only an old mimi.ke passkey are sent to securysign.com/mimi to make one.
- 3Never point a partner's own servers at a *.mimi.ke host: any page there can use MIMI passkeys and read MIMI's session.
- 4Secure Identity Verification, MIMI and MIMI.ke are names: never translated.
- 5The frame names the asking site by its address, never by a name the partner sends.
Source: mimi apps/web/app/passkey/frame/page.tsx · mimi apps/web/app/passkey/frame/frame.tsx · mimi apps/web/app/passkey/frame/strings.ts