Customer-controlled authorisation
Cardinal does not request seed phrases or private keys. The customer or its authorised wallet provider remains responsible for transaction approval.
This page explains how Cardinal approaches transaction authorisation, evidence, operational policy and protected settlement—and identifies which capabilities are live, controlled pilot or testnet.
Cardinal does not request seed phrases or private keys. The customer or its authorised wallet provider remains responsible for transaction approval.
ALLOW, REVIEW and BLOCK outcomes are accompanied by the relevant evidence and matched business rule available to the workflow.
The product is designed to record where evidence came from, when it was observed and whether it was live, cached or demonstrative.
Where a policy requires evidence that is unavailable, the intended safe outcome is REVIEW rather than an unsupported approval.
Higher-risk transactions can be routed into SafeSend review timing or conditional Escrow workflows on supported environments.
Payment details, evidence, policy reasoning, authorised action and settlement status can be retained as one decision record.
Cardinal separates live information, controlled demonstrations and testnet settlement so customers and investors can evaluate the product accurately.
Network coverage, evidence providers, business policy, transaction limits and operational ownership are agreed for each design partner.
Request an enterprise review