Field Manifest

The Field Manifest defines additional fields that appear in the signing portal alongside the primary signature. It is derived automatically from the PDF template's signature block definitions and is embedded in the signing session at creation time.

Field Types

Manifest Structure

{
  "version": "1.0",
  "signingMode": "sequential",
  "slots": [
    {
      "slotIndex": 0,
      "role": "vendor",
      "fields": [
        {
          "fieldId": "vendor-sig",
          "fieldType": "sign",
          "role": "vendor",
          "anchor": "sig-vendor-main",
          "label": "Vendor Signature",
          "required": true
        },
        {
          "fieldId": "vendor-initials",
          "fieldType": "initials",
          "role": "vendor",
          "anchor": "sig-vendor-initials",
          "label": "Initials",
          "required": true
        },
        {
          "fieldId": "vendor-date",
          "fieldType": "date",
          "role": "vendor",
          "anchor": "sig-vendor-date",
          "label": "Date Signed",
          "required": true
        },
        {
          "fieldId": "vendor-title",
          "fieldType": "text",
          "role": "vendor",
          "anchor": "sig-vendor-title",
          "label": "Title / Position",
          "required": false,
          "length": 100
        }
      ]
    }
  ]
}

Slot Properties

OTP identity verification is always required before a signer can access the document - it is not a per-slot setting. The OTP code is always delivered by email.

Field Properties

Stored Field Values

After signing, all field values are stored in ESignSlotEntity.fieldsJson as a key-value record in your Azure Table Storage:

{
  "vendor-sig":      "<base64-png>",
  "vendor-initials": "<base64-png>",
  "vendor-date":     "2026-05-29",
  "vendor-title":    "Director of Operations",
  "vendor-terms":    true
}

Storage Details:

• Primary signature PNG: Also stored directly in ESignSlotEntity.signaturePngBase64 for evidence certificate generation
• Initials PNG: Stored as base64-encoded PNG (same as signature)
• Date fields: Stored in ISO 8601 format (YYYY-MM-DD)
• Text fields: Stored as UTF-8 plaintext (up to length limit)
• Checkbox fields: Stored as boolean (true/false)
• Audit trail: All field values linked to the evidence certificate via correlationId and groupId
• Encryption: fieldsJson and signaturePngBase64 are protected at rest by Azure Storage's platform-level encryption, the same as the rest of the table. They are not additionally encrypted at the application layer - unlike the signer's email address and the session's internal keys, which do go through application-layer AES-256-GCM encryption before storage.
• Data residency: Field values are written to your Azure Table Storage, in your chosen region

How Field Values Reach Your Storage

The signer completes fields in the eSign portal's browser UI. On submission, the portal constructs an HMAC-signed callback body - which includes the field values and the signature PNG - and posts it to your Dispatcher (POST /api/esign/callback). The field values and signature bytes therefore pass through the REFRACT-hosted portal in memory during that callback, on their way to your storage; the portal does not write them to its own database. Your Dispatcher verifies the HMAC signature before writing the values to your Table Storage.

All traffic between the portal and your Dispatcher uses HTTPS with a TLS 1.2 minimum.

Field Value Examples

Signature Field (sign)

{
  "fieldId": "vendor-sig",
  "fieldType": "sign",
  "label": "Vendor Signature"
}

Stored as:

{
  "vendor-sig": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNkYPhfDwAChwGA60e6kgAAAABJRU5ErkJggg=="
}

(Base64-encoded PNG, captured in portal, sealed in evidence certificate)

Initials Field (initials)

{
  "fieldId": "vendor-initials",
  "fieldType": "initials",
  "label": "Initials"
}

Stored as:

{
  "vendor-initials": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNkYPhfDwAChwGA60e6kgAAAABJRU5ErkJggg=="
}

Date Field (date)

{
  "fieldId": "vendor-date",
  "fieldType": "date",
  "label": "Date Signed",
  "required": true
}

Stored as:

{
  "vendor-date": "2026-05-29"
}

(ISO 8601 format, captured from signer's selection in portal)

Text Field (text)

{
  "fieldId": "vendor-title",
  "fieldType": "text",
  "label": "Title / Position",
  "required": false,
  "length": 100
}

Stored as:

{
  "vendor-title": "Director of Operations"
}

(UTF-8 plaintext, up to 100 characters)

Checkbox Field (check)

{
  "fieldId": "vendor-terms",
  "fieldType": "check",
  "label": "I agree to the terms and conditions",
  "required": true
}

Stored as:

{
  "vendor-terms": true
}

(Boolean: true if checked, false if unchecked)

Audit & Evidence

Field values are incorporated into the evidence certificate:

• All field IDs and values: Captured in fieldsJson within evidence
• Timestamps: Field value submission time recorded per field
• Signer identity: Linked via evidence certificate
• Document hash: Proves the document was not modified post-signing
• Consent text: Frozen at signing time, recorded alongside the signer's acceptance