Skip to content

Wallet and transfers ​

Outcome: An eligible Investor receives a wallet and obtains a recorded result for a verified bank link, deposit, or withdrawal.

Owner and application ​

  • Actors: Investor, identity and compliance services, wallet and payment services, and Administrator for cross-platform exceptions
  • Applications: One Torque Investor experience and administration workspace for exceptions
  • Conditions: The profile is owned, the applicable identity and eligibility result is available, and the provider path is configured.

Normal path ​

  1. The identity and compliance services return the required KYC or profile result for the Investor.
  2. The wallet service provisions the applicable Wallet or custodial sub-account, records its Wallet ID, and links it to the owned profile.
  3. The Investor links a permitted bank account through the provider flow. The provider returns a verified account reference or processor token, and the wallet service creates the FundingSource record.
  4. For a deposit or withdrawal, the Investor selects the verified source or destination and submits the amount in the wallet experience. For a permitted digital-asset transfer, the Investor selects the linked Crypto Wallet and authorizes the chain operation.
  5. The wallet service creates the Transaction record, records its pending state, and sends the instruction to the payment provider. The selected rail controls settlement timing.
  6. The provider or chain returns a status. The owning wallet service reconciles the operation, updates the Transaction and wallet balances, and records the provider or chain reference.
  7. The notification service shows the result and next action to the Investor. The audit record preserves the handoff and completion evidence.

Failure and recovery ​

  • A pending or rejected identity result prevents wallet provisioning and returns the Investor to the applicable onboarding or evidence action.
  • A wallet-provider failure leaves the profile, provider response, and provisioning attempt identifiable for the wallet owner.
  • A rejected or ambiguous bank-link result does not create a verified FundingSource. The Investor can resume the provider flow or use the approved recovery path.
  • A pending deposit or withdrawal remains pending until the payment provider confirms, rejects, or returns it. The wallet service owns reconciliation rather than treating a client response as settlement.
  • A withdrawal red flag, source mismatch, or account change creates a review or hold for the responsible compliance or payment owner.
  • An ambiguous transfer response loads the existing Transaction and provider operation before a retry or new instruction.
  • Administrator receives a cross-fund or cross-issuer exception. The wallet or payment service closes recovery only after it records the final provider result and audit evidence.

Handoff and evidence ​

HandoffReceiving ownerCompletion evidence
Identity result to wallet provisioningWallet serviceProfile, KYC result, provider response, and Wallet ID
Bank-link request to FundingSourceBank-link and wallet servicesProvider verification, token or reference, and source status
Deposit or withdrawal to payment railPayment serviceTransaction, source or destination, amount, and provider operation
Provider status to wallet reconciliationWallet serviceProvider or chain result, balance update, and reconciliation record
Result to Investor experienceNotification and Investor servicesFinal status, next action, and notification
Failure or cross-scope exception to recoveryOwning service and AdministratorError context, assigned owner, audit entry, and recovery result

See Digital Wallet & Custodial Account Creation, Funds Transfer, Electronic Payment, Depositing Funds, Linking a Bank Account, and Withdrawing Funds pages.