Wayfare

Vault

Custody built for the controls your licence requires

Wayfare Vault holds client and house assets across the chains you operate on, behind the approval chains and policies your compliance function already expects. Controls are enforced by the vault, not by convention.

See pricing →

How it works

Nothing moves without the approvals you configured

  1. 01

    Hold

    Assets sit in vaults across Tron, Ethereum, Base, Polygon and Solana, segregated per client and tiered across hot, warm and cold storage.

  2. 02

    Approve

    Every movement passes maker-checker approval: one person proposes, another authorises. No single credential can move funds on its own.

  3. 03

    Enforce

    The policy engine applies your spend limits and address whitelist to every request, and automated sweeps move balances between tiers on the rules you set.

WHO SIGNS OFF ON CUSTODY

TREASURY MANAGERS

Every movement, under a rule you wrote

  • Maker-checker on every outgoing transfer
  • Spend policies by asset, chain, amount and destination
  • Hot, warm and cold tiers with automated sweeps

COMPLIANCE MANAGERS

Every decision, on the record

  • Immutable audit log of every approval and change
  • Client assets and own assets classified and versioned
  • Destinations screened before they can receive funds

FOUNDERS

Controls a licence application can point to

  • No single person can move funds
  • No Wayfare staff role can move your funds
  • Built for the regimes in Ghana, Nigeria and Kenya

Everything in the Vault

WALLETS AND CHAINS

Multi-chain custody organised the way your book is.

  • Supported chains. Tron, Ethereum, Base, Polygon and Solana.
  • Supported assets. USDT on Tron; USDT and USDC on Ethereum, Base and Polygon; USDC on Solana; and each chain's native asset for network fees.
  • Tiered storage. Hot, warm and cold wallets, each with its own policies and approval requirements.
  • Client and own assets. Every wallet is classified as holding client assets or your own. Classification is versioned, so you can see what any wallet was on any past date.
  • Deposit addresses. Generate addresses per client with an internal reference, so incoming funds are attributed on arrival.
  • Automated sweeps. Move balances above a threshold from deposit and hot wallets to warm or cold storage on a schedule, through the same approval policies as any other transfer.

APPROVALS AND POLICY

No single person moves money, and every rule explains itself.

  • Maker-checker. Every outgoing transfer needs an approver who is not the person who requested it. This is enforced in the database, not only hidden in the interface.
  • Policy engine. Write rules on asset, chain, amount band, destination type, wallet tier, time of day and rolling cumulative totals.
  • Three outcomes. Each rule allows, requires approval, or blocks. A blocked transfer always says which rule stopped it.
  • Velocity limit. A daily outbound limit for the organisation. Above it, a transfer needs one extra approval even where policy would otherwise allow it.
  • Notification on every sensitive action. Approvals, policy changes, role changes and whitelist changes are emailed to the person who acted and to the organisation's owners.

DESTINATIONS

Funds go only where you have already agreed they can go.

  • Address whitelisting. Outgoing transfers go only to approved addresses.
  • 24-hour cooling period. A newly approved address cannot receive funds for 24 hours, with a visible countdown. If someone adds an address you did not expect, you have a day to notice.
  • Screened before use. New whitelist addresses are screened before they become active.
  • Labelled address book. Addresses are labelled and linked to the counterparty they belong to.

ACCESS AND IDENTITY

Stolen passwords should not move money.

  • Roles. Owner, admin, dealer, approver, compliance and viewer. Each sees and does only what the role needs.
  • Mandatory MFA. Every user, every organisation, no opt-out, enforced at the data layer.
  • Step-up authentication. Approving, releasing, whitelisting and changing policy ask for your second factor again.
  • Hold after credential change. After a password change, MFA reset or email change, that user cannot send or release funds for 24 hours.
  • New device alert. A sign-in from a new device alerts the user and the organisation's admins, and cannot approve or release anything for its first hour.
  • Self-service freeze. An owner can freeze all outbound movement instantly. Unfreezing needs a second owner, or 24 hours.

RECORDS AND RECONCILIATION

Balances you can reconcile to the last unit.

  • Ledger-derived balances. Every balance is calculated from ledger entries, never a stored counter that can drift.
  • Exact arithmetic. Amounts are held as exact decimals, never floating point.
  • Immutable audit log. Every sign-in, request, approval, policy change and transfer, with who, what and when. Exportable.
  • Statements and exports. Wallet statements and a full ledger export for your accountants and auditors.

Settle without sending first.

Wayfare is invite-only while the network builds. Tell us about your desk and we will be in touch.

Get Started