Skip to content
Custody Docs Paribu Custody

Transactions

Transaction List

Section titled “Transaction List”

The Transactions page is where the user can view all transactions within the selected workspace. Transactions are listed in two categories: Transaction History and Pending Transactions.

  • Transaction History lists details of completed deposits, sweeps, and transfers.
  • Pending Transactions displays the current stage of ongoing transfers.

Transaction Types

Section titled “Transaction Types”
  • Transfers: Transactions made from the current workspace.
  • Deposits: Transactions made to the addresses within the workspace.
  • Sweep: The automatic transfer of the balance deposited to proxy addresses into the main address of the relevant asset in the vault.
  • Stake: The process of locking a selected asset from the wallet in the current workspace for a specified period of time.
  • Unstake: The process of unlocking assets that were previously locked through a staking transaction.
  • Rewards: Earnings from staking assets.

Transfer Types

Section titled “Transfer Types”

Internal Transfer is a transfer type where both the source and destination addresses are within the workspace.

  • The transfer can occur between vaults within the workspace.
  • This can be done by transferring a balance from a vault within the workspace to the gas fee assistance address.
  • The balance in the proxy wallet address is transferred to the main wallet address.

External Transfer is a transfer type in which the balance is sent to an address outside the selected workspace.

  • These transfers can be made to whitelisted or non-whitelisted addresses.

Transaction Statuses

Section titled “Transaction Statuses”

The transaction statuses in the Transaction History table are as follows:

  • Success: All transaction processes have been completed successfully.
  • Failed (System): A transaction error occurred. The transferred balance will be returned.
  • Failed (Network): A transaction error occurred on the blockchain. The transferred balance will be returned.
  • Canceled: The requested transfer was canceled and not completed.
  • Blocked by policy: The transfer triggered a “block” action rule in the workspace policy. The transfer was halted due to a policy rule.
  • Non-whitelist block: When the workspace is restricted from transfers to non-whitelisted addresses, any transfer attempt to such addresses will be blocked.
  • Expired: The approval or signature process required for the transfer has passed its expiration date. The transfer has been stopped.
  • Rejected: The transfer was denied by a user during the approval or signature process.
  • Dropped: In certain networks, a transfer that was blocked has been re-submitted with updated information, namely that transfer has been dropped.
  • Replaced: In certain networks, a blocked transfer has been resubmitted with the same nonce and a higher gas fee.
  • Blocked by system: The transfer could not be processed due to a policy version change in the system.
  • Blocked by AML: The transfer has been blocked because it does not comply with Anti-Money Laundering (AML) regulations.

The transaction statuses in the Pending Transactions table are as follows:

  • Waiting approval: The transfer is awaiting approval from the designated individuals according to the policy rules. Transfer approval is pending.
  • Waiting for your approval:
  • Waiting for signature: The transfer is awaiting signatures from the designated individuals according to the policy rules. Transfer signature is pending. The process will be completed once the individual signs off on the transfer.
  • Waiting broadcast: A created transfer has been signed and is waiting to be broadcast to the chain.
  • Broadcasted: A transaction has been broadcast to the chain and is waiting to be included in a block.
  • Awaiting confirmation: The transaction is waiting to receive a sufficient number of confirmations for deposit completion.

Export

Section titled “Export”

The export feature on the transaction list page enables users to report transactions from the past six months in Excel format by selecting a start and end date.

Create Transfer

Section titled “Create Transfer”

Balances can be transferred internally or externally through the Paribu Custody interface. Transfers can be initiated from different sections of the application. By clicking the New Transfer button, the user can complete the transfer by following these steps.

  • The user begins by selecting the asset they wish to transfer.
  • The available networks for transactions with the selected asset are displayed. If only one network is available, it is selected by default and cannot be modified.
  • The vaults holding the selected asset in the From field are displayed.
  • The To field is populated based on whether the transfer is internal or external. For an internal transfer, a vault from the list in the To field is selected. For an external transfer, the user selects either a Whitelisted or Non-Whitelisted address option. If a whitelisted address is selected, the registered whitelisted addresses within the workspace are displayed. If a non-whitelisted address is selected, the address must be entered manually in the To field.
  • If the entered address is incompatible with the selected network, an error will be displayed.
  • The available balance is displayed in the Amount field, and the user specifies the amount to be sent.
  • After pressing the Continue button, the Transfer Confirmation screen is displayed.
  • The user approves the transfer transaction, and a confirmation request is sent to the mobile devices of the users specified in the policy rule for the relevant transaction.
  • At this stage, the transaction is listed in the Pending Transactions table.
  • Once the signing process is complete, the transaction is listed on the Transaction History page.

Cancel Transfer

Section titled “Cancel Transfer”

The transfer can be canceled from the Pending Transactions tab before the signing process is completed. Cancellation can be made by the transfer owner and admin quorum members.

  • The user clicks the Cancel button to initiate the cancellation.
  • The transfer’s source and destination addresses are displayed. The user may add a note explaining the cancellation.
  • The transaction is canceled upon clicking the OK button.
  • The transaction appears as Canceled on the Transaction History page.

Withdraw from Main Address

Section titled “Withdraw from Main Address”
  1. Create Transaction Retrieve the workspaceId and fromVaultId information from the Get Workspaces endpoint.
  2. Get Ceremonies For the created transaction, obtain the queued ceremonies via the Get Ceremonies endpoint.
  3. Build Transaction Generate the message to be signed for the transaction. The transaction ID can be obtained from the Get Ceremonies endpoint.
  4. Sign Retrieve the following details from their respective endpoints:
    • organizationId, workspaceId, vaultId, curve from the Get Ceremony Details endpoint.
    • path from the Get Address endpoint.
    • userId from the Me endpoint.
  5. Check Transaction Verify the transaction status using either the Get Ceremony Details or Check Transaction endpoints.

Sweep from Proxy Address

Section titled “Sweep from Proxy Address”
  1. Get Proxy Deposits Retrieve the proxy deposits along with the details of operations available for sweeping.
  2. Select Proxy Deposits Submit the selected ID values from the Get Proxy Deposits endpoint via this endpoint.
  3. Get Ceremonies For the created transaction, obtain the queued ceremonies via the Get Ceremonies endpoint.
  4. Build Transaction Generate the message to be signed for the transaction. The transaction ID can be obtained from the Get Ceremonies endpoint.
  5. Sign Retrieve the following details from their respective endpoints:
    • organizationId, workspaceId, vaultId, curve from the Get Ceremony Details endpoint.
    • path from the Get Address endpoint.
    • userId from the Me endpoint.
  6. Check Transaction Verify the transaction status using either the Get Ceremony Details or Check Transaction endpoints.