Is HyperPay Safe? Security You Can Verify

What "audited" means, specifically

Security audits are frequently invoked and rarely explained. An audit is a time-boxed review by an external firm of a defined scope of code or infrastructure, producing findings that the vendor then fixes or accepts. It is evidence that qualified outsiders looked, not a guarantee that nothing was missed.

HyperPay's core app has been reviewed by two independent firms, SlowMist and CertiK, both of which are well known in the blockchain security industry. Sealer2100, the flagship hardware wallet, has been audited by CertiK and Kudelski Labs. We name the firms because a named auditor is checkable and the phrase "independently audited" on its own is not.

The honest framing is that audits reduce the probability of certain classes of defect. They do not make a wallet unbreakable, and any vendor implying otherwise is overselling what the process does.

Open source: exactly what is and isn't

The HyperPay wallet application is not open source. Its source code is not published for independent review, which means external verification of the app relies on third-party audits rather than on anyone being able to read the code themselves. That is a real limitation and we state it rather than working around it.

Sealer2100 is different. Its full codebase is published under the Apache 2.0 licence on public GitHub, and it has been independently audited by CertiK and Kudelski Labs. If verifiable software is a requirement for you, that is where HyperPay meets it: keys live on a device whose firmware you can read, audit and rebuild, with the wallet app acting only as an interface.

How custody risk differs by mode

In self-custody mode, private keys are generated and stored locally on your device. HyperPay cannot move, freeze or recover those funds — and neither can anyone else, including you, if the recovery phrase is lost. The dominant risk is your own backup discipline, not the provider.

In custodial mode, key management moves to HyperPay's infrastructure, with assets held through HyperBC. That removes seed-phrase loss as a failure mode and adds provider dependence. Neither model is universally safer; the wallet supports both.

Where HyperPay is published

HyperPay is published by CipherBC Hyperpay Pte. Ltd., a Singapore-registered company operating the wallet since 2017. Desktop build 5.6.210401 is distributed from hyperpay.dev, and mobile listings carry the same publisher name.

• Publisher: CipherBC Hyperpay Pte. Ltd., Singapore, operating HyperPay since 2017.
• Current desktop build: 5.6.210401 for Windows, macOS and Linux.
• HyperPay support never asks for a recovery phrase.

Practical steps for your own setup

For balances where device compromise is a genuine concern, add hardware. HyperMate signs offline over Bluetooth, and Sealer2100 signs air-gapped via QR codes with iris-based access. Keep firmware current and split holdings.

1. 1

   Back up your recovery phrase offline.

   On paper or metal, in at least two separate physical locations.

2. 2

   Keep it out of digital storage.

   Never store it in a photo library, notes app or cloud drive.

3. 3

   Test the restore first.

   Do this before you fund the wallet with a meaningful amount.

Where this fits

Security is one input into the wider picture; the HyperPay wallet overview explains how custody, the HyperCard and staking fit together once you have decided the security model works for you. For background on the custody model itself, read our guide to whether crypto wallets can be traced, and the HyperPay company background page names the team behind these commitments.