Passport SDK v5.0
  • Overview
  • Account Lifecycle
  • Integration
    • Client Side Enablement
    • Credenza Presence (Optional Visual Elements)
    • Account Provisioning (Sign-up)
      • New Authentication System
      • Existing Authentication System - New Customer
      • Existing Authentication System - Existing Customer
  • Passport Subsequent Logins
  • Post-Login Capabilities
    • Account Information Access
    • Blockchain Wallet Access
  • Smart Contract Interactions
    • Instantiating The Contract Object (Server-Side)
    • Instantiating The Contract Object (Client-side)
    • Calling Contracts
  • Monetary Transactions
  • Appendix I: Passport Configuration Options
    • Magic
    • Ethers.js
    • Installation
    • Usage
    • Passport Instance Properties
    • Passport Static Properties
    • Modes
    • Supported query params
  • Transaction UI v3.0 (now part of Passport)
    • Magic
    • Ethers.js
    • Installation
    • Usage
    • Apple Pay
    • Google Pay
    • Methods
    • Events
  • Appendix II: MetaMembership Contract Access
  • Appendix III: Ledger Contract Access
  • Appendix IV: Decentralized Commerce Configuration
Powered by GitBook
LogoLogo

©2023 Credenza. All rights reserved.

On this page

Overview

Understanding the basics of Passport

Email feedback@credenza3.com for comments or questions regarding this document.

Credenza Passport is a password-less authentication mechanism that gives account owners access to a custodial blockchain wallet that runs across several blockchains, including Ethereum, Polygon, and Binance Smart Chain. Using the Credenza Passport SDK, any client site can embed this functionality to allow a customer to connect their Credenza Passport wallet and subsequently lookup assets (NFTs, crypto, etc) contained within the wallet to provide additional benefits or privileges associated with a blockchain-aware membership.

There are three layers of accessible functionality to the Passport product at the foundational level, Passport serving as an authentication mechanism.

  • It operates without a password, so it requires external authentication (email link) can you validate an account. This allows for confirmation that the owner of the account is indeed requesting access and avoids forgotten or leaked passwords. Passport confirmed the user a date set up services on behalf of the user, including the ability to generate a dynamic scannable code that can be read by Credenza Scanner code to validate accounts in a physical setting.

  • The next level of Passport functionality allows it to interact with smart contracts, especially those built and licensed by credenza. Passport provides a critical abstraction that makes our smart contracts as easy to program against as any API thanks to our Javascript libraries. As you’ll see, we have the ability to map the contract to the blockchain based on the contract schema (known as a “Application Bytecode Interface” or ABI) service coupled with a blockchain address for the contract to create a Javascript object as if it were on the local device.

  • Finally, Passport will serve as a payment authorization system, whether using cryptocurrencies or Credenza-provisioned stored value wallets. Credenza has a standard ERC20 contract to represent stored value and can created unique “tokens” for clients. In addition, we can leverage existing cryptocurrencies and also support Stripe to be able to handle fiat currencies like dollars through credit cards.

Our goal has been to make Passport as painless as possible to implement. In addition, our focus is on flexibility and managing any situation, whether it be an existing application that retroactively migrates all users or brand-new application solely dedicated to running Credenza apps and services. This guide will walk through the implementation of each scenario and the subsequent operation in management of the accounts. In addition, perhaps the greatest strength of Passport is it ability to be a programmable wallet that not only allows access to information about the user’s assets, attributes, and crypto balances, but also perform actions on the blockchain on behalf of the user. This guide will provide details on how to best use this technology to establish an identity with associated blockchain accounts, access Credenza’s smart contracts, and perform financial transactions using Credenza stored value contracts or 3rd-party cryptocurrencies that run on EVM-compliant blockchains.

NextAccount Lifecycle

Last updated 2 years ago