Identity-bound sender
Identity and authority are bound to the submitted content.
Authenticated in sample flowA unified infrastructure combining party identity, secure delivery, electronic seals, trusted timestamps and evidence preservation so every material event can be independently checked.
Review licence and assurance recordsIdentity and authority are bound to the submitted content.
Authenticated in sample flowContent is handed over to the recipient domain under policy.
Handed over to recipient systemThe platform mirrors how Mobile-ID delivers the service: commercial engagement, trust assurance, integration and public disclosure.
Pain points, value, deployment models and tailored CTAs for business, technical and compliance audiences.
Explore solutions →Licence, certifications, policies, practices, security commitments and assurance reports.
Trust Center →REST API, OAuth 2.1, mTLS, webhooks, AS4/eDelivery, events and evidence packages.
Developer Portal →Documents with hashes, versions, status, publication sources and change history.
Public Register →Content adapts to decision-maker needs without sacrificing operational depth.
Standardize delivery, automate reconciliation and provide evidence when claims arise.
REST · OAuth 2.1 · mTLS · Idempotency · Signed Webhooks · AS4/eDelivery · OpenAPI 3.1.
Developer Portal →Clearly separate Vietnamese legal obligations, international reference standards and published internal policies.
Trust Center →Each stage produces an identity-bound, time-stamped and hash-linked event. “Handed over” does not automatically mean “read” or “accepted”.
The service receives content from an authenticated sender.
A content hash, event identity and transaction relationship are created.
The event receives a trusted time assertion.
Content reaches the recipient domain or information system.
Content is pushed to or retrieved by the recipient application.
eSeal, TSA, certificates and audit records are preserved under policy.
An operating and capability model aligned to trust-service controls; it is not a claim of qualified status in the EU Trusted List.
Certificates cover specific modules, devices or management systems; current maintenance status is disclosed transparently.
ISMS for the scope printed on the certificate.
SIS351224I008Biometric presentation attack detection assessment.
PCEB 26/04/06Electronic identification assurance level HIGH.
PCEB 26/04/07EAL 4+ augmented, AVA_VAN.5, ALC_FLR.3.
PCEB 26/04/09Connectors for banks, public authorities, VAN platforms, ERP, CA/TSA/HSM, e-contracts and AS4 interoperability. The list below illustrates an integration model and does not confirm commercial relationships.
Transaction notices and credit files
Administrative record exchange
Invoices and electronic receipts
eSeal, timestamp and certificate status
Workflow documents and approvals
Contract signing and handover
Sender and recipient identity
Claims and benefit notices
The Public Register manages licences, certifications, policies, operational certificates, hashes and version history.
TAYLLORCOX PCEB · PCEB 26/04/06
Open →TAYLLORCOX PCEB · PCEB 26/04/07
Open →TAYLLORCOX PCEB · PCEB 26/04/09
Open →SIS Certifications Pvt. Ltd. · SIS351224I008
Open →Demo data with demo/production control
Open →Portals, applications and integration assets are organized for individuals, organizations, technical teams and administrators.
Define the events to prove, identity assurance, evidence package, retention and integration model.