Secure cloud
Managed cloud deployment for a lightweight go-live. Keys remain held in the institution’s own signing service.
Platform
Signing authority, inside your perimeter.
Hardware and software built as one system: keys that never leave your environment, a ledger your finance team can audit, and settlement that speaks the standard your operations already run on.
01Signing
The cryptographic signing server.
Before settlement comes authority. Every movement of value needs a signature, and every signature needs a root of trust that the institution — not a vendor — controls.
Intel TDX trusted execution
Key operations run inside a hardware-isolated enclave, protected from the host operating system.
Optional FIPS-certified HSM
For institutions whose policy requires certified hardware key storage, without changing the workflow.
Threshold signatures
Approval quorum enforced cryptographically: no single operator can move value alone.
Multi-chain key derivation
One root of trust, many networks — new chains do not require new key ceremonies.
On-premises or private cloud
Deploy inside your perimeter. Kept offline, the same server is a cold vault.
No vendor access
There is no backdoor, no remote key export and no operator override. Not even for us.
02Wallet and ledger
The institutional wallet stack.
A wallet is not a place to store tokens. It is the policy, approval and accounting layer between a business process and a signature.
Tiered custody
Hot and cold tiers with explicit limits, so operational speed never becomes unmanaged exposure.
Policy and approval engine
Multi-level approvals, role separation and signing quorums expressed as rules your risk team can read.
Treasury and pooling
Merchant fund pooling, internal transfers and treasury sweeps that reconcile to the ledger rather than beside it.
Four-state sub-ledger
Available, reserved, in transit and confirmed — an accounting model that maps to how banks already book settlement.
Four states, one balance
01
Available
Spendable now, inside policy limits.
02
Reserved
Committed to an instruction awaiting approval.
03
In transit
Broadcast on-chain, awaiting confirmation.
04
Confirmed
Settled, final, reconciled to the message hash.
03Settlement
Messaging unchanged. Settlement replaced.
Institutions do not want a new operating model; they want the one they have, with a better core. Messages stay ISO 20022. What moves behind them changes.
ISO 20022, SWIFT-compatible
Payment instructions and status reports stay in the format your payment engine and correspondents already process.
Peer-to-peer on-chain
Value moves directly between two licensed institutions. On-chain confirmation constitutes settlement finality — in minutes, 24/7.
Message-to-hash binding
Every instruction is bound to its transaction hash, so an audit trail can reconstruct a payment end to end.
Position management
Stablecoin positions are sourced, sold and rebalanced through licensed platforms, not left to accumulate.
Currency-neutral
USDT, USDC, other compliant stablecoins or tokenised deposits — switchable without re-architecting the network.
Habits preserved
Pricing, FX spread and client relationships stay where they are. Only the settlement core moves.
04Architecture
Built as one system, not an assembly.
The signing server, wallet stack and settlement layer share one key hierarchy and one audit chain. That is what separates system integration from component assembly.
04
Your systems
Core banking, payment engine, treasury, ERP and reporting — unchanged interfaces.
03
Settlement
ISO 20022 messaging · on-chain P2P · position management · message-to-hash audit.
02
Wallet and sub-ledger
Policy engine · approval quorum · tiering · four-state accounting.
Private keys never cross this line
01
Cryptographic signing server
Intel TDX or FIPS HSM · threshold signing · multi-chain derivation — deployed inside your environment.
05Deployment
Run it where your regulator wants it.
Hybrid
Signing and core ledger services on your premises; business-side asset management and settlement in the cloud.
Fully private
The entire stack deployed in your own environment — for institutions with strict residency or sovereignty requirements.
06Assurance
What we can show your risk committee.
Key lifecycle
Generation, backup, rotation and destruction with documented ceremony and dual control.
Deployment validation
Multi-site deployment testing across regions, including failure and recovery paths.
Audit by default
Every instruction, approval and signature is logged and bound to its on-chain result.
Independent review
Cryptographic design documented for external review; diligence materials available under NDA.
07Boundaries
What we do — and what we deliberately do not.
Vetrapay provides
- Cryptographic signing infrastructure, deployed under your control
- Wallet, policy and sub-ledger software integrated with your systems
- Settlement messaging, on-chain routing and audit binding
- Integration with licensed conversion and liquidity partners
Vetrapay does not
- Hold client funds, assets or private keys
- Issue stablecoins or operate a stablecoin treasury
- Offer digital-asset trading or custody to end customers
- Serve retail customers, or any client in mainland China
See it running in your environment.
A technical walkthrough takes about an hour. Bring your architect and your risk lead.