Enterprise // agentic commerce

Enterprise & authorization partners

Agent Authorization Authority — beside your rail, not instead of it.

Enterprise & authorization partners

Framework mapping

  • DORAMAPPED
  • PCI DSS v4.0.1 Req 6.5.1MAPPED
  • FS AI RMFMAPPED
  • NIST SSDFMAPPED
  • EU AI Act Article 12READINESS
  • Five Eyes Agentic AI guidanceLINKED MAPPING
  • Partial SLSA L1–L2EVIDENCE
  • NXP SE050 secure element (PoC ✓ Jul 2026)ROADMAP

Ed25519

commit envelopes

offline-verifiable proof

local-only

CLI & HOOKS

repo never uploaded

Scroll Gate

PR enforcement

signed vs unsigned

SSX360

control plane

identity · billing · audit

For payment & agentic commerce teams

You run the rail. We prove the authorization.

Tokenization, authentication, and settlement stay on your network. SSX360 is the portable proof layer: signed commits on infrastructure code, CI gates before merge, and (in pilot) bounded agent mandates with human approval records you can verify offline.

Agent payments · AP2-ready proof

Proof layer beside your payment rail

Networks tokenize and move money. SSX360 answers who authorized the agent, what limits applied, and whether the change was signed before merge — authorization first, compliance mappings as billing.

Ships today

Fintech change-control evidence

  • Ed25519 authorization records on agent-assisted merges
  • MCP manifest baselines with drift detection
  • Scroll Gate CI — block unsigned changes on protected branches

Pilot program open

Agent spend & approval

  • Bounded spend mandates — cap, TTL, merchant allowlist
  • Human-present approval records with offline verification
  • Financial-infra presets for payments/** and ledger/** paths

Complements agentic payment infrastructure (AP2-style mandates) — we do not process cards or replace network tokens.

Raw activity logs are useless to regulators. Stack protocol, policy, and physical hardware.

  1. Layer 1 · Protocol (Sign)

    Matrix Scroll SDK, local Ed25519 signing, and MCP Trust Scanner — the open-source foundation.

  2. Layer 2 · Governance (Trust / Govern)

    SSX360 platform, team console, drift alerts, and Scroll Gate CI PR enforcement — the control plane.

  3. Layer 3 · Hardware (Prove)

    SE050 physical USB-C device and Authorization Pilot deployments — bench-validated preview, not GA.

High-stakes financial workflows

Fraud & AML screening

Prove which model flagged or cleared a case, under whose authority, months or years later.

Credit & lending decisions

Maintain an immutable record of the agent, the inputs, and the human approval behind automated lending.

KYC / KYB onboarding

Attest that identity verification ran exactly as required, backed by cryptographic proof.

Payments & agentic actions

Bind money-movement configurations to a scoped, authorized session with a verified human in the loop.

Authorization Pilot phases

  1. Phase 1 · Hardware Pilot

    Deploy physical devices to select engineering teams for hands-on validation in real development environments.

  2. Phase 2 · Platform Integration

    Expand across the organization — full fleet-wide enrollment, CI gating, and measurable compliance improvements documented.

  3. Phase 3 · Scale & self-serve

    Proven results drive enterprise-wide expansion once warn-mode gates and evidence export are validated.

Architecture at a glance

Three layers — open protocol, CI enforcement, hosted control plane.

  1. Matrix Scroll

    Open protocol. Signs commit envelopes locally via CLI, hooks, and MCP — keys never leave the machine.

  2. Scroll Gate

    CI enforces signed commits on protected branches before merge — unsigned changes are blocked or flagged.

  3. SSX360

    Hosted control plane for identity, billing, policy registry, and audit evidence export.

How it works

USB-C hardware possession factor (SE050 preview), merge gates on GitLab or GitHub, and audit export — governed sessions for agents, not developer productivity surveillance.

  1. 01 · Sign

    Matrix Scroll attaches commit envelopes via hooks, CLI, or MCP when agents touch your codebase.

  2. 02 · Gate

    Scroll Gate and ssx360 check enforce signatures before merge.

  3. 03 · Export

    Trust Operations Console: audit ledger, policy registry, and JSON evidence for procurement.

Repository roles

Project manager

Owns Git repositories, controls permissions, manages project access, and approves merge activities.

Developer

Works on assigned repositories with possession-factor sessions — commits, pull requests, and signing recorded with identity and device status.

Security / GRC

Monitors security events, reviews audit logs, and performs compliance readiness checks — SIEM export and offline evidence packs, not certification.

Audit event coverage

Pilot and enterprise deployments scope logging for assessor review — Prometheus / Grafana and SIEM export integrate with your monitoring stack; evidence packs remain offline-verifiable.

  • Hardware authentication and session activity
  • Device enrollment and revocation
  • Commits, pull requests, and merge approvals
  • Policy violations and access changes
  • Security events for SIEM export

Hardware signing · SE050

SE050 on-chip signing is bench-validated — evaluate it in a pilot now.

The NXP SE050 secure element generates its Ed25519 key on-chip and signs under the same RFC 8032 byte contract as the shipping SDK — no verifier changes required. This is a bench-validated PoC available for enterprise pilot evaluation, not a GA or certified hardware product.

  • Non-exportable keys

    The Ed25519 private key is generated inside the SE050 on first boot and never leaves the chip — no USB key-generation path exists.

  • Browser + CLI verify

    Every signature checks out in the matrixscroll.com browser verifier and the matrixscroll CLI under the current byte contract — same verify path as software-signed envelopes.

  • Bench-validated, Jul 2026

    10 acceptance vectors (64–800 B payloads) signed on SE050 hardware and cross-checked against Matrix Scroll before leaving the contractor's bench.

NXP SE050 secure element passed its first PoC milestone (bench-validated, Jul 2026) — preview until productized; emulated Ed25519 software signing ships today.

Example deployment profiles

Illustrative deployment profiles — not endorsements or customer relationships.
Example archetype

Financial infrastructure

Context: Payments, ledger, and core banking systems under PCI-adjacent change control as agents refactor pipelines.

Fit: Signed commits and Scroll Gate enforcement before merge — machine-readable evidence for internal audit, not payment-rail certification.

Pilot focus

  • Financial-infra guard on payments/** and ledger/** scopes
  • Unsigned protected-branch block demo with sample ledger
  • Procurement-ready JSON export mapped to DORA and PCI DSS v4.0.1 Req 6.5.1

Cloud platform

Context: Hyperscale internal repos with continuous integration and AI codegen at scale.

Fit: Signed provenance at commit time bridges AI-assisted changes and zero-trust CI/CD — declared actor and tool metadata in the audit ledger.

Pilot focus

  • Scroll Gate on monorepo protected branches
  • Evidence pack mapped to SLSA L1–L2
  • MCP provenance verbs in editor evaluation

Regulated software delivery

Context: SEC, PCI-adjacent, and federal supplier codebases under software change-control scrutiny.

Fit: Machine-readable verification manifests — auditable proof of which production paths were touched by agents.

Pilot focus

  • Regulated software delivery preset with exportable mapping
  • Evidence pack for change-control review
  • Honest scope — provenance evidence, not model governance

Every pilot includes

  • Architecture review with your platform or security team
  • Warn-mode Scroll Gate on up to two protected branches
  • Trust Operations Console walkthrough + JSON evidence export
  • Policy preset aligned to your regulatory mapping (DORA, PCI DSS v4.0.1, FS AI RMF, SSDF)
  • 30-day evaluation with weekly sync and procurement-ready summary
Agent mandate evaluationRequest Pilot ConsultationSDK on GitHub