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

Account Lifecycle

To understand the components of Passport and where to implement them, we will break the implementation down into three primary components.

The workflow of a Passport account consists of three primary steps:

  1. Initial registration

  2. Post-registration logins

  3. Access to account utilities, smart contracts, and stored value/crypto.

In addition, Passport has created several useful front-end tools to provide default experiences for allowing users to log in and access the Passport services. These services can be invoked through method calls of the Passport object.

Passport has created similar interfaces to support each segment of this workflow. Registration and login are similar, except a different JavaScript event is called, which allows for an interstitial (though not required) step to capture additional one-time information (name, address, etc) as necessary. Once confirmation has been received by our servers through a link that is emailed and clicked Passport provisions blockchain accounts across several blockchains regardless of which blockchain is used this is the only time the registration process is necessary.

PreviousOverviewNextIntegration

Last updated 1 year ago