Prevent · Authenticate · Discourage
Strengthen transaction security, communication authenticity and trust checks before a sensitive action.
Transaction security · Fraud prevention · Digital trust
Protect trust before and after a cyberattack.
TAA SECO is a digital-trust and transaction-security platform developed under Divitia Holding Ltd. It brings together two distinct inventions — TAA and TPV — with SECO, a public security-identification code from the TAA framework, and AOM, an affiliation and mission-verification service.
TAA SECO complements existing cybersecurity and authentication systems. Public information intentionally excludes protected implementation details, confidential technical know-how and security-sensitive specifications.
TAA-TPV = combined protection framework
TAAInvention 1 · transaction security & anti-coercion
TPVInvention 2 · controlled trust, pseudonymization & identity status
SECOSecure External Code · public security-identification reference
AOMAffiliation & mission-verification service
Before & after compromise
The protection objective continues after data has already been stolen.
Reduce exploitation · Verify · Protect
When real information has already been exposed, reinforce trust checks so possession of stolen data alone is not treated as proof of legitimacy.
Preserve and restore trust
An organization may evaluate TAA SECO before an incident or after compromise, when confidence in identities, communications and counterparties must be rebuilt.
A different trust problem
Real data can be used by a false identity.
An attacker may already know a person’s name, telephone number, address, bank, employer or other information obtained through a compromise. The data may be real while the identity presenting it is false. TAA SECO is designed so that stolen data does not automatically become proof of legitimacy.
Impersonation riskFraudulent calls, SMS, cloned sites, SIM-swapping-related impersonation and social engineering can imitate legitimate organizations.
Transaction riskA legitimate user can be manipulated into authorizing a fraudulent payment or action even when strong authentication works correctly.
Authority riskFalse representatives, technicians, delivery personnel or agents can use real details to support a convincing physical or digital impersonation.
How the trust decision works
Verify more than the user before a high-risk interaction becomes irreversible.
At public level, the platform can be understood as a sequence of trust checks. The detailed authentication, enrolment, anti-coercion and validation mechanisms remain protected and are not disclosed here.
Recognize when a communication, credential, payment destination or transaction requires a higher level of trust.
Confirm that the asserted person, organization, representative or mission context is consistent with trusted information.
Add a separate trust reference around the expected beneficiary, service, organization or interaction destination.
Support a user or institution in deciding whether to continue, challenge, delay or escalate the sensitive action.
Where the use case permits, preserve controlled records of verification state, validity, expiry, revocation or institutional action.
Beyond strong authentication
“Is this really the user?” is not the only security question.
Strong authentication is essential for confirming the user. Fraud can still occur when the legitimate user is manipulated into authorizing an operation they believe to be legitimate.
Within the combined TAA-TPV framework, SECO can add a second trust question: is the user really dealing with the identity, recipient or context they believe is legitimate? TAA adds a further concern: what happens when the legitimate user is themselves under pressure or coercion?
Why this matters · Real-world context
Trust failures are not theoretical.
Selected public sources illustrate how impersonation, uncertain authority, changed payment destinations and other trust failures can affect real interactions. TAA SECO links these examples to the broader verification problem without claiming involvement in or guaranteed prevention of a specific incident.
YouTubeExternal trust risk
External trust-risk reference 01
Public-awareness reference illustrating a situation where trust can become uncertain.
Context & relevance →
YouTubeExternal trust risk
External trust-risk reference 02
Public-awareness reference illustrating a situation where trust can become uncertain.
Context & relevance →
YouTubeExternal trust risk
External trust-risk reference 03
Public-awareness reference illustrating a situation where trust can become uncertain.
Context & relevance →
YouTubeExternal trust risk
External trust-risk reference 04
Public-awareness reference illustrating a situation where trust can become uncertain.
Context & relevance →External sources are independent and remain responsible for their content. Inclusion is contextual, not endorsement or a claim that TAA SECO would necessarily have prevented the event. New agent discoveries require editorial and Legal & Compliance approval before publication.
Canonical architecture
One public platform, two inventions, a security code and a verification service.
TAA SECO is the master public brand. TAA and TPV are distinct inventions. SECO is a public security-identification code issued from the TAA framework. AOM is a service enabled by the TAA/SECO security infrastructure.
01
TAA
First invention: transaction security and anti-coercion protection around sensitive actions, communications and exchanges.
02TPV
Second invention: controlled trust, pseudonymization and identity-status context, particularly for unknown counterparties.
03SECO
Secure External Code: a public security-identification reference derived from the TAA framework.
04AOM
Affiliation & Mission Order: a service for verifying organizational affiliation and mission or authorization status.
AOM · trust beyond the screen
Physical identity and mission claims can also require verification.
A person may present themselves as a technician, employee, institutional representative, delivery person or other authorized agent. AOM is designed to help verify whether the person is actually affiliated with the organization and, where the deployment supports it, whether the claimed mission or authorization is valid.
This extends the trust model beyond the telephone or computer screen into physical interactions where false representatives can exploit real information.
Institutional use cases
One trust architecture, multiple high-risk operating environments.
Beneficiary and instruction confidence
Add an independent trust reference around sensitive payment instructions, remote communications and expected transaction destinations.
Institutional use →Trusted transaction context
Support stronger checks around account identity, expected recipients and high-risk actions in mobile financial workflows.
Institutional use →Trust signals before execution
Complement existing fraud controls with contextual verification before a sensitive instruction becomes irreversible.
Institutional use →Authenticity around remote contact
Strengthen the distinction between expected institutional communications and impersonation, spoofing or social-engineering attempts.
Institutional use →Affiliation and mission verification
Support controlled confirmation of institutional identity, representation, validity, expiry or revocation status.
Institutional use →Protected business interactions
Help verify professional identity, payment changes, service instructions and sensitive remote interactions across organizations.
Institutional use →Institutional audiences
Designed for progressive integration with existing systems.
The public proposition addresses telecommunications operators, banks and financial institutions, Mobile Money and payment providers, insurers, enterprises, merchants and e-commerce operators, startups, digital platforms, public administrations and security-sensitive infrastructure operators.
- Telecommunications and Mobile Money trust services
- Additional controls for financial institutions
- Trusted enterprise communications and professional identity
- Merchant, e-commerce and platform integration
- Affiliation and mission verification for public or institutional environments
Trust & assurance
Complementary protection, controlled disclosure and careful claims.
Layered, complementary controls
TAA SECO is positioned as an additional trust and resilience layer, not a replacement for regulated authentication, banking, telecom or cybersecurity controls.
No serious system can guarantee the absence of cyberattack or fraud.Technology supports vigilance
The platform is designed to add system-level trust indications and controls when users must decide under uncertainty, urgency or pressure.
The objective is to reduce the burden placed entirely on human judgment.Documented status, careful claims
Patent procedures, project roles and corporate structuring are described using documented status rather than overstating granted or worldwide rights.
Confidential patent documentation and protected know-how remain outside the public repository.Public disclosureFunctional-level information only
Security detailsRestricted
Institutional pilotsControlled evaluation pathway
Production deploymentSubject to technical, legal and regulatory validation
Governance & structure
Technology leadership and international structuring, clearly separated.
TAA SECO is being developed under Divitia Holding Ltd with defined project roles and a progressive corporate architecture so partners can understand accountability without confusing project functions with corporate mandates.
View governance & structure →Lana II Aimé Rodrigue
Founder & Inventor
Directeur Technique / CTO — TAA & TPV / AOM Project
Head of Intellectual Property
Adrian Popoviciu
Strategic Co-Founder
Directeur Général / Managing Partner — TAA & TPV / AOM Project
Divitia Holding LtdTransitional structuring & incubation vehicle · England & Wales · Company No. 16990023
Intellectual property
Two distinct inventions, documented filing status and protected technical disclosure.
The TAA and TPV technologies are distinct inventions and are the subject of patent applications transmitted to and received by OAPI in March 2026. Documentary references associated with those procedures include PV No. 1202600119 and PV No. 1202600120, dated 19 March 2026.
The public website does not state that a patent has already been granted, that protection is worldwide, or that a PCT filing has already been completed.
Read the public IP statement →Pilot-first deployment
Evaluate feasibility before scale.
Institutional collaboration is intended to progress from priority use cases to technical feasibility, controlled pilot scope, governance and confidentiality, evaluation, and only then to progressive deployment.
Production use would remain subject to operator or institutional integration, technical validation, governance requirements and applicable regulation.
Partner, pilot & licensing approachInstitutional & strategic entry
Move from public information to a controlled discussion.
Banks, payment providers, telecom operators, public institutions, technology partners and strategic investors can begin with the public proposition and progress into a qualified institutional conversation. Restricted technical, legal or investment materials are shared only through controlled channels when appropriate.
Qualified inquiry
Tell us the institutional context.
Use the institutional contact route for partnership, pilot, technology integration, licensing, strategic capital, public-sector or post-compromise protection discussions.
Start an institutional inquiryInstitutional contact
Public information separated from protected technology by design.
This website is the approved public information layer. Restricted product specifications, sensitive security mechanisms, patent documentation and confidential commercial or legal materials are maintained outside the public repository.
Contact the Project →