Documentação

English

Português
Español

English

Português
Español

Appearance

Deposit Synchronizations ​

Access Prerequisites

  • Permission (module): viewDeposits
  • License/Feature: DEPOSITS_HANDLING
  • Menu container: GENERAL → Operations group

What it is / when to use ​

A block reprocessing tool for the blockchain. The deposit watcher continuously reads blocks from the networks (EVM) to detect on-chain deposits and credit users. When a block was not processed (watcher outage, RPC unavailable, network delay) and an on-chain deposit did not appear in the customer's wallet, the operator provides the network and block number to force reprocessing of that block and capture the missing transaction.

Prerequisites ​

  • Permission: viewDeposits (dual permission — CPM enum + dynamic module in DB).
  • License/Feature: DEPOSITS_HANDLING enabled (without it the menu item does not appear at all).
  • Dependencies from other screens: the destination user of the on-chain deposit must have a mapped wallet; the block must contain a transfer to a monitored wallet in order to generate a credit.

Step by step ​

  1. Access the Operations → Deposit Synchronizations menu.
  2. Select the Network (e.g.: Ethereum, BSC, Polygon, Arbitrum, Optimism, Avalanche, Base, Moonbeam) — the list comes from getNetworks().
  3. Enter the Block number to reprocess (the field is trimmed; required).
  4. Confirm by clicking submit — calls reprocessBlock({ network, blockNumber }).
  5. Monitor the success or error feedback (snackbar).

Fields ​

FieldWhat it isRequired?System/backend effect
NetworkTarget blockchain for reprocessingYesDefines the chain queried by ExternalBlockchainProvider; validates against the list of enabled networks
Block numberBlock to reprocessYesTriggers re-reading of the block; transactions to monitored wallets generate a credit via FMS (idempotent by txHash)

Actions and modals ​

  • Submit: validates the form, trims the block number and calls reprocessBlock. On success, clears the form; on error, displays the message returned by the backend.

Business rules / cautions ​

Caution

  • Provide the exact block number. Reprocessing the wrong range will not create the missing credit.
  • If the network list fails to load, the screen displays an error — verify service availability before attempting to reprocess.
  • The tenant's default fiat currency and the USD→EUR bridge affect the reading/reconciliation of credited amounts.
  • Financial values: handled as BigNumber — no rounding.
  • Idempotency: the watcher is idempotent by txHash — reprocessing the same block multiple times does not duplicate credits. If FinLib returns E00021 "already processed", that deposit had already been credited (success).
  • APPROVED status: crediting the user presupposes a user with status APPROVED.