Guides
Start typing to search…

Account Wallets

The Account Wallet is the root wallet provisioned for each business using 3PAY. It anchors all wallet operations, holds configuration and policies, and serves as the primary treasury point for inflows and outflows

Role in Each Operating Model

  • Custodial model: All client deposits settle into the Account Wallet. End-user balances are managed on the business’s internal ledger.
  • Non-custodial model: The Account Wallet exists for treasury, fee capture, and operational transfers, while end users hold funds in their own User Wallets. (Coming Soon)

Addresses and Funding

  • Persistent deposit address: Each Account Wallet has a stable, reusable deposit address per supported rail (e.g., USDT-TRC20).
  • Multiple rails: One Account Wallet can expose multiple deposit addresses—one per enabled asset/network.
  • Inbound detection: Deposits are observed on-chain and reflected in the wallet balance after confirmation.

Outflows and Governance

  • Payouts/Transfers: Outbound movements (to custody, liquidity, PSPs/banks, or external wallets) originate from the Account Wallet.
  • Policies: Role-based approvals and threshold rules (e.g., 2-of-N quorum for amounts above a limit) can be applied to sensitive actions.
  • Non-custodial guardrails: When operating alongside User Wallets, policies can mandate segregation (no sweeping) unless explicitly approved.

Reconciliation & Reporting

  • On-chain source of truth: Balances and movements are verifiable on the blockchain.
  • Operational ledger: In custodial setups, internal sub-ledgers must map precisely to the Account Wallet’s on-chain balance.
  • Artifacts: Store transactionId, rail (currencyType), timestamps, and references to approval records for audit.

Typical Flows

Custodial

Client Deposit → Account Wallet → Internal Ledger Credit → (Payout / Treasury / PSP/Bank)

Non-custodial (treasury)

User Wallet → (Optional) Treasury Transfer → Account Wallet → Custody / Liquidity / PSP/Bank

Compliance Considerations

  • Segregation clarity: Document whether balances represent the business’s funds (custodial) or operational float (non-custodial).
  • Sanctions/AML screening: Apply screening to inbound and outbound movements according to your program.
  • Refunds-to-origin policy: If refunds are supported, return funds to the source address to preserve auditability.

Operational Best Practices

  • Labeling & purpose: Tag Account Wallets by function (e.g., treasury, ops-liquidity, receivables).
  • Rail selection: Prefer lower-cost rails for routine treasury moves; reserve high-assurance rails where required.
  • Address hygiene: Expose deposit addresses only for rails you actively reconcile.
  • Approval hygiene: Require multi-party approvals for large payouts and external transfers.
  • Monitoring: Alert on balance thresholds, unusual velocity, or policy bypass attempts.

When to Use Account Wallets

  • Custodial businesses centralizing client deposits and operating an internal ledger.
  • Non-custodial platforms maintaining operational float, fee capture, or settlement buffers separate from User Wallets.
  • Enterprises/PSPs orchestrating payouts to custody, liquidity wallets, PSPs, or banking corridors.

Next Steps

  • Review User Wallets to understand per-user segregation in non-custodial mode.
  • See Custodial vs Non-custodial for model selection guidance.
  • Configure Policies & Governance to enforce approvals and thresholds on outflows.

Updated about 1 month ago