Sumsub checks the format of crypto wallet addresses and transaction hashes before it accepts a transaction.

When the check runs

The check runs when you create or update a transaction. It applies to the following fields:

• applicant.paymentMethod.accountId
• counterparty.paymentMethod.accountId
• info.paymentTxnId

You can send these values with the following methods:

• Submit transaction for existing applicants
• Submit transaction for non-existing applicants
• Submit transaction with async scoring
• Submit transaction with async scoring for non-existing applicant
• Patch transaction with chain transaction ID
• Update wallet address

How the network is determined

Sumsub takes the network from info.cryptoParams.cryptoChain.

For a native coin with an empty cryptoChain, the network is taken from info.currencyCode (for example, BTC for Bitcoin).

Checked networks

Sumsub checks the following networks:

• all EVM chains
• Bitcoin
• Litecoin
• Dogecoin
• Tron
• Solana

Values for other networks (for example, XRP or Stellar) are not checked.

Validation rules

Error response

If a value is invalid, the API returns the 400 error. The description has the following format. If several values are invalid, the problems are joined with a comma:

Invalid wallet data for network <network>: <field> <reason>, <field> <reason>

Example:

{
  "description": "Invalid wallet data for network ethereum: applicant.paymentMethod.accountId EIP-55 checksum mismatch, info.paymentTxnId must be 64 hex characters with an optional 0x prefix",
  "code": 400
}

To fix the error, make sure that the wallet address and the transaction hash match the network from cryptoChain (or currencyCode for a native coin).

Valid values

The following are examples of valid wallet address and hash values.