Wallets. Payments. Treasury.

Secure crypto
operations.
One platform.

Receive deposits, manage treasury and send payments—with the security controls your business needs and the integrations your team expects.

  • Wallets across Bitcoin, Ethereum, TRON & XRP
  • Signing options, approvals & access controls
  • REST API, webhooks, Slack & Telegram
Visibility across your operationActual product · Demo data
Aegis dashboard with total balance, deposit and withdrawal volume charts, balances by chain and recent transactions. Demo data.
Balances, activity and payment volume in one view.See more screens ↓
Security at every stepFrom account access to transaction signing
Connected operationsWallets, payments and treasury in one place
Built to integrateYour product, your team, your workflow
Across your key networks

Manage assets together.
Keep each network in view.

BitcoinBTC wallets & transfers
EthereumETH & ERC-20 assets
TRONTRX & TRC-20 assets
XRP LedgerXRP wallets & transfers

Asset and signing availability depend on your configuration.

Additional networks on request

Bring us the networks and assets your business needs. We’ll agree integration scope and timing with your team.

Discuss your network
  • Solana
  • BNB Chain
  • Polygon
  • Base
  • Arbitrum
  • Avalanche
The Aegis platform

Everything behind a crypto payment.
Connected in one workspace.

From the first deposit address to the month-end statement, give finance and engineering a shared operational picture.

Wallets & vault accounts

Give each customer, merchant or business unit its own receiving accounts. Organize addresses and assets in a structure your team understands.

Multi-chain walletsDeposit addresses

Deposits you can follow

Track incoming funds from detection through network confirmation. Know what has arrived, what is pending and what is available.

Confirmation trackingEvent notifications

Payouts with visibility

Prepare single or multi-recipient payments, review fees and follow each withdrawal through approval, signing and confirmation.

Batch recipientsTransaction status

Recurring payment plans

Save recipients and schedule one-time, daily, weekly or monthly payouts. Scheduled payments enter your signing workflow for review.

Reusable plansFlexible schedules

One counterparty directory

Keep receiving accounts and payout destinations alongside the people and businesses behind them. See received and paid flows per asset.

Saved destinationsPayment attribution

A clear treasury position

See balances, asset allocation and upcoming outflows together. Export transaction records and monthly statements for reconciliation.

Treasury overviewCSV statements
Team permissions and payment review built into the workflow.Records ready for your finance team.See it with your use case
Inside Aegis

See how the work comes together.

Actual Aegis screens in English with demo data. Take a closer look at the tools your operations team will use every day.

01 / Treasury visibility

Your position.
Your next move.

See where your assets sit and what is scheduled to leave. Give finance a shared view of balances, allocation and upcoming payouts.

  • Allocation by asset and network
  • Scheduled outflows in context
  • Counterparty flows and monthly statements
Talk through your treasury workflow
Aegis treasury showing total position, allocation by chain and asset, counterparty flow filters and scheduled outflows. Demo data.
Treasury · Demo data · English interfaceView full size: Treasury (new tab)
02 / Repeatable payouts

Set the schedule.
Keep the control.

Save recipients and payment schedules for suppliers, contractors and recurring settlements. Each run prepares a pending withdrawal that still goes through signing.

Aegis payment plans for infrastructure, team payouts and treasury allocation with recipients and next run dates. Demo data.
Payment plans · Demo data · English interfaceView full size: Payment plans (new tab)
03 / Connected relationships

Know who is
behind each payment.

Bring customers, vendors and your team into one directory. Link deposit accounts and saved payout addresses, then follow received, paid and net transaction flows.

Aegis counterparty directory showing customers, vendors and employees, their relationships and saved payout address counts. Demo data.
Counterparties · Demo data · English interfaceView full size: Counterparties (new tab)
Security & control

Protect your assets.
Control how they move.

Security belongs in the daily workflow: who has access, what they can do and how a payment gets signed.

Distributed key protection

