HiveAuth
HomeGitHub
  • Introduction
    • Authentication
    • Signing and Broadcasting Transactions
    • Why use Hive Authentication Services?
  • Support
  • Developer documentation
    • Protocol description
      • Authentication
      • Transactions
      • Challenge
    • HAS for Applications
      • Connection
      • Encryption key (auth_key)
      • Authentication
        • Authentication request
        • Authentication payload
        • Authentication approval
        • Authentication refusal
        • Errors
        • Expiration
      • Transactions
        • Transaction request
        • Feedback to user
        • Transaction approval
        • Transaction refusal
        • Errors
        • Expiration
      • Challenge
        • Challenge request
        • Feedback to user
        • Challenge approval
        • Challenge refusal
        • Errors
        • Expiration
      • Attach
  • HAS for Wallets (PKSA)
    • Connection
    • Server Encryption Key retrieval
    • Proof of Key
    • Account registration
    • Authentication
      • Authentication payload
      • Authentications request
      • Feedback to user
      • Authentication approval
      • Authentication refusal
      • Errors
    • Transactions
      • Transaction request
      • Feedback to user
      • Transaction approval
      • Transaction refusal
      • Errors
    • Challenge
      • Challenge request
      • Feedback to user
      • Challenge approval
      • Challenge refusal
      • Errors
  • Tutorials
    • App code example
      • HAS Wrapper library
      • HTML code example
      • .NET code example
    • PKSA code example
      • Service Mode
  • Resources
    • Materials
Powered by GitBook
On this page
  1. Developer documentation
  2. HAS for Applications
  3. Transactions

Transaction approval

If the user approves the transaction request with its PKSA, the latest will send a sign_ack message to the HAS. The HAS will then forward the following message to the APP:

sign_ack

{
    cmd: "sign_ack",
    uuid: string,
    broadcast: boolean,
    data: object
}
  • uuid: the transaction request identifier

  • broadcast: true if the transaction was broadcasted to the blockchain by the PKSA, otherwise false

  • data: contains either the transaction id (txid) if the transaction has been broadcasted or the signed transactions (signed_tx) if it has not been broadcasted.

PreviousFeedback to userNextTransaction refusal

Last updated 3 years ago