Products

In order to enable Financial Operations, it is necessary to create customer products. This document outlines product definitions, as well as creating and managing customer products.

Products definitions

Product name	productType	productCode	Description
Balance	CASH	BALANCE_ACCOUNT	Balance account in EUR for natural persons or legal entities
Depository	DEPOSITORY	DEPOSITORY_ACCOUNT	Depository account for natural persons or legal entities
Wallet	WALLET	CURRENCY_WALLET	Crypto token wallet for natural persons or legal entities

Finding updated product definitions that are already or could be potentially available for partner, is always available with Get Product Definitions.

Products dependencies

To better understand how different types of customer products support specific financial operations, it's helpful to look at the core dependencies by use case. The following section breaks down which account types are required for common scenarios, and how each component plays a role.

• Cash top/ups/payouts are possible with BALANCE_ACCOUNT only.

• Traditional asset trading requires operations on DEPOSITORY_ACCOUNT and BALANCE_ACCOUNT . In this case BALANCE_ACCOUNT reserves/settles cash, while DEPOSITORY_ACCOUNT holds positions; corporate actions post to Depository.

• Crypto trading/custody will run only with active BALANCE_ACCOUNT and CURRENCY_WALLET . BALANCE_ACCOUNT is necessary for transfers with fiat currency and fees. CURRENCY_WALLET is required for on-chain assets custody.

Creation & lifecycle

Understanding products creation and lifecycle of customers products is essential for smooth usage of the platform. The following section covers possible products actions and redirects to the right API references.

• Create products per customer with POST /customers/{customerId}/products.

• Update status with PATCH /products/{customerProductId} (e.g., CLOSE).

• Cash movements via POST /transfers (SEPA-style); get full details of a transfer with /transfers/{transferId}.

• Trades via /trading/order/{type} (market/limit/stop) and /trading/order/{orderId} (updates/cancel).

• Current balances and positions (cash, securities, crypto) via:

  • GET /customers/{customerId}/products

  • GET /products/{customerProductId}

  • Includes availableBalance vs withdrawableBalance (cash) and quantity vs availableQuantity (positions).

• Event-level ledger of movements (trades, settlements, transfers) via:

  • GET /customers/{customerId}/transactions

  • GET /transactions/{transactionId}

Product Status and Compliance

Customer products can transition to BLOCKED status due to regulatory compliance requirements. Key scenarios include:

• Missing Tax Identification Number (TIN): Under German tax office regulations, customers are required to have a valid TIN on file. If a TIN is not provided within the regulatory grace period (90 days), all associated products (BALANCE_ACCOUNT, CURRENCY_WALLET, DEPOSITORY_ACCOUNT) will be automatically blocked. This applies to both natural persons and legal entities.

• Entity suspension: If the underlying entity (natural person or legal entity) is suspended or blocked for compliance reasons, all associated products are also blocked.

To resolve a BLOCKED status caused by missing tax information:

1. Ensure the required TIN is provided via the entity update endpoint.

2. Both the entity and the customer role must return to ACTIVE status before products are unblocked.

3. If the TIN was not provided within the 90-day regulatory period and the account has been suspended, the partner must contact the Tradevest support team to initiate the unsuspension process.

4. Product status changes are communicated via webhook notifications.

Monitor release notes: Compliance enforcement rules may be introduced or updated in platform releases. Partners should regularly review the release notes to stay informed about regulatory changes that may affect existing customers.

Operational notes

• BALANCE_ACCOUNT is prerequisite for any activity that settles fees or fiat legs.

• One customer can hold multiple BALANCE_ACCOUNT, DEPOSITORY_ACCOUNT, CURRENCY_WALLET; trading endpoints select the right product via IDs.

• For traditional assets, trades are executed T0 but settle on T+2:

  • On T0: cash reserved (availableBalance ↓), position booked in quantity.

  • On T+2: withdrawableBalance adjusted, availableQuantity updated.

• Securities bought are immediately visible and can be sold again (exposed in quantity), availableQuantity is the difference between blocked assets from e.g. limit orders and quantity.

• Cash proceeds from a sale are available for new trades right away (availableBalance), but only withdrawable after settlement (withdrawableBalance).