Accounts

Private by default.

Balances and transactions on Wirex are shielded from public view onchain, powered by Arc's privacy layer (the Arc Privacy Sector, delivered through our partnership with Circle). Your users' activity stays theirs. Your program's compliance checks still run on every transaction.

What you get.

Every wallet and account on Wirex is shielded onchain by default. Public explorers do not show your users’ balances or counterparties; your program’s screening and monitoring run unchanged.

Balances not readable from public block explorers

Transaction amounts and counterparties shielded onchain

Compliance screening and monitoring unchanged

Privacy by architecture, not by policy

Two views of one transaction.

Public explorers do not show your users’ balances or counterparties; your program’s screening and monitoring run unchanged.

Public block explorerYour program and Wirex
Wallet balanceShieldedVisible
Transaction amountShieldedVisible
CounterpartyShieldedVisible
Screening and monitoringNot applicableRuns unchanged

How it works.

  1. 01

    Transactions settle on Arc with the Arc Privacy Sector, Circle’s privacy layer.

  2. 02

    Amounts, balances and counterparties are shielded from public view; the data your compliance program needs stays available to you and to Wirex.

  3. 03

    Nothing changes in your integration.

Wirex runs.

  • Privacy layer operations on Arc
  • Compliance screening and transaction monitoring
  • Reporting your program needs

Read the privacy docs.

What do teams build with it?

Privacy, answered.

Balances and transactions are shielded from public view onchain by Arc’s privacy layer, while compliance checks still run. It is privacy by architecture, not a reporting position.

Ask AI about Privacy

Give your users privacy by default.