F-01 / SSC / IDLESecure Signature Confirmation · SecurySign
SecurySign™
Secure signature confirmation™

Authorise this signature

gopaperless.ke is asking for your signature

Loan guarantee agreement.pdfPDF · SHA-256 9f2c41…a07e3b
Your signature

Use your fingerprint, face or screen lock to authorise.

Purpose

The signer authorises one signature with their passkey. SecurySign checks the passkey and applies the signature with the signer's own certificate key. The relying party (GoPaperless) prepares the document and embeds the result.

General notes · both frames
  1. 01Width. One card, centred; full screen on a phone (max 440 px)
  2. 02Skeleton. Header (mark, wordmark, language) · body (centred, one action) · footer (Cancel, Help) (A · B · C)
  3. 03Typeface. Space Grotesk, every weight from the wordmark down (400 / 600 / 700)
  4. 04Action. One full-width pill per screen; its label carries the state (radius 999, py 14)
  5. 05Status. One line under the action; halo while a passkey prompt is open (aria-live polite)
  6. 06Way out. Cancel bottom left in danger-soft, Help bottom right (always both)
ProjectTendaworld passkey frames
DrawingSSC · Secure Signature Confirmation
OwnerSecurySign
SheetF-01
Scale1 : 1
Rev02 · 19 Nov 2026
A

Header

Who runs the ceremony: Tendaworld's mark, SecurySign's wordmark, and the language.

№ElementSpecificationValue
01FrameColumn: header, body, footer. White cardmax-width 440 px, min-height 600 px
02TypeSpace Grotesk everywhere, the wordmark includedfont-sans
03HeightReported to the page on every changeSSC_RESIZE {height, width once}
04Languagelang param, then the flag picker; choice kept in the browseren sw fr ar pt es de zh hi
05BarFlex, space-between, gap 12px-6 py-4 (24 / 16 px)
06Tendaworld mark28 × 28, links to tendaworld.com in a new tabh-7 w-7
07WordmarkSECURYSIGN™, Space Grotesk 400, caps, ™ 9 px15 px, gap 8 after the mark
08LanguageFlag 21 × 14, 2 px radius, hairline ring; chevron 12 px; native select over itpill, hover fill
09DirectionMark and wordmark stay left to right, Arabic includeddir="ltr" on the group
B

Body

What is being authorised and who is asking: the eyebrow, the title, the asking site, the document and the signer's signature in one card, one status line and one button.

№ElementSpecificationValue
01BlockCentred columnpx-8 py-5 (32 / 20 px)
02EyebrowLock 12 px + SECURE SIGNATURE CONFIRMATION™, never translated12 px semibold caps, tracking 0.14em, muted
03TitleAuthorise this signature26 / 32 px semibold, tracking-tight, mt 8
04Asker{rpOrigin host} is asking for your signature, host in semibold ink. Every state. New 2026-11-19, not in signa yet15 / 22 px, muted, max-width 340, mt 8
05File cardRounded 16, hairline border, shadow-sm, padding 12, mt 24icon tile 44 × 44, radius 10, info blue, FileText 22
06File nameOne line, ellipsis15 / 20 px semibold
07File metaPDF · SHA-256 first 6…last 613 / 18 px muted, hash mono 12 px
08SignatureYour signature, under the file in the same card, on a white strip so dark ink shows. Every state when the token is LOA-4 and the signer has drawn one; no strip otherwisehairline rule, pt 12; 12 px caption; image 64 px high, object-contain, radius 10
09Status lineIcon + one sentence; halo fingerprint while the prompt is open14 / 20 px, min-height 40, mt 20
10ButtonFull width pill: Sign with MIMI.ke · Authorising · Try again · Done15 px semibold, brand fill, brand-ink text, py 14
D

Colour tokens

Light theme, as the frame ships. Names are the frame's own; the values are what the page shows.

  • brand#04D56DButton fill
  • brand-hover#00C05BButton hover
  • brand-ink#0F172AButton text
  • brand-softrgba(4,213,109,.12)Passkey halo
  • success-ink#067A44Signed line, fingerprint
  • ink#1A1C1ETitle, file name
  • muted#5A616CEyebrow, asker, meta, Help
  • hairline#E0E3E8Card border, flag ring
  • info#4285F4File icon tile
  • danger#E30000Error line, Cancel text
  • danger-softrgba(227,0,0,.12)Cancel fill
  • card#FFFFFFFrame background
E

Usage

How a relying party embeds the frame, end to end. Copy usage puts all of it on the clipboard as Markdown.

  1. 1 · Your server asks for a signing token

    Five minutes, bound to one document hash. Send the signer's SecurySign account email so the token is LOA-4 and names their one passkey. Without it the token is LOA-2 and the browser offers every passkey on the device.

    POST https://securysign.com/api/ssc/token
    Content-Type: application/json
    
    {
      "clientId": "<your RP client id>",
      "clientSecret": "<your SSC secret, not the OIDC secret>",
      "documentHash": "<hex SHA-256 of what is signed>",
      "loa": "LOA-4",
      "email": "<the signer's SecurySign account email>"
    }
    -> 200 { "token": "<eyJ...>" }
  2. 2 · Your page embeds the frame

    Your origin must be on the RP's Authorised signing origins, and your CSP must allow framing securysign.com.

    <iframe
      title="SecurySign signing"
      src="https://securysign.com/#/sign-frame?documentHash=<hash>&documentName=<name>&mode=registered&rpOrigin=<your origin>&token=<token>"
      allow="publickey-credentials-get *"
      sandbox="allow-scripts allow-same-origin allow-forms allow-popups"
      style="width:100%;border:0"></iframe>
  3. 3 · Messages

    Accept a message only when event.origin is https://securysign.com and event.source is the frame. The first SSC_RESIZE means the frame is listening: answer it with SSC_SIGN_REQUEST and the passkey prompt opens without a click.

    frame -> page  { type: "SSC_RESIZE", height, width? }        set the iframe height
    page  -> frame { type: "SSC_SIGN_REQUEST", documentHash, documentName, mode: "registered", token }
    frame -> page  { type: "SSC_SIGN_COMPLETE", signatureBase64, documentHash, operationId,
                     timestamp, mode, levelOfAssurance, userVerified, signingPath }
    frame -> page  { type: "SSC_SIGN_ERROR", error }             the frame shows Try again
    frame -> page  { type: "SSC_CLOSE_FRAME" }                   Cancel, or Done after signing
  4. 4 · Your server finishes

    Check that SSC_SIGN_COMPLETE's documentHash is yours, then verify signatureBase64 against the signer's certificate (GET /api/pki/certificates/me with their token) before embedding it. Never trust the page's word for it.

F

Rules

What every embedding keeps, whoever builds it.

  1. 1Only passkeys SecurySign issued (RP ID securysign.com) can sign. A passkey made under mimi.ke can't, by SecurySign's design.
  2. 2Always send the signer's email: one passkey in the prompt, not every passkey on the device.
  3. 3Let the frame size itself: set the iframe's height from every SSC_RESIZE, never a fixed height.
  4. 4SECURE SIGNATURE CONFIRMATION and SECURYSIGN are names: never translated.
  5. 5The words say authorise, not sign: the person authorises, SecurySign applies.
  6. 6The frame names the asking site by rpOrigin's host, never by a name the page sends.

Source: signa app/src/pages/SignFrame.tsx · signa app/src/features/sign-frame/*