WasabiCard has issued a security statement to make clear that it has no connection to Wasabi Protocol, Wasabi Wallet, or any related projects. The announcement appears aimed at reducing confusion that could arise from similar branding and reinforcing the company’s identity as an independent Web3 financial infrastructure provider.
Company stresses independent status
In its statement, WasabiCard said its operations, product structure, and security framework are separate from the Wasabi-branded protocol and wallet ecosystem. In the Web3 sector, name similarity can easily lead to mistaken assumptions by users, so explicit clarification can play an important role in risk communication and trust building.
Security and compliance partners highlighted
To support its security claims, WasabiCard said it works with Safeheron and uses private key sharding technology to protect on-chain funds. Such an approach is generally designed to reduce the risks associated with a single point of private key failure and improve the security of asset management processes.
The company also said it collaborates with security firms including SlowMist for comprehensive audits. On the compliance side, WasabiCard said it uses tools such as SumSub for identity verification, indicating that it has implemented measures related to user verification and compliance controls.
Licensed provider focuses on core capabilities
WasabiCard described itself as a licensed Web3 financial infrastructure provider and said that security and compliance are among its core capabilities. The latest statement serves both as a clarification of its corporate identity and as a signal that the firm wants to provide greater transparency around how it protects users and handles regulatory requirements.
Based on the disclosed information, the company’s message is centered less on product expansion and more on independence, fund security, third-party auditing, and compliance verification. For users following Web3 payments and financial infrastructure, the clarification may help distinguish between similarly named entities and better understand the boundaries of operational and security responsibility.