Add independent oversight to your crypto treasury
Monitor business wallets, identify material risks and receive clear daily alerts and periodic management reports—without transferring custody of your digital assets.
Available to approved business clients. Monitoring is subject to supported assets, networks and service configuration.
Turn blockchain activity into useful business information
Your business keeps control of its wallets and digital assets. Bitkaya monitors and reports; it does not move or take custody of the assets.
What the service provides
- Daily wallet monitoring. Registered wallets are checked for new activity, balance changes and relevant risk indicators.
- Exception alerts. Material or unusual findings are reported so that your organization can investigate and respond promptly.
- Monthly treasury statements. Receive a consolidated record of monitored wallet balances and movements for management oversight and reconciliation.
- Transaction risk screening. Incoming and outgoing transactions are screened using specialist blockchain analytics to identify exposure to relevant risk categories.
- Multi-wallet oversight. Bring several approved business wallets into one reporting structure, including wallets maintained for different entities, purposes or networks.
- Human-readable reporting. Reports explain what happened, why it may matter and what practical follow-up could be considered, while retaining the technical information needed by specialists.
What can be monitored?
Bitkaya focuses on established digital assets commonly used for corporate treasury and settlement:
| Asset | Supported networks |
|---|---|
| Bitcoin | Bitcoin main chain |
| USDT | Tron and Ethereum (main chain) |
| USDC | Ethereum and Solana (main chain) |
Support for an asset or network must be confirmed before monitoring begins. Available coverage may change based on blockchain-data availability, analytics-provider support and operational considerations.
How monitoring works
1. Register the wallets. Your business identifies the wallets that should be included, their purpose, the relevant legal entity and the authorized representative responsible for them.
2. Confirm the wallet context. Bitkaya records essential information such as the asset, network, expected activity and whether the wallet is used for treasury, payments, reserves or another approved business purpose.
Bitkaya may ask the business to demonstrate control of a wallet before it is treated as a verified company wallet.
3. Configure the service. The monitoring scope is agreed based on the selected service arrangement, including the wallets, reporting frequency, recipients and relevant alert parameters.
4. Monitor activity. Bitkaya checks registered wallets for new transactions, balance changes and relevant blockchain-risk indicators.
5. Report material findings. Where a finding meets the applicable reporting criteria, Bitkaya provides an exception alert with a plain-language explanation and supporting transaction details.
6. Provide periodic reporting. The client receives periodic wallet statements or management reports in accordance with the agreed service arrangement.
Daily monitoring that people can understand
A useful monitoring report should not simply reproduce technical blockchain data.
Bitkaya’s daily reporting is designed to answer the questions management and operations teams actually have:
- Did any monitored wallet move?
- Which asset and amount were involved?
- Was the transaction incoming or outgoing?
- What was the value?
- Which wallet and business entity were affected?
- Was any relevant risk indicator identified?
- Does the transaction require attention?
- What practical follow-up should be considered?
Technical details—including wallet addresses, blockchain networks and transaction hashes—remain available for compliance, finance and technology specialists.
Monitoring without custody
Bitkaya does not need to hold the client’s assets to monitor its wallets.
The service uses wallet addresses and available blockchain data to observe and report activity.
Bitkaya:
- Does not receive the client’s private keys
- Cannot initiate or approve transactions
- Does not take possession of monitored assets
- Does not change the client’s wallet configuration
- Does not block or reverse blockchain transactions
- Does not replace the client’s internal approval controls
The client remains responsible for wallet security, transaction authorization and decisions made in response to monitoring findings.
Indicative Pricing
Final pricing is determined in quotation based on specific client circumstances
Light
Fit for small low-activity treasury wallets.
- 3 wallets
- 75 transactions /month included
- annual payment only
- No upgrades
Standard
fit for most regular businesses
- 5 wallets
- 500 transactions/ month included
- Extra wallet $150 /month
- Extra transaction $0.75 /tx
- Monthly or yearly plan
Heavy
fit for high-volume treasury flows
- 20 Wallets
- 4000 transactions /month included
- Extra wallet $100 per month
- Extra transaction $0.50 /tx
- Extra perks
- Monthly or yearly plan
Frequently Asked Questions
About the Service
Crypto Treasury Monitoring is a non-custodial service that observes registered business wallets and reports balances, transactions and relevant risk indicators. It gives the client additional oversight without transferring control of the assets to Bitkaya.
With custody, Bitkaya controls the custody wallet and processes transactions based on authorized client instructions.
It combines elements of both. Bitkaya monitors wallet activity for relevant blockchain-risk indicators and organizes the resulting information into daily alerts and periodic treasury reports.
No. Bitkaya provides monitoring and reporting. The client remains responsible for treasury strategy, wallet administration, transaction approvals and decisions made in response to findings.
No. Subject to onboarding and technical support, Bitkaya can monitor eligible external wallets controlled by the client or maintained with another provider.
Wallets, assets and networks
You can reach our customer support team by emailing info@yourcompany.example.com, calling +1 555-555-5556, or using the live chat on our website. Our dedicated team is available 24/7 to assist with any inquiries or issues.
We’re committed to providing prompt and effective solutions to ensure your satisfaction.
Bitkaya’s intended coverage includes Bitcoin, USDT and USDC across selected supported networks. The exact coverage is confirmed during service setup.
Yes. The number of wallets included depends on the selected service arrangement. Additional wallets can be added subject to identification, configuration and any applicable charges.
Potentially, but the legal ownership and purpose of each wallet must be clearly recorded. Separate reports or service arrangements may be appropriate where different legal entities are involved.
No. Monitoring is primarily based on identifiable on-chain wallet addresses. Assets held within a pooled exchange account may not be attributable to the client through public blockchain data.
Not automatically. Support depends on reliable blockchain data, analytics coverage and Bitkaya’s operational configuration. New networks must be assessed before they can be added and require a custom monitoring plan.
Wallet registration and verification
Bitkaya currently focuses on Bitcoin, USDT and USDC across selected blockchain networks. Availability depends on the asset, network, transaction size, liquidity and compliance review.
- The wallet address
- The asset and blockchain network
- The legal entity associated with the wallet
- The expected type of activity and purpose
- The authorized representative
- Whether the wallet is self-managed or held with another provider
Additional information may be requested where needed.
No. However, if the client operates a regulated business, Bitkaya may require proof of control before identifying a wallet as a verified business wallet.
Depending on the blockchain and wallet setup, verification may involve a message signature, a small verification transaction, an existing known transaction, custody documentation or other reliable evidence.
Not necessarily. Verification demonstrates control of, or an established relationship with, the wallet at a particular point in time. It does not independently establish the legal or beneficial ownership or source of every asset in the wallet.
The new wallet must be registered and, where required, verified. The previous wallet should remain in the reporting scope for an appropriate period if historical continuity is needed.
Daily monitoring and alerts
Wallets are checked on a daily basis rather than continuously in real time.
No. A daily monitoring service may identify activity after the blockchain transaction has already taken place.
Alerts are based on configured monitoring criteria, which may include material risk indicators, unexpected activity, significant balance changes, unknown counterparties or technical monitoring issues.
Yes, but depending on your chosen monitoring setting. Routine activity may be included in the daily or periodic report without generating a separate exception alert. The service is intended to highlight matters that may require attention.
Alerts are sent out daily, covering changes from the previous report. Report receipients can chose to get notified of all new transactions, or only those that have a high/severe risk assessment.
- The affected wallet
- Asset and network
- Transaction direction
- Amount
- Transaction date and time
- Transaction hash
- Relevant risk indicator
- Available technical details
Risk screening
Depending on available blockchain analytics, indicators may include exposure associated with sanctions, fraud, scams, stolen assets, ransomware, mixing services, darknet activity, terrorist financing or other higher-risk services and entities.
No. An alert indicates a potential risk connection or pattern that requires contextual assessment. It does not by itself establish that the client or counterparty has committed an offence.
Indirect exposure means that assets have passed through one or more intermediate wallets associated with a risk category. The significance depends on factors such as transaction distance, amount, percentage exposure, timing and available context.
Yes. Wallet attribution and risk classifications can change as analytics providers obtain new information. A transaction may therefore be assessed differently at a later date.
No. Blockchain analytics cannot identify every person, wallet or source of risk. The absence of an alert is not a guarantee that a transaction or counterparty is legitimate.
Bitkaya may use selected third-party blockchain analytics providers to support the monitoring service. The provider may change where necessary for coverage, quality, operational separation or service continuity.
Reports and statements
- Daily monitoring summaries
- Exception alerts
- Monthly wallet statements
- Supporting transaction details
The exact deliverables and frequency are agreed with the client.
A monthly statement may show registered wallets, assets, networks, opening and closing balances, transactions during the period and relevant risk scores.
Yes. Reports can consolidate multiple registered wallets where this is included in the service configuration.
No. We're only reporting the movements in the crypto asset itself.
They can support reconciliation and recordkeeping but do not replace the client’s accounting system, valuation policy or professional accounting judgment.
The client may use the reports as supporting information, subject to the service terms and applicable confidentiality requirements. The recipient should understand the report’s scope and limitations.
No, unless expressly stated otherwise. Standard monitoring reports are operational reports and do not constitute an audit, assurance opinion, certification or independent valuation.
Yes as a decision support tool. Bitkaya does not provide compliance advice nor replaces the client's MLRO, compliance department or regulatory responsibility.
Client responsibilities and follow-up
The client should assess the finding in the context of its own records and relationship with the counterparty. Appropriate action may include requesting supporting documents, pausing further activity, escalating internally or obtaining compliance or legal advice.
No. For a non-custodial wallet, Bitkaya cannot block the transaction and does not make the client’s business decision. Bitkaya simply reports the finding. The client is responsible for follow-up action, if any.
No. The service can support the client’s controls, but it does not replace customer due diligence, sanctions compliance, transaction monitoring, internal escalation or regulatory reporting obligations.
No. The client remains responsible for determining whether a matter must be reported to a regulator, financial intelligence unit or other authority.
Security and privacy
No. Bitkaya only needs the public wallet address and relevant contextual information. Clients should never send private keys, seed phrases or wallet recovery credentials to Bitkaya.
No. Public wallet addresses allow activity to be observed but do not provide transaction authority.
Public blockchain transactions are publicly accessible. However, linking a wallet to a particular company, purpose or representative creates additional business information that Bitkaya handles in accordance with its contractual and privacy arrangements.
Reports are sent to the recipients authorized by the client. The client should keep its recipient list current and promptly notify Bitkaya of changes.
Service limitations
No. The service identifies and reports activity; it cannot stop or reverse transactions from a non-custodial wallet.
Historical analysis may be available as a separate service. Its scope depends on the blockchain, available data and agreed review period.
Bitkaya will handle material service interruptions in accordance with the applicable service terms. Monitoring may be affected by blockchain outages, analytics-provider availability, technical failures or incomplete data.