Private payments is available with the Global USD Account. You can learn more about the Global USD Account here.
Overview
A growing number of larger companies need a way to pay counterparties (employees, vendors, subsidiaries, etc.) on-chain without revealing sensitive treasury information or exposing the relationship of one recipient to another recipient. Traditional on-chain privacy solutions often require switching networks, using unfamiliar assets, or other custom setups with significant learning curve and limitations.
Request Finance can offer a pragmatic solution for private on-chain payments by leveraging custodial wallets from a trusted partner. This approach provides strong practical privacy while staying on mainstream networks, wallets and tokens that companies already use.
How it works
The Global USD Account uses different wallet addresses when processing deposits and payouts. This mean that when you send a payment, the recipient will see a different wallet address than the one that's associated with your Global USD Account – they won't be able to trace back from where they've been paid. Additionally, the payment is mixed in with unrelated activity, obfuscating how other payees related to you are paid.
You fund the Global USD Account using a supported deposit method
Pay regularly with the Global USD Account (Single Payments are private by default) or, when batch paying, activate the Private Payments option
The recipient is paid from a sending wallet that's unrelated to your Global USD Account
When batch paying, payments are released with a random delay, mixing your payments with other unrelated activity
Result: no visible link between the funding wallet, the Global USD Account, or the recipient, and no clear way to connect related payments within a batch payment.
Why it’s private
This solution achieves privacy in two ways:
Break in direct wallet linkage: The sender address visible on-chain is an unrelated wallet not associated with your Global USD Account. Recipients cannot trace the payment back to the original payer.
Payment throttling: To avoid clustering of payments – e.g. a batch payment of a payroll run –, payments are released via a throttling mechanism, which mixes them with other unrelated activity on the sending wallet. This ensures that recipients cannot easily determine how much others are being paid or identify patterns between transfers.
You can see real activity of a sending wallet on Base below for the effect:
Key benefits
Stay on main chains and stablecoins
No new tools or workflows
No recipient onboarding required
Bank transfers supported for funding
Work the same as regular payments with the Global USD Account
Supported assets
You can find the list of the supported assets for this solution here.