eTransfers

How it works#

eTransfers are Interac-style push payments on non-custodial rails. Nobody at U.CASH can move, redirect, or hold the funds: each transfer gets its own on-chain escrow address with fixed rules, and the money only ever moves on claim (to the recipient's chosen address) or refund (to your wallet).

1. Create the transfer in your console: recipient email, amount, asset, expiry, and an optional security code. Pay precomputes a unique escrow address
2. Fund it with one plain transfer from any wallet - the console shows the exact amount and address; no approvals, no special wallet needed
3. The recipient is emailed automatically the moment the funds land, with a private claim link
4. They open the link in any browser - no account, no crypto experience, no gas - enter their wallet address (or tap "Use my U App wallet"), and claim
5. The escrow pays out to their address minus the fee; if they chose "receive as BTC/ETH", the claim routes through an instant exchange that pays native BTC or ETH to their address
6. If nobody claims by expiry, the escrow refunds your wallet on-chain - automatically, and permissionlessly

Fees#

Recipients always receive the full amount; fees are charged to the sender's account only when a transfer completes.

• Two-tier: 1% of the send up to $25, then a flat $0.25 - a $1 send costs one cent, a $100 send costs $0.25
• Free tier: verified U Accounts get 5 free completed sends every month
• Nothing for nothing: expired, cancelled, and declined transfers never cost a fee

The fee schedule is set per platform and shown live in the console panel before you send.

Assets and chains#

At claim time the recipient picks "receive as" the same asset, BTC, or ETH. BTC and ETH payouts settle through the U.CASH instant exchange rail - the provider pays true native BTC/ETH to the recipient's own address.

Security codes#

Attach an optional security code (a 4 or 8 digit PIN, or any passphrase of 4+ characters) when you create the transfer. With a code set, the claim email hides the amount and details, and the claim page requires the code before showing anything. Five wrong attempts start a 15-minute cooldown; three cooldowns lock the transfer until you unlock it from your console. Codes are stored hashed; U.CASH staff can never read them.

Cancel, decline, and reissue#

• Cancel: cancel a funded transfer before it is claimed - your own wallet signs the cancellation (a wallet signature, not a password), and the escrow returns the funds to you immediately
• Decline: the recipient can decline from the claim page ("don't want it") - funds return to you the same way
• Reissue: sent to the wrong email? Reissue to a new address without moving the escrow - the old link closes, the new recipient is emailed

Who holds what#

The funds path is always: your wallet, to a per-transfer escrow contract with fixed on-chain rules, to the recipient's address. U.CASH orchestrates the emails, the claim page, and a relayer that pays the gas - but the platform holds no keys to the escrowed funds, and the claim authorization is a destination-bound, single-use permit that cannot be redirected. An unclaimed transfer can only ever refund to the sender's wallet; there is no other exit written into the contract.

Limits and safety#

• Per-transfer value is capped (platform-set; launches conservatively and rises as the system proves itself)
• 50 transfers per account per day; at most 5 open transfers to the same recipient email per day
• Destination addresses are validated and screened against sanctions lists before any payout
• Every state change is visible in your console list with its escrow address and transaction hashes