ZADA Network Member Manual: Issuing and Verifying Digital Credentials
Welcome to the ZADA Network Member Manual. This guide will walk you through the process of issuing and verifying digital credentials using our platform, which leverages Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs) for secure, user-controlled data sharing.
You can interact with the ZADA Network through two primary methods: the user-friendly ZADA Portal WebApp for managing connections and credentials, or the ZADA Core API for developers seeking direct integration into their applications and systems.
Table of Contents
Getting Started with ZADA
Introduction to the ZADA Network and platform overview.
Using the ZADA Core API
Developer integration tools and API documentation.
Credential Types & Connections
Hot vs Cold credentials and establishing secure connections.
Credential Varieties
Wallet, Foundational, and PDF credential formats.
ZADA Portal Operations
Login procedures and credential issuance workflows.
Verification Processes
Methods for validating credential authenticity.
Use Cases & Support
Real-world applications and obtaining assistance.
Getting Started with ZADA
For All Users
Access to a ZADA Wallet or compatible digital identity wallet capable of managing DIDs, establishing DIDComm connections, and storing/sharing Verifiable Credentials.
For Portal WebApp Users
A ZADA account, your ZADA Auth Credential (for secure login), and a web browser to access the interface.
For Core API Users
A ZADA Tenant account, your unique Tenant ID and Tenant Secret for API authentication, and a development environment capable of making HTTPS requests.
ZADA Credential Types: Hot vs Cold
Hot Credentials
W3C standard-compliant credentials for online verification.
  • Requires both parties to be online
  • Secure DIDComm connection
  • Real-time verification process
  • Enhanced privacy controls
Cold Credentials
PKI-based credentials enabling offline presentation.
  • Only verifier needs internet access
  • QR code presentation format (in App or as PDF)
  • Suitable for high-traffic scenarios
  • Works in limited connectivity environments
ZADA Credential Verification
Credential verification through the ZADA Network creates a secure trust ecosystem. Organizations receive pre-verified data without contacting issuers directly.
Trust Framework
Members adhere to governance standards ensuring immediate data reliability.
Secure Exchange
Verified credentials flow securely between trusted network participants.
Instant Verification
Recipients verify credential authenticity without contacting issuers.
Trusted Data
Organizations make confident decisions based on pre-verified information.
The ZADA Network eliminates redundant verification processes, saving time while maintaining data integrity across organizations.
Verifying Credentials
ZADA offers two approaches for verifying digital credentials:
Connection-based Verification
Select an established connection, initiate a verification request specifying required credentials or attributes, and send the request. The user approves sharing in their wallet, and results display on the Portal.
Connection-less Verification
Create a verification request generating a unique QR code. The user scans this code with their wallet, selects matching credentials, and approves sharing. The Portal updates automatically with verification results.
How Connections Work
ZADA Network uses the peer-to-peer DIDComm protocol to establish secure connections between issuers and recipients.
  • Issuer creates a connection invitation via Portal
  • Recipient receives and accepts the invitation
  • Secure DIDComm channel is established automatically
Creating a Connection
Recipients can establish connections through three convenient methods:
  • QR code scanning with ZADA Wallet
  • Deeplink activation via email or SMS
  • Adding a connection from inside the ZADA Wallet
Once connected, both parties can securely exchange credentials through their established Connection (DIDComm channel).
ZADA Credential Issuance
ZADA's credential issuance follows a strict governance framework designed to maintain trust across the ecosystem.
Issuer Verification
Organizations undergo rigorous onboarding to become authorized issuers within their domain.
Credential Authority
Issuers can only provide credential types within their verified jurisdiction.
Compliance Audits
Regular process audits ensure issuers maintain governance standards.
Trust Framework
All issuance follows standardized protocols maintaining ecosystem integrity.
For example, only authorized hospitals can issue vaccination certificates, preventing unauthorized credentials from entering the system.
Self-Sovereignty
Users maintain control of their credentials while enabling selective disclosure of information.
Secure Storage
All credentials are encrypted and stored locally on the user's device.
Credential Types: ZADA Wallet Credential
Every ZADA Wallet comes with an automatically generated baseline credential that serves as the first digital identity for users.
Unique DID
Decentralized Identifier that uniquely represents the wallet owner in the ZADA ecosystem
Verified Phone Number
Phone number that has been validated through authentication processes
Unverified User Name
Self-declared name provided by the user without verification
Credential Types: ZADA Foundational Credentials
Foundational credentials establish core identity within the ZADA ecosystem. These self-created credentials provide the basis for secure digital interactions.
Government IDs
Create digital versions of driver licenses, passports, and national ID cards directly in your wallet.
Regional Documents
Support for specialized credentials like Thai Pink Cards and other region-specific identifiers.
Official Documents
Store legally valid proof or evidence of specific facts, statuses, rights, permissions issued by a government body or another authorized institution
Credential Types: Other Ecosystem Credentials
Beyond foundational credentials, ZADA supports domain-specific credentials that enable powerful verification use cases across industries.
Organizational Memberships
Employee badges, access cards, and association memberships.
Education Achievements
Academic degrees, professional certifications, and training completions.
Healthcare Records
Vaccination certificates, insurance cards, and medical history.
Financial Documents
Transaction receipts, insurance policies, and loan agreements.
Event Credentials
Tickets, badges, and access passes that cannot be forged or transferred.
Supply Chain & Provenance
Certificate of origin for goods, chain of custody records, quality assurance attestations.
Legal & Contractual
Digitally signed agreement confirmations , power of attorney attestations.
Commerce & Loyalty
Verified customer status, loyalty program, proof of purchase for returns/service.
Travel & Mobility Credentials:
Digital visas, boarding passes, trusted traveler program memberships, car rental agreements, hotel bookings.
All credentials maintain user privacy through selective disclosure while enabling instant verification by authorized parties.
ZADA PDF Credentials
(Cold Credential)
Transform your digital credentials into professionally branded documents with ZADA PDF Credentials.
  • Custom-branded printable certificates with your organization's identity
  • Embedded QR codes enable offline verification
  • Built on Cold Credential technology for maximum accessibility
  • Ideal for certificates needing physical distribution or display
