Versions Compared

Old Version 11

changes.mady.by.user Technical writer (Unlicensed)

Saved on

compared with

New Version 12

changes.mady.by.user Technical writer (Unlicensed)

Saved on

Key

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


Info

The Lequinox platform does not archive transactions for external role accounts or external personal identities as they represent another organisation.


Steps

  1. Submit a request in accordance with the details in Open transaction as a platform-managed user.
  2. The platform performs the following validations:
    1. If the participant of the transaction is revoked. Refer to REVOKE of Service.
    2. If transaction can be opened and is not locked. Refer to TIMELOCK_BEFORE and TIMELOCK_AFTER of Service.
  3. It then The platform opens the transaction.
  4. The platform archives the opened status of the transaction along with the timestamp.
  5. TransactionMessageResponse is returned.


Plantuml


Error messages

Expand
title


HTTP status codeMessageComments
400Input not valid: Participant can not be null.This error message is returned if the 'user' parameter of ManagedUserTransactionRequest is missing.
400Input not valid: Transaction can not be emptyThis error message is returned if the 'transaction' parameter of ManagedUserTransactionRequest is missing or is empty.
400An error has occurredThis error message is returned if the transaction data of ManagedUserTransactionRequest is not in the correct format.
400Input not valid: Participant can not be of unknown type: null

This error message is returned if

400Input not valid: Participant corporateId can not be null for corporate or server user.
400

Input not valid: Participant applicationAccessId can not be null for private or corporate user.


400Input not valid: Participant privateId can not be null for private or corporate user.
400Unknow errorThis error message is returned if a wrong 'type' is specified for User. For example, a CORPORATE type is mentioned as SERVER.
500
  • An unexpected error occurred: JSON parse error: [...]
  • An unexpected error occurred: Type definition error: [...]
These error messages are returned if one or more parameters are of the wrong type.