MPC-POWERED DIGITAL ASSET INFRASTRUCTURE
Arkwalletx ships as a working treasury application — accounts, approvals, risk controls, team roles — and as a WaaS API you can embed. Both run on the same MPC threshold-signing core.
Start with the product. Move to the API when you need to — your keys, policies and history carry over.
Log in and start today
Cross-border commerce · Payment providers · Crypto-native teams
Embed it in your own product
Trading platforms · Funds · Licensed institutions
One view across every account, currency, and chain — updated as transactions settle.
Separate accounts per business line, currency, or counterparty. Balances roll up; permissions don't.
Total position and per-asset holdings, priced and refreshed continuously.
Every inbound and outbound transfer, with on-chain reference and internal approver.
Flows, holdings, and movement over time — exportable for reconciliation.
Every transfer passes through rules you define — before it ever reaches a signer.
Not on our servers, not on your device, not at any moment in the signing process. That's not a policy — it's how threshold cryptography works.
Signing requires m of n independent key shares to cooperate. No single share, and no single machine, can produce a valid signature.
Share computation runs inside a trusted execution environment. Memory is sealed — inaccessible even to the host operating system.
Shares are stored across isolated environments with independent backup and recovery paths. Losing one is recoverable; compromising one is not enough.
What this means in practice: even Arkwalletx cannot move your assets outside the policies you set.
Collect from customers and pay suppliers in stablecoins, without a banking relationship in every market.
Accept crypto on behalf of merchants, settle on schedule, keep funds segregated per merchant.
Hot, warm, and cold separation with programmatic signing and per-desk limits.
Hold and move stablecoin reserves under board-approved policy, with an audit trail that survives review.
30+
chains
500+
tokens
Mainstream networks and the stablecoins your counterparties actually use — USDT, USDC, and more, across every chain we support.
Companies that receive, hold, or send digital assets as part of normal operations — cross-border merchants, payment service providers, trading platforms, funds, and corporate treasuries. If your finance team currently handles crypto through personal wallets or exchange accounts, Arkwalletx is the replacement.
The Platform requires no integration — you can be operating the same day your account is provisioned. For WaaS, the path is: request API credentials → build against the sandbox → go live. Timeline depends on your scope; our engineering team scopes it with you before you commit.
Pricing depends on custody volume, transaction throughput, and which capabilities you use. Contact our sales team for a quote based on your business.
30+ mainstream chains and 500+ tokens, including USDT and USDC across all supported networks. Contact us for the current full list.
Yes. Create a separate treasury account per business line, currency, or counterparty. Each carries its own balances, permissions, approval rules, and transaction history. They roll up for reporting but stay isolated operationally.
Members are assigned roles scoped to specific treasury accounts. Roles determine who can initiate transfers, who must approve them, and at what thresholds. Every action is logged with actor and timestamp, and access can be revoked with immediate effect.
No one holds a complete private key, including us. Signing uses threshold MPC: the key exists only as n independent shares, and producing a signature requires m of them to cooperate. Share computation happens inside trusted execution environments, where memory is sealed even from the host operating system. The full key is never reconstructed — not at any step, not on any machine.
No. Every transfer must satisfy the policies you configure — approval thresholds, allowlists, velocity limits — before it ever reaches a signer, and signing itself requires a threshold of independent key shares. We cannot move your assets outside the policies you set.
Shares are stored across isolated environments, each with an independent backup and recovery path. Losing one share is recoverable. Compromising one share is not enough to produce a signature, because signing requires m of n shares to cooperate.
No. Arkwalletx is custodial only. There is no self-custody mode and no co-managed mode in which you hold part of the key material. The protection against misuse comes from threshold cryptography and the policy engine described above, not from splitting custody with you.
A trusted execution environment is an isolated region of a processor whose memory cannot be read by the host operating system or by anyone with access to the machine. Key-share computation runs inside one, so a share is never exposed in plain memory even to infrastructure operators.
In order: policy validation against limits and allowlists, AML/KYT screening of the counterparty address, then multi-level approval according to your rules. Each of those stages can block the transfer. Only after all three pass does MPC signing begin — and once signing starts, the transfer cannot be recalled.
Authority is split by role and scoped by wallet. The member who initiates a transfer is not the member who approves it, and neither necessarily holds signing authority. Approval thresholds by amount and destination mean a single compromised account cannot move material funds. Every action is logged with actor, timestamp and outcome.
Amount, asset, and destination address. Rules can require multiple levels of approval above given thresholds, and can be scoped to specific treasury accounts rather than applied blanket across the organisation.
Yes. Creating, editing or deleting a risk policy goes through the same approval queue as a transfer, as does inviting a team member. Someone cannot quietly weaken the controls and then move funds through the gap.
Remove the member and their access ends immediately — there is no propagation delay or session that keeps working. Their historical actions remain in the audit log.
Yes. Members, roles and scopes are assigned per treasury account. A member can hold different roles on different accounts, and business lines are isolated from each other by default.
Yes. WaaS integration is built and tested against a sandbox environment before going live. The sequence is: request API credentials, build against the sandbox, then go live.
No. Your keys, policies and transaction history carry over. The Platform and the WaaS API are two interfaces onto the same custody core and the same risk engine, not two separate products.
Yes. Flows, holdings and movement over time can be exported from the reporting dashboard, and every transfer carries both its on-chain reference and the internal approver, so an entry can be traced end to end.
A 30-minute call is usually enough to tell whether Arkwalletx fits how your business moves money.