Recipients can proudly display credentials while verifiers can instantly validate authenticity without internet connectivity.
Example - Seamless Onboarding Online
(Connection-Based / Hot Credential)
ZADA's connection-based verification uses a connection to request the credential to be verified, also offering a simple organization onboarding process while maintaining security and privacy standards.
1
Phone Number Entry
User enters their phone number to initiate login or registration.
2
Connection Verification
System checks for existing connections. If none exists, displays QR code or deeplink to create connection.
3
Credential Request
Over the existing connection, system automatically requests verification of the Wallet ID Credential.
4
Authentication Complete
User approves the request in their ZADA Wallet. Registration or login completes instantly.
Example - Seamless onboarding Online
(Connection-Less / Hot Credential)
ZADA's connection-less verification simplifies the organization onboarding process while maintaining security and privacy standards.
Generate Verification Request
System creates a unique QR code when users select "Sign up with ZADA Wallet."
Credential Verification
Users scan the QR code with their ZADA Wallet, selecting which credentials to share.
Instant Account Creation
Organization receives verified credential data on their pre-defined webhook and automatically creates the user account.
No persistent connection required between organization and wallet. Verification happens seamlessly through the ZADA Network's trust framework.
Example - Seamless Onboarding In Person (Connection-Less / Hot Credential)
ZADA's physical verification streamlines in-person credential verification without requiring a connection.
Display Physical QR Code
Organizations place QR codes at entry points or registration desks.
User Scan
Attendees scan code with ZADA Wallet, selecting credentials to share.
Instant Verification
System verifies credentials against requirements in real-time.
User Identified / Registration Done
Upon successful verification, system grants immediate access or registration.
Loading...
Example - Seamless Onboarding In Person
(Cold Credential / Cold Credential)
ZADA's cold credential verification enables quick in-person verification of a users credential.
Present QR Code
User displays their cold credential QR code directly from ZADA Wallet or PDF Credential.
Verifier Scan
Staff scans the code using ZADA-enabled verification device or app.
Instant Validation
System immediately verifies credential authenticity against issuer records.
Verification Done
Upon successful verification, verifier can store the details or just dispose of it.
Loading...
Example - Automatic Issuance of Receipts
(Connection-based / Hot Credential)
ZADA streamlines document delivery through secure connections, eliminating the need for email, SMS, or paper records.
Established Connection
User has previously set up a secure P2P connection with the organization through their ZADA Wallet.
Activity Completion
After a transaction or service, the system automatically generates a verified credential receipt.
Instant Delivery
Credential is sent directly to the user's ZADA Wallet over the secure connection.
User Acceptance
User receives notification of the new credential and accepts it with one tap.
Works with payslips, medical records, shopping receipts, travel bookings, and more - all verified and instantly accessible.
Example - Extended KYC for Tailored Benefits
ZADA's verification system enables organizations to request specific credentials for enhanced KYC processes.
Request Additional Credentials
Organizations request specific credentials like student or employee IDs through customized verification flows.
User-Controlled Sharing
Users select which credentials to share from their ZADA Wallet, maintaining control over personal data.
Instant Verification
Cryptographically secured verification happens in seconds without need to contact the original issuer.
Personalized Experience
Organizations deliver tailored discounts, benefits, and services based on verified status.
Example - Decentralized Access Management
Educational Access
Schools issue student ID credentials directly to ZADA Wallets.
  • Learning portals verify credentials instantly
  • Library and lab access through smartphone scanning
  • Temporary guest passes for visiting scholars
