Technology / operating licence
Authorised use of approved TAA SECO technology or services within an agreed territory, field of use, term, governance framework and commercial scope.
Discuss this pathway →Licensing & institutional collaboration
Choose the pathway that matches how you want to work with TAA SECO.
TAA SECO can be evaluated through several licensing, integration and partnership structures. Depending on the use case, collaboration may involve TAA, TPV, SECO, AOM or the combined TAA-TPV framework. The public pathways below describe the commercial route only; protected technical mechanisms, IP, pricing, exclusivity and regulated deployment details are handled after qualification.
Core licensing models
Use, integrate or embed approved technology under a defined scope.
TAA and TPV are distinct inventions. SECO is a public security-identification code derived from TAA, while AOM is a service enabled by the TAA/SECO infrastructure.
Integration licence
Integration of selected TAA, TPV, SECO or AOM functions into an existing banking, payment, telecom, enterprise, platform or digital-service workflow.
Discuss this pathway →API / SDK integration
Controlled technical access for qualified partners where an API, SDK or comparable interface is appropriate to an approved deployment model.
Discuss this pathway →White-label / OEM
Embedding or presenting approved TAA SECO capabilities within a partner product, service or device under a defined brand and governance arrangement.
Discuss this pathway →Evaluation & market deployment
Start with evidence, then structure the appropriate commercial model.
Pilot / evaluation
A limited, measurable evaluation before broader commercial or institutional deployment. Pilot scope, success criteria and responsibilities are defined in advance.
Request a pilot discussion →Public-sector deployment
Deployment pathways for administrations and public-service environments, subject to procurement, regulatory, data-governance and institutional requirements.
Discuss a public-sector deployment →Reseller / distribution
Commercial distribution or market-development arrangements for qualified partners, with territory, responsibilities and permitted representations defined contractually.
Discuss distribution →Research / testing
Controlled research, testing or validation arrangements where the objective is evidence generation rather than immediate commercial deployment.
Discuss research or testing →Partnership pathways
Build together when a standard licence is not the right structure.
Development partnership
Joint product, integration or market-development work with explicit scope, deliverables, confidentiality, background IP, newly created IP and commercial responsibilities.
Explore a development partnership →Strategic partnership
A broader long-term relationship that may combine deployment, post-compromise protection, market access, institutional engagement, investment, licensing or co-development under a negotiated framework.
Explore a strategic partnership →Case-by-case structures
Visible for completeness, but never automatic rights.
These structures require specific legal, IP, governance and commercial approval. Their presence here does not constitute an offer, entitlement or pre-approved right.
Sublicence / assignment
Any sublicensing, assignment or transfer of contractual rights is considered only where expressly approved and documented. It is not an automatic right under a standard licence.
Request case-by-case review →Other / bespoke structure
Exclusivity, territory rights, IP-transfer elements, ownership changes, bespoke economics or other exceptional arrangements can be evaluated after qualification.
Discuss a bespoke structure →Not looking for a licence?