Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Steps

  1. Submit a request in accordance

with the
  1. with the details in Sign transaction for the application.

  2. The platform

retrieves the details of the requesting application and the server accountThe platform retrieves the details of the organisation to which application belongs
  1. validates the request, by verifying, among other things:

    1. that the transaction is specified in the TransactionRequest.

    2. whether or not the participant's access to the transaction has been revoked.

Info

Refer to the serviceType ‘REVOKE’ in the API endpoint Service. A revoked participant cannot sign the transaction.

c. whether or not the transaction can be opened and signed.

Info

Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER in the API endpoint Service.

  1. The platform unlocks and opens the transaction

required
  1. to sign.

  2. The platform signs the transaction.

  3. The platform updates the signed-status of the

archived
  1. transaction

with
  1. in the

signed details
  1. archive.

  2. The platform returns the ParticipantStatusResponse

 with the ParticipantStatus.
plantuml
  1. .

Plantumlcloud
toolbarbottom
filenamePlantUML Diagram 1.svg
originalHeight358
datanVTRbtswDPwaY08pZKUZ+uo4KfaQbsHSPReqRSdCZMqT5GzY14+0uiTWWqyYbQQBeXc6nmQXtyJE5ePQ2UJUHx6h662KUMyrQorFk3wSXF6dS3TPZ2U5k1wPR4O98qqjhoZWDTbeO4yfVQdU+QT2BNE0KkPu4PsA2MADhKD2UFmzRyo3gBF8hv3qBtS180gdKcpF1t6Sc9OYXmFcOq/B1846Rj5b1RzzdQ9Kux8G9/S/VTbAX2Jap26+zL1zZI1H+6NfyLkYrzeRO/OLQyglITJQeAngZmNa2BiEJZnd+zTqWR/u+P4ndTL2tS16Dkazh5ZMPbufqdZfIhsJsup7S5sUjaNdkFRTgX426yrp1WJ1t5KvETfkxSDpSsFnpnW+uxbYvvA/rtbr+t188nitUf6fyHIiIjORSzIDWoNH0KmommhOfNLT+KJKIcyK+ToNNL4Bu3Rco1cYmMGxUcQcfzwwV10FOhXdpnXGaDLVLXj2zoZPyho90sMb4C89YMg8vI5ks+9DfutpTQjnKQIxQc/o4xAHrrqWU1zUmNrT8Q1epvfNwZwgTeohDp57jxP4WTTFdr2pI01Dntq0Mm5OcSsANX23fgM=
compressedtrue
originalWidth486
revision3