Corporate Buildings
Each tenant organization manages their own access credentials.
  • Decentralized from building management
  • Organizations issue employee and visitor passes directly
  • Access revocation happens in real-time
Security Benefits
ZADA's credential system enhances security while simplifying processes.
  • Cryptographic verification prevents forgery
  • No physical cards to duplicate
  • Audit trail of all credential usage
Example - Auto-Populated Forms
Traditional Forms
Users manually enter the same data repeatedly across different services.
  • Time-consuming data entry
  • Error-prone information
  • Multiple accounts to manage
  • Security risks with stored data
ZADA-Powered Forms
Secure credential sharing instantly populates forms with verified information.
  • One-tap credential sharing
  • Verified, accurate data
  • User controls what's shared
  • No persistent data storage
Common Applications
Streamlines everyday form-filling across multiple sectors.
  • Travel booking details
  • Visa applications
  • Delivery information
  • Financial applications
Using the ZADA Core API
Authentication
Include your Tenant ID and Secret in request headers or obtain a short-lived access token.
API Integration
Construct API requests to issue credentials or verify existing ones programmatically.
User Interaction
Users still need to accept credential offers or approve verification requests in their wallet.
Result Handling
Process verification results via webhooks, polling, or synchronous responses per API design.
The full ZADA API Document can be access here https://documenter.getpostman.com/view/8801337/U16kq4zH
Using to the ZADA Portal
1
Navigate to Portal URL
Access the ZADA Portal URL provided by your administrator or documentation.
2
Authenticate with Wallet
Scan the QR code displayed on the Portal using your ZADA Wallet to authenticate your identity.
3
Approve Login Request
Confirm the login request within your wallet to complete the secure authentication process.
Issuing Credentials via the ZADA Portal
Find Connection
Find an existing connection, or create a new connection invitation (QR code or link) in the 'Connections' section and have the recipient scan or open it with their ZADA Wallet.
Issue Credential
Navigate to 'Issue Credential', select credential type and recipient, fill in required attributes, and click 'Issue' to send the offer.
Recipient Acceptance
The recipient must review and accept the credential offer in their ZADA Wallet to store it securely.
Batch Credential Issuance
1
Prepare Data
Create a CSV or JSON file with connection identifiers and credential attributes for each recipient.
2
Upload Batch
Navigate to 'Batch Issuance', select credential type, and upload your prepared file.
3
Sign & Send
Initiate the issuance process to send credential offers to all recipients, each one signed by you.
4
Individual Acceptance
Each recipient must individually accept their credential offer in their wallet and counter sign the credential.
Key Concepts & Support
DIDComm Connection
A secure, private communication channel between two DIDs, essential for sending credential offers and verification requests directly to a user's wallet.
Verifiable Credential (VC)
A digital, tamper-proof claim issued by an Issuer, held by a Holder (user), and verifiable by a Verifier.
ZADA Wallet
The user's application for managing their digital identity, connections, and credentials where they accept offers and approve requests.
User Control
Users always control their data and must explicitly consent before any credential information is shared or accepted.
ZADA Verification Applications
VeriFlow
Build custom verification workflows tailored to your organization's specific needs. Design multi-step verification processes with conditional logic.

See one custom deployment at https://www.myzada.info
Verify
Quickly authenticate cold credentials by scanning QR codes or uploading documents. Perfect for on-the-spot identity verification.
https://verify.zadanetwork.com
QR Scanner
Scan credential QR codes and create custom actions based on verification results. Integrate with your existing systems.
https://qrscanner.zada.solutions
Demos of using ZADA for online services
Frequently Asked Questions
What is the ZADA Network?
A decentralized network for processing verifiable credentials without storing user data.
How does ZADA handle data?
ZADA only processes credential issuance and verification. No personal data is stored on the network.
Are credentials secure?
Yes. Credentials use cryptographic proofs that ensures they are tamperproof and they are encrypted in the wallet and when shared.
Who controls credential data?
Users maintain full control through their ZADA Wallet. Sharing requires explicit consent.
5
Can I Revoke Credentials
Yes. The issuer can mark credentials as revoked, which a verifier will see when he verifies a credential.
Can I revoke access?
Yes. The issuer can revoke a credential, and the system controlling access will know the credential is revoked.
Support & Technical Assistance
ZADA provides comprehensive support to help you implement and maintain your credential solution. Our team is available to assist with technical questions, implementation challenges, and best practices.
Documentation
Access detailed guides, API references, and implementation examples in our knowledge base.
Connect with our technical team via chat or scheduled video calls for personalized assistance.
Community Forum
Join discussions with other ZADA members to share experiences and solutions.
Developer Resources
Access sample code, SDKs, and development tools to accelerate your integration.
Contact our support team at support@zada.io or through your dedicated account manager for specialized assistance with your implementation.