Sigillum Finans
TRContact us
Sigillum/Integration

Integration

Connect your applications and institutional systems

Connect .NET, Java and Python services through the current SDK packages. Follow complete examples and API references in Sigillum Developers.

HOW IT WORKS

Integrate a shared service once.

Portal links and propagated transaction context associate shared-service records with the relevant application.

THE INSTITUTION’S SERVERS AND NETWORK
  1. 01
    Distinct business processes

    Applications

    Each application uses its own entry point and configured scope.

  2. 02
    One SDK installation

    Shared service

    Observation and context propagation follow application links.

  3. 03
    Correct application context

    Transaction relationship

    Calls and steps are assembled within their own trace.

  4. 04
    Review by application

    Institution portal

    Manage service links and inspect related transactions.

INTEGRATION SUPPORT

Supported technologies

Supported versions, integration methods and capabilities
TECHNOLOGYVERSION / METHODCAPABILITY
.NET.NET 8 / 9 / 10 · ASP.NET Core · HttpClientCore SDK and ASP.NET Core integration. Automatic HTTP observation through supported handlers.
JavaJava 8+ · JDK HttpServer · URLConnection · HttpClient (11+)Service lifecycle, shared context and supported JDK HTTP clients.
Servlet / Jakartajavax.servlet 3.1 / 4 · jakarta.servlet 5 / 6Separate servlet adapters; the framework’s Java requirements still apply.
PythonPython 3.10+ · ASGI · HTTPX 0.27 / 0.28Automatic observation at standard ASGI HTTP and HTTPX boundaries.
OpenTelemetrySpan attributes · Events · LinksNative span context remains distinct from SDK observer context.
AI evidenceModel · Prompt · Retrieval · Tool · PolicyAdditional structured information through the SDK enrichment API; see language-specific examples.
Institutional sourceHTTPS JSON · PostgreSQL JSONConfigured read-only sources for comparing institution records with the sealed trace.
Offline verificationEvidence package · Verification keysVerify exported evidence with the desktop verifier, outside the portal.

Integration planning matches these methods to your institution’s versions, client configuration and recording requirements. Deployment includes acceptance in your own environment.

01 / SDK

Reuse integration across shared services

Download the service package and configuration from your institution portal. Install the corresponding SDK in the service and propagate the transaction context through supported call boundaries.

Application-service links are controlled in the portal. Reusing a connected service requires the correct application context, without reinstalling the SDK.

02 / Examples

Language-specific application examples

Developers includes .NET credit assessment, Java payment risk and Python document-assistant examples. Download the examples and use the commercial SDK supplied by your institution portal.

03 / Additional information

Add relevant business context

Enrich observations with available model, prompt, retrieval, tool, policy and human-review information. Data origins remain distinguishable during review.

04 / Verification

Compare and verify

Define comparison fields and a read-only institution source. Compare the business record with the recorded trace; export the evidence and keys for offline integrity verification.

PRODUCT INFORMATION

Frequently asked questions

Where can I get the SDK?

From the Integrations screen of your institution’s Sigillum portal. Language-specific installation and usage instructions are in Developers.

DISCUSS YOUR REQUIREMENTS

Plan an evaluation for your institution.

Bring your workflow, integration requirements and review questions. We’ll discuss how Sigillum Finans fits your environment.

Talk to our team