MPC signing distributes key material across separate participants. The signing policy is defined by your custody configuration.

Access that fits each role

Separate owner, finance and support permissions. Add two-factor authentication and IP restrictions for portal and API access.

Review before funds move

Keep payment preparation, approval and signing visible. Review the asset, amount and recipient before authorizing a transfer.

Hardware signing options

Use the desktop signing station with Ledger or Trezor for supported assets and signing setups.

Recovery you prepare for

Device-secured wallets use customer-held recovery material and recovery drills. Build a recovery plan before you need one.

Protected integrations

Authenticate API requests with HMAC signatures, restrict access by IP and verify the signatures on incoming webhook events.

Encrypted key storage

Managed-key setups support encrypted storage backed by a key-management service, adding protection for sensitive key material at rest.

A record of who did what

Audit records capture authenticated API activity and payment signing events, helping your team trace actions and investigate issues.

Integrations & developer tools

Fits your product.
Connects to your team.

Build wallet operations into your own platform, and bring the updates your team needs to the tools they already use.

REST API

Build into your product

Create vault accounts and deposit addresses. Work with balances, withdrawals and transaction history through authenticated endpoints.

Signed webhooks

Keep systems in sync

Receive deposit and withdrawal lifecycle events. Verify signatures and use delivery retries to support your event-driven workflows.

Slack

Bring operations to your team

Connect your workspace for transaction notifications and wallet queries, with role and channel visibility controls.

Telegram

Stay close to your activity

Link team accounts and chats for deposit alerts, withdrawal updates, balances and transaction queries.

Ledger & Trezor

Connect your signing hardware

Use compatible hardware wallets through the Aegis signing station. Network support depends on the device and signing setup.

CSV & statements

Fit your finance workflow

Export deposits, withdrawals and monthly treasury statements for reconciliation and downstream reporting.

For engineering teams

Your interface.
Aegis underneath.

Connect an exchange, payment gateway, fintech app or internal treasury tool through the API. Use webhooks to connect transaction events to your own business logic.

  • Vault accounts and address generation
  • Balance and transaction queries
  • Authenticated requests and signed events
Talk through your integration
Generate a deposit addressExample request
POST/api/v1/addresses/generate
{
  "walletId": "YOUR_WALLET_ID"
}
Follow the deposit lifecycledeposit.pending
→ deposit.confirming
→ deposit.confirmed

HMAC authentication required. Your integration supplies the wallet ID and request signature.

Built around your business

Real workflows.
From collections to the month-end close.

Run crypto operations in the workspace, or connect Aegis to your own product. Start with the job your team needs to get done.

Merchants & collection businesses

Know who paid. Follow every deposit.

When customer payments arrive across wallets and networks, your team needs a clear way to attribute and track them.

  • Assign receiving accounts to customers or merchants.
  • Follow deposits from detection through confirmation.
  • Send signed events to your system and alerts to team chat.
What your team gets

A clear connection between the counterparty, the incoming payment and its status.

Receiving accounts · Deposit tracking · Webhooks
Finance & accounts payable

Make supplier payments repeatable.

Recurring supplier and partner payouts should not start with rebuilding a recipient list every time.

  • Keep counterparties and payout destinations in one directory.
  • Create one-time, weekly or monthly payment plans.
  • Review prepared withdrawals through the normal signing flow.
What your team gets

Reuse payment instructions while keeping authorization in the workflow.

Counterparties · Payment plans · Approvals
Distributed teams & service businesses

Coordinate contractor payouts.

Paying multiple people means keeping recipient details, amounts, assets and payment status organized.

  • Save each contractor’s payout destination.
  • Prepare multi-recipient payments and review fees before signing.
  • Track confirmations and export the payment records.
What your team gets

One operational process for a payment run, from recipient selection to finance records.

Multi-recipient payments · Fee review · Exports
Exchanges & digital asset platforms

Connect wallets to your own product.

Your customers use your interface. Your team still needs the wallet infrastructure and operational visibility behind it.

  • Create vault accounts and deposit addresses through the API.
  • Connect confirmed deposit events to your customer ledger.
  • Integrate withdrawal requests and follow transaction status.
What your team gets

Keep your customer experience while giving operations a shared wallet workspace.

Vault API · Deposit events · Withdrawal tracking
Payment gateways & fintech builders

Build crypto payment workflows.

A customer-facing payment flow needs a connection between your application logic and the team handling funds.

  • Use deposit addresses in your own payment experience.
  • Connect lifecycle events to order or account updates.
  • Prepare merchant or partner payouts through the withdrawal flow.
What your team gets

Connect collections, business events and outgoing payments through API and webhooks.

REST API · Signed webhooks · Payouts
Treasury teams & crypto-native businesses

See your position before the next outflow.

Balances spread across assets and networks make it harder to plan payments and explain where funds moved.

  • Review asset balances, network allocation and upcoming outflows.
  • Keep operating funds organized in distinct vault accounts.
  • Reconcile activity with exports and monthly treasury statements.
What your team gets

A shared view for the people planning payments and the people closing the books.

Treasury overview · Vaults · Monthly statements
One connected operation

Follow the money through the work.

Walk through your use case
  1. 01

    Receive

    Generate an address, identify the counterparty and follow the deposit to confirmation.

  2. 02

    Review

    Prepare the payment. Check the asset, recipient, amount and fees with the right team access.

  3. 03

    Pay

    Authorize through your configured signing flow and follow the outgoing transaction.

  4. 04

    Reconcile

    Connect payment activity to counterparties and export records for your finance workflow.

Your business rules stay in your application. Aegis provides the wallet, payment and operational controls you connect to them.

Questions before you start

The details
that matter.

Security, integrations and everyday operations.

Talk to the team
How does Aegis help protect our assets?

Aegis combines configurable signing models with team permissions, two-factor authentication, IP restrictions and authenticated integrations. Customer-device signing for newly generated device-secured keys requires your device to participate. Hardware-wallet signing is also available for supported setups. We work through the right configuration for your operation during onboarding.

Can Aegis move funds without our approval?

Signing authority depends on the key and custody configuration. Newly generated device-secured keys require your device to participate; Aegis alone cannot sign. Managed signing and existing or migrated keys have different guarantees. Customer-device signing is in preview, and the exact setup is agreed during onboarding.

Which networks and assets can we use?

Aegis implements Bitcoin, Ethereum, TRON and XRP Ledger integrations, including supported ERC-20 and TRC-20 assets. Additional networks—including Solana, BNB Chain, Polygon, Base, Arbitrum and Avalanche—can be discussed as part of a custom integration. They are not available in the standard offering today; we agree scope and timing with you. Asset and signing availability for existing integrations depends on your configuration and is confirmed before onboarding.

What can we connect to Aegis?

Use the REST API and signed webhooks to connect your own exchange, fintech app, payment gateway or treasury tool. Slack and Telegram integrations bring notifications and wallet queries to team chat. CSV exports and monthly statements support your finance workflows. Ledger and Trezor connect through the signing station for supported setups.

Do scheduled payments bypass approval?

No. A schedule prepares a pending withdrawal for the normal signing workflow. Payment plans let you reuse recipients and timing while keeping the required authorization in place.

How does recovery work?

Recovery for device-secured wallets depends on keeping the required recovery material. Setup and recovery drills help you prepare. Losing every enrolled device and the necessary recovery material can make funds unrecoverable, including by Aegis.

How do we get started?

Contact sales with the networks you use, your payment workflows and your security requirements. We can walk through the platform, discuss integration and signing options, and agree the commercial scope and onboarding plan.

Let’s talk about your operation

Bring your crypto business
onto a stronger foundation.

Tell us what you need to receive, manage and pay.
We’ll walk through the platform and the setup that fits.

Product walkthroughSecurity requirementsIntegration planning