One-time addresses
Pay each person at a fresh address made from their keys, so the chain shows a payment to a new address, not to their wallet.
What a one-time address is
Each payment goes to a fresh address made from the payee’s registered keys. People looking at the chain see a payment to an address never seen before, not to the payee’s wallet. The paying address, the amount and the time stay visible.
Tick Pay to one-time addresses on the new payout form, or send oneTime: true with a budgeted API key. One-time addresses are for USDC payouts only: an EURC payment would leave no USDC at the address to pay the network fee to move it.
What stays visible
The paying address, the amount and the time are on the chain for anyone to read, the same as any payment. What a one-time address hides is the payee: the chain shows a payment to an address never seen before. Only the payee, and the payer and Memoline, who made the address, can tell whose it is.
The reference stays in your books and is not written on the chain for a one-time payment. A reference on the chain could name the payee the one-time address is there to hide.
Setting up keys, finding and moving payments
A payee registers once, at /receive, with no sign-in. Each visit, the wallet signs again to make the same keys.
- Connect a wallet. This is the wallet whose signature makes the keys and registers them.
- Make my one-time keys. The wallet signs Memoline’s message twice, and the keys are made from that signature in the browser. That signature is the key to the payee’s one-time payments, so sign it only on /receive. Signing moves no money and costs nothing. The private part of the keys stays in the browser and is never sent anywhere.
- Register these keys. The first time only. One transaction from the payee’s wallet writes the public part of the keys to Arc’s public registry, for a network fee in USDC. Payers can pay this payee at one-time addresses only after this.
- Find my payments. The page reads every announcement of a payout made through Memoline, and every other one made on Arc testnet since Memoline began reading it, and keeps the payee’s own, in the browser.
- Move this payment. Enter the wallet to move the payment to, then press this button: the page checks with Arc and shows the amount that will move and the most the network fee can cost, which comes out of the payment. Then press the button that names that amount, for example Move 24.999391 USDC for a payment of 25 USDC at Arc’s usual fee: the browser signs a transfer from the one-time address with its own key and sends it to Arc’s public node.
Smart-contract wallets cannot make these keys.
Memoline cannot make, recover or replace your keys, and cannot move a payment at a one-time address. Your keys come only from your wallet’s signature on /receive: if you lose that wallet, the payments at your one-time addresses are lost. If you register other keys, payments already made to the earlier keys can be moved only with those keys.
Why a wallet that signs differently each time cannot be used
The keys are made from the wallet’s signature of Memoline’s message, so the same wallet has to sign that message the same way every time. Memoline asks the wallet to sign twice and checks that the two signatures match. If they differ the page stops: "Your wallet signs differently each time, so these keys could not be made again. Use another wallet."
Moving a payment to your usual wallet
A one-time address holds the payment until the payee moves it. Moving it to your usual wallet links the two on the chain. Anyone reading the chain can then see that the one-time address and the usual wallet are the same person. To keep payments apart, move each to a fresh wallet of its own.
On Arc testnet only today
One-time addresses work on Arc testnet only today, where the ERC-5564 announcer and the ERC-6538 registry are deployed. On Arc mainnet the choice is hidden, and the API and /receive say: "One-time addresses are not available on this network yet."
What Memoline keeps
For each one-time payment, Memoline keeps its one-time address, the ephemeral public key and the view tag, together with a hash of the payee’s registered keys and a seal only the server can make, so a stored address that was changed is never paid. Memoline never keeps the payee’s keys, nor a payment’s private key.
Memoline also keeps the announcements /receive reads, which are public on Arc, and gives all of them to everyone who looks: a payee’s browser keeps only its own, so looking tells Memoline nothing about which payments are whose. A payer who paid through Memoline, and Memoline’s record of that payout, know the one-time address they paid.
/receive stores nothing and sends no private key anywhere: registering writes only the public part of the keys to Arc. The payee’s browser asks Arc’s public node about the wallet and each one-time address, and sends each move through it; that node can see they were asked about together.
A payment that settled without its announcement (only a transaction sent outside Memoline can do that) is marked on the payout, which shows its one-time address and its key, the ephemeral public key. The payer gives both to the payee, who enters them at /receive under "Enter a payment by its address and key".
A payment is set aside at the check, and nothing is sent to it, when:
- "This payee has not set up one-time addresses."
- "The one-time keys this payee registered are not valid keys."
- "This payee registered new one-time keys after the payout was checked."
- "This payment’s one-time address does not match what Memoline wrote at the check: it was changed since, or the server’s key changed."
- "The announcement of this payment’s one-time address would fail on Arc."
See custody, safety and what is public and the terms and privacy page.