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. Altme Saas
  2. Beacon integration

Receive the Verifier data with a webhook in your backend

If you want to receive the data in your backend, create a webhook and copy the URL of the webhook in the page (“Webhook URL of your application”).

  • POST request with header Content-Type : application/json and in option an API KEY authentication ‘key’ : <your_key>)’

  • Event types : ‘VERIFICATION’ or ‘VERIFICATION _DATA’

Example :

{"event": "VERIFICATION", "id": "1234", "presented": "2022-11-15T14:59:43Z", "vc_type": ["Over13"], "verification": true}
  • event : string ‘VERIFICATION’ or ‘VERIFICATION_DATA’

  • id : string : The id passed through the call or the user blockchain address

  • presented : string : date of the user connexion

  • vc_type : ov13, over18, loyalty cards, etc

  • verification : Signature check

Event “VERIFICATION_DATA” : in that case the webhook receives the full verifiable presentations signed by the wallet with the verifiable credentials signed by the issuer.

Below an example of a webhook code in python :

from flask import Flask, jsonify, request

app = Flask(__name__)
app.config.update(SECRET_KEY = "abcdefgh") # Flask key
verifier_secret = 'c8f90f24-5506-11ed-b15e-0a1628958560' # take the client_secret from the platform https://talao.co

@app.route('/webhook', methods=['POST'])
def dapp_webhook() :
    if request.headers.get('key') != verifier_secret :
        return jsonify('Forbidden'), 403
    data = request.get_json()
    if data['event'] == 'VERIFICATION' :  # this is an event to catch a digest of the credential
        print(data)
        return jsonify('ok')

if __name__ == '__main__': #  use Gunicordn for production
    IP = "127.0.0.1"
    app.run( host = IP, port=4000, debug =True)
PreviousVerify the age of your users (+13, +18) in a dAppNextOn-chain and off-chain access with TezID

Last updated 2 years ago

☁️
📲