Active Management

​

Overview

CryptoMate’s Active Management product lets businesses manage their clients’ digital assets through an integrated Wallet and Holding Wallet system. Deposits are received on dedicated addresses, while the real assets are consolidated in a secure, company-managed holding wallet. The product is built on top of Polygon, BNB Chain, and Tron, providing a robust, transparent, and scalable foundation for business operations.

​

Supported tokens

The tokens available for use across each blockchain are the default listed tokens plus any custom tokens your company has registered. You can consult the full list at any time via the List custom tokens endpoint.

​

Core concepts

​

Deposit-to-holding flow

​

Managing virtual wallets

Deposits and withdrawals. Clients can deposit and withdraw funds as needed from their virtual wallets. Withdrawals to external wallets. When funds are withdrawn from a virtual wallet to an external address, the assets are deducted from the holding wallet, ensuring a real transfer of funds. Transfers between virtual wallets. Internal transfers between two virtual wallets are simple virtual balance movements — no blockchain transactions occur. This prevents unnecessary holding wallet deductions for in-ecosystem operations.

​

Managing the holding wallet

​

Company clients and ramp operations

​

What is a company client?

A company client is an end user that has completed KYC verification and can perform ramp operations (fiat-to-crypto and crypto-to-fiat).

​

Client-wallet relationship

• One wallet → one client. Each virtual wallet is associated with exactly one client.
• One client → multiple wallets. A client can own multiple wallets across blockchains or purposes.
• Active wallets only. Only wallets in active status can be associated with a client.

​

Prerequisites for ramp operations

​

On-ramp (fiat → crypto)

1. The client initiates an on-ramp request and receives fiat deposit information.
2. Funds are received and verified.
3. The equivalent amount of cryptocurrency is credited to the client’s virtual balance.
4. The real assets are held in the holding wallet; the client’s virtual balance reflects ownership.

​

Off-ramp (crypto → fiat)

1. The client initiates a withdrawal from their virtual wallet to their bank account.
2. The system deducts the virtual balance.
3. Real cryptocurrency is transferred out of the holding wallet for fiat conversion.
4. Fiat currency is sent to the client’s linked bank account.

​

Colombian Peso (COP) ramps

COP ramps support two payment rails with different user experiences. You select the rail per operation by sending payment_rail in Create bank ramp-on; for ramp-off the rail is inferred from the destination bank account.

​

CO Bank Transfer (PSE)

PSE (Pagos Seguros en Línea) is a redirect-based flow. When you create a ramp-on with payment_rail: "co_bank_transfer", you must also send a redirect_url — the URL will send the user back to after they authorize the payment with their bank.

1. You call Create bank ramp-on with source_currency: "COP", payment_rail: "co_bank_transfer", and a redirect_url.
2. The response includes a start_url — redirect the user there to begin the PSE checkout in their bank’s interface.
3. The user selects their bank, logs in, and authorizes the COP transfer.
4. After authorization the user is sent back to your redirect_url.
5. Bridge processes the payment, credits the equivalent crypto amount to the virtual balance, and emits a ramp_on webhook event.

​

Bre-B

Bre-B is a key-based flow — no redirect. When you create a ramp-on with payment_rail: "bre_b", the response includes a bre_b_key that you display to the user.

1. You call Create bank ramp-on with source_currency: "COP" and payment_rail: "bre_b".
2. The response includes a bre_b_key — display it to the user so they can copy it.
3. The user opens their bank app, chooses “Pay with Bre-B”, pastes the key, and sends the COP.
4. Bridge processes the payment, credits the equivalent crypto amount to the virtual balance, and emits a ramp_on webhook event.

For ramp-off the client must have an existing Bre-B bank account registered with the destination Bre-B key. Funds are sent from the holding wallet to that account.

​

Webhooks

Active Management emits events with product: "virtual_wallets" so you can drive your UI and accounting as soon as funds move. Register a webhook URL and webhook_key from the Portal (or via the Subscribe webhook URL and Subscribe webhook key endpoints). See Webhooks for the full envelope, authentication via X-Webhook-Key, retry behavior, and payload examples.