We publish the specification we run in production.
Yinkozi has been building device-side security infrastructure for African and Middle-Eastern financial systems since 2013. YinkoShield is the platform; the Execution Evidence Infrastructure is the architectural pattern we extracted from years of production deployment and published as a specification.
Thirteen years of device-side engineering, one spec.
- 2013
Yinkozi founded
Device-side security R&D for African and Middle-Eastern financial systems.
- 2019
Witness layer in production
Anchor reference at a Tier-1 South African bank — 30M+ endpoints under continuous evidence today.
- 2023
Hardware abstraction at scale
~13,000 distinct Android hardware configurations covered by a single abstraction layer.
- 2025
YEI-001 v1.0 published
The architectural pattern extracted, named, and documented as a specification.
- 2026
Strategic engagements
Schemes, processors, regulators, and tier-1 banks evaluating EEI as substrate.
The specification is the artefact, not the asset. The asset is the engineering investment required to run it at scale across the full distribution of real-world device configurations: the hardware abstraction layer that handles ~13,000 distinct configurations, the regression infrastructure that tracks platform-vendor change cycles, the chaos-engineering machinery that validates ledger coherence under partition.
We sell strategic engagements to payment networks, schemes, processors, and tier-1 banks. Pricing is bilateral. Conversations start with a briefing, not a sales call.
What procurement and risk teams need before the briefing.
Four structural facts about how YinkoShield operates. They shape the procurement, data-protection, and continuity conversations before they start.
-
·01
No data path to YinkoShield
The runtime ships embedded in the operator's application. The verifier runs in the operator's stack. Keys are generated inside the device's TEE and registered to the operator's backend over an operator-controlled channel that does not include us. There is no telemetry the operator did not ask for; there is no licence check at runtime.
-
·02
Operator owns the data lifecycle end-to-end
Evidence is generated and signed at execution time, against a device-resident append-only ledger. The ledger does not auto-upload. Device identifiers are pseudonymous (SHA-256 of the device public key); no customer PII appears in evidence. The spec enforces a privacy-profile choice — `strict` is required for South African consumers under POPIA §11; the same `strict` posture satisfies Nigeria's NDPR, Kenya's DPA 2019, Ghana's DPA 2012, Côte d'Ivoire's LPDP, Morocco's Law 09-08, Mauritius DPA, and the EU GDPR for European data subjects. These regimes apply at the operator boundary, not at ours, because the data does not cross it. The producer-conformance checklist in YEI-001 names each regime explicitly so an operator's DPO can map it to local requirements.
-
·03
Sovereign verification — no vendor-in-the-path
Verification of an Evidence Token requires the token, the operator-stored public key, and a verifier implementation. None of those three things has to involve YinkoShield. A YinkoShield outage does not interrupt verification. A YinkoShield termination does not interrupt verification.
-
·04
No certification programme; the spec is the contract
We do not certify operators, processors, or schemes. The spec, the four reference verifiers, and the cross-language test-vector corpus are sufficient. Adoption is a procurement choice, not a credential we issue.
-
·05
PCI DSS / SOC 2 / ISO 27001 — out of scope by design
Per the spec's CONFORMANCE.md §8: payment-scheme certification, PCI DSS, and the legal admissibility of evidence in any given jurisdiction are explicitly not what the substrate replaces. There is no cardholder-data path through YinkoShield infrastructure (we have no infrastructure in the trust path), so PCI scope does not apply at our boundary. The operator's program owns these certifications against its own deployment.
For the spec table of contents, the verifier contract, the threat-model boundary, and the standards lineage — read the specification page.
Procurement track: for our standard MSA / DPA templates, write to contact@yinkoshield.com with your jurisdiction. We share them ahead of the briefing.
-
UAE
Yinkozi Middle East FZE — incorporated entity
-
South Africa
Anchor production deployment, Tier-1 bank
Founder-led. The fastest path for scheme, processor, and tier-1-bank conversations is direct.
For procurement / vendor due-diligence, for the spec, for a technical briefing, or to schedule a Signal Lab walk-through: one email, two business days, no funnel.