Altme's documentation
  • 🧾Introduction
    • 📋What is Self Sovereign Identity ?
    • 🕵️Altme solution suite is made up of 3 components
      • 🗂️Altme Wallet
      • 📇Altme Saas
      • 📇Altme Web3 issuer
    • 🗂️Give an Identity to your crypto wallet
    • 🛠️Technical considerations
  • ☁️Altme Saas
    • Quick start
      • ⬇️Download Altme Wallet from Apple or Google store
      • 📁Get more credentials in your wallet
      • 🔒Connect to the Altme Saas platform to setup a SSI verifier
      • 📲Integration in your app
    • Beacon integration
      • 🖥️Overview
      • 🏅Verify the age of your users (+13, +18) in a dApp
      • 📲Receive the Verifier data with a webhook in your backend
      • 🪙On-chain and off-chain access with TezID
      • 💾Verify other data with other credentials
      • 📇Issue a Welcome card in a dApp
      • ✅Check user data of your Issuer (no code)
      • ✅Check user data of your Issuer with a webhook
      • 🕵️Under the hood : the process flow of a Beacon Verifier
    • OpenID integration
      • 🖥️Overview
      • 1️Example 1 with an “implicit flow” with no code
      • 1️Example 1 with an “authorization code flow” in Python
    • EBSII integration
  • 🗂️Alme Wallet
    • Protocols overview
      • 🔑Collecting a verifiable credential
      • 🔑Requesting a verifiable presentation
    • Credential offer protocol
      • 🧘‍♀️Motivation
      • 📖Issuer implementation
    • 🖥️Credential manifest of the credential offer protocol
    • 💰Wallet rendering
      • 📝Input descriptors
    • Presentation request query types
      • 🧘‍♀️Motivation
      • 📖Verifier implementation
      • 🔐DIDAuth
      • QueryByExample
      • QBE Examples
    • ✅Issuers and Verifiers return codes accepted by wal
    • 🔗Universal link
      • 🖥️Access from a desktop viewer
      • 📱Access from smartphone viewer
  • *️Others
    • 📂Flow between wallet, dApp and Verifier
      • 📱Hybrid dApp onboards a user with VCs
      • 📱dApp onboards a user with VCs
      • 📱dApp adds a user in whitelist
    • 📍Indices and tables
      • 📁Index
      • 🔍Search
    • 👨‍💻Show source
Powered by GitBook
On this page
  1. Introduction
  2. Altme solution suite is made up of 3 components

Altme Saas

PreviousAltme WalletNextAltme Web3 issuer

Last updated 2 years ago

Altme Saas is a low code solution to build Issuers and Verifiers in minutes

Altme Saas is a next-generation platform to integrate Decentralized Identity solutions in an application.

Altme Saas is a no code or low code platform to generate issuers and verifiers. The platform is an open source project : ​

To use Altme Saas, you don’t need to learn Verifiable Credentials standards, DIDs signature or how to work with a complex an unstable SDK.

Instead, Altme Saas uses OpenID for Web2 aplications and dapp-to-wallet protocols for Web3 applications as a simple and familiar method to integrate issuers and verifiers. All the complexity of the protocols and standards used by SSI wallets are managed by the platform. You can focus on your application and leave Altme Saas manages authentication, identification or credential issuance.

For web2 applications Altme Saas is compliant with NodejS, Python, Ruby, Go, C, PHP, Java, Wordpress, Webflow….

For web3 applications Altme Saas supports WalletConnect and Tezos Beacon.Documentation :

  • Go to for a quick startup

  • Go to for an OpenID integration

The Altme Saas platform is in Beta, access is free :

🧾
🕵️
📇
https://github.com/TalaoDAO/sandbox
https://altme-documentation.gitbook.io/altmes-documentation/altme-saas/quick-start
https://altme-documentation.gitbook.io/altmes-documentation/altme-saas/openid-integration
https://talao.co