Payment and Wallet Security

Torque keeps payment records, wallet records, custody actions, and final confirmation as separate controls.

Custody, signing, and confirmation

The Wallet model records a profile's fiat ledger. The Crypto Wallet model records a profile's blockchain address. These records and their provider or chain operations remain distinct even when one Investor experience presents them together.

Fund-owner signing and Investor claims are separate custody actions. The holding workflow separates acceptance, owner signing, fulfillment, and the Investor claim. The redemption workflow separates pricing, owner fulfillment, the Investor claim, and a later wallet withdrawal. A claimable record does not prove a confirmed holding or receipt of proceeds.

A page transition or provider status does not prove completion. The service that owns the action must record its authoritative result. Interfaces and Integrations defines provider and service boundaries.

Configurable two-factor authentication for wallet actions

Torque supports configurable rules that require two-factor authentication (2FA) before selected wallet actions. Examples include withdrawals, on-chain signing, wallet security changes, or another protected wallet action. The exact rules depend on deployment policy and provider capabilities.

The 2FA check occurs before the protected action. It does not replace custody authorization, signing review, or provider and chain confirmation.

Practical checks

• Read the exact amount, destination, and signing context before approving an action.
• Follow the recovery action shown by the applicable flow when a payment or wallet action is incomplete.

The Application Security Framework defines technical requirements for role controls, transaction review, account recovery, and incident response.