Overview

System Workflow Overview

This section describes the standard operational workflow of the system, from initial setup through address generation, deposit tracking, and withdrawals.

1. Initial Setup & Technical Enablement

As part of the onboarding process, the technical teams collaborate to enable secure transaction operations within the customer’s environment.

During this phase:

• A dedicated signing executable is provided to approved customers

• The executable is deployed and operated on the customer’s infrastructure

• The platform provides guidance for installation, configuration, and validation

This setup ensures that signing operations are performed in a controlled and automated manner.

2. Wallet Initialization & Public Key Registration

2.1 Wallet Initialization

Once the signing service is operational:

• Wallets are initialized for the supported blockchains

• Wallet generation follows deterministic standards to ensure consistency and traceability

• The process is fully automated and requires no manual intervention after setup

2.2 Public Key Reporting

After wallet initialization:

• The signing service automatically reports the corresponding extended public keys (XPUBs) to the platform

• Only public, non-sensitive key material is transmitted

• XPUBs are stored for address derivation and monitoring purposes

3. User Address Generation

Using the registered XPUBs, the platform:

• Generates unique blockchain addresses for end users

• Associates each address with a specific user reference

• Maintains a deterministic mapping between users and addresses

Address generation is handled centrally, allowing seamless scaling across users and assets.

4. Deposit Monitoring & Detection

4.1 Blockchain Monitoring

The system continuously monitors:

• All generated addresses

• Supported blockchains and tokens

• Incoming transactions and confirmation states

4.2 Deposit Detection

When a deposit is detected:

• The transaction is validated on-chain

• Confirmation thresholds are applied

• The deposit is attributed to the correct user and asset

5. Notification & Delivery Mechanism

Once a deposit is confirmed:

• A notification is sent to the customer’s configured endpoint

• The payload includes transaction and user-related details required for reconciliation

To ensure reliability:

• Notifications are retried every 5 minutes if delivery fails

• Retries continue for up to 24 hours until successful delivery

6. Asset Visibility & Administration

Through the administrative interface, customers can:

• View cumulative balances derived from generated addresses

• Track deposits per user and per asset

• Access historical transaction data for reporting and reconciliation

7. Withdrawal Workflow

7.1 Withdrawal Requests

• Withdrawal requests are created via API

• Requests enter a controlled approval pipeline

7.2 Approval Flow

• Each withdrawal requires approval from two authorized personnel

• All approval actions are logged for audit purposes

7.3 Transaction Execution

After approval:

1. The platform prepares a transaction payload

2. The payload is sent to the customer’s signing service

3. The signed transaction is returned

4. The system broadcasts the transaction to the blockchain

This process is fully automated once approvals are completed.

8. Batch Operations

For operational efficiency:

• Withdrawal requests can be batch-processed

• Batch execution follows the same approval and signing workflow

• Status updates are provided per transaction

9. Reliability & Operational Safeguards

The system includes:

• Automated retry mechanisms

• High-availability job processing

• Full audit logging across critical operations

These safeguards ensure operational continuity even during partial outages.

10. Summary

The system provides:

• Automated wallet and address management

• Scalable user address generation

• Reliable deposit detection and notification

• Controlled, auditable withdrawal execution

• Clear operational visibility via admin tools

API requests require setting up HMAC. POST requests are protected by HMAC, API keys, and an IP whitelist.

You can generate deposit-tracking sessions for your users, and the system will return a checkout URL. The blockchain addresses for your users are automatically generated.

The system detects deposits made to your users' blockchain addresses and sends a notification to your endpoint. Even if your system is down, a high-availability job ensures you receive the notification. The system will retry sending the notification every 5 minutes for 24 hours until it is successfully delivered.

Using our customer administrator pages, you can track the cumulative value of your assets associated with your generated addresses.

You can request a withdrawal from your wallets, and the system requires approval from two authorized personnel (four-eye principal).

You can batch-process your withdrawal requests.