OffBlocks
  • πŸ‘‹Welcome to OffBlocks
  • Overview
    • πŸ’‘What we do
    • ✨Core Concepts
    • πŸ“œWhitepaper
    • ⛓️Supported Blockchains and Assets
    • ❔FAQ
  • Developer Guides
    • πŸ—οΈSystem Architecture
    • βš™οΈAPI Integration
      • πŸš€Getting Started
      • πŸ“―Postman
      • πŸ”‘Authentication
      • πŸ”Request Signatures
      • πŸ†”Idempotency
      • ⛓️Blockchain Identifiers
      • πŸ“’Blockchain Updates
      • πŸ“²Sign in With X
      • πŸ’°Fees
      • πŸ•ΉοΈSimulator
      • πŸ”’API Reference
        • πŸ¦Έβ€β™‚οΈCustomers
        • 🏦Accounts
        • πŸ’³Cards
        • πŸ”ƒTransactions
        • πŸͺWebhooks
        • πŸ•ΉοΈSimulator
        • πŸš‚Engine
      • ⏭️States and Transitions
        • πŸ¦Έβ€β™‚οΈCustomer States
        • 🏦Account States
        • πŸ’³Card States
        • πŸ”‘Authorisation States
        • πŸ”ƒTransaction States
    • 🧬Smart Contracts
      • OffBlocksEscrow.sol
      • OffBlocksSmartWalletFactory.sol
      • OffBlocksSmartWallet.sol
      • PendingWithdrawal.sol
      • Interfaces
    • πŸ”’Step-by-step Guide
      • 1️⃣API Credentials
      • 2️⃣Authentication
      • 3️⃣Request Preparation
      • 4️⃣Customer Creation
      • 5️⃣Customer Verification
      • 6️⃣Account Creation
      • 7️⃣Card Issuance
      • 8️⃣Card Authorisations
      • 9️⃣Webhooks
  • Use Cases
    • πŸ’°Wallet Providers
    • πŸ§‘β€πŸŒΎDeFi Apps
    • 🏦Neo-banks and FinTechs
Powered by GitBook
On this page
  1. Developer Guides
  2. API Integration
  3. States and Transitions

Account States

PreviousCustomer StatesNextCard States

Last updated 1 year ago

  • initiating - an initial Account state. This state is immediately assigned to an entity created using endpoint provided it has passed basic validations (such as whether the input is correct, requested currencies are supported and customer is active). If validations were failed, account is transitioned to failed state. At this stage we expect an account challenge to be signed and verified before proceeding to next states. Upon successful challenge verification an entity is transitioned to pending state

  • pending - an Account is being deployed on-chain. Upon completion it is transitioned to active and chainId is assigned

  • active - an Account has been successfully deployed and is ready to be used to issue cards and perform payments. An entity can be temporarily deactivated in case of any issues or if we suspect any illicit activity. In this case an entity is transitioned to inactive state. You can also deactivate Account yourself using endpoint. If we have evidence of any illicit activity received through our constant monitoring workflows, an entity is transitioned to closed state

  • inactive - an Account entity is temporarily deactivated. It can be re-activated again on our end or using endpoint

  • closed - an Account has been closed and is no longer available for our services. This can be done via endpoint. This is a final state

  • failed - an Account creation request has failed some of the validations. A new request must be submitted. This is a final state

βš™οΈ
⏭️
🏦
#customers-customerid-accounts
#accounts-accountid-deactivate
#accounts-accountid-activate
#accounts-accountid